View Single Post
Old 01-24-2015, 01:12 PM   #35
chrox
Zealot
chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.
 
Posts: 144
Karma: 405567
Join Date: Nov 2012
Device: K3 KPW PB840
Quote:
Originally Posted by rkomar View Post
The SDKs also provide the system headers and libraries, so you wouldn't have to worry about which glibc/libjpeg/libtiff,... versions are being used. I cross compile using the old SDK, and I've never had a problem with the resulting objects on version 2 to version 4 firmwares. The system libraries stayed the same in the gnueabi firmwares until version 5, where some were updated. Using the old SDK, you can probably also build a version for the old 3XX devices (pre-gnueabi), as well. Those devices were built well, and many are still being used.
GLIBC problem is handled properly now in Koreader with the latest SDK from PocketBook. We managed to compile all Koreader libraries targeting GLIBC_2.4. And almost all dependencies like libpng, libjpeg, libtiff, libgif, libfreetype are self-contained in Koreader distribution so Koreader won't be affected by the library versions provided by the system. If PocketBook provides a sane framebuffer configuration Koreader can also run on rather old device/firmware while building with latest SDK.
chrox is offline   Reply With Quote