arm-poky-linux-gnueabi-readelf -d your-appshows a list of required libraries (among others).
In this blog I will tell about my experience of porting existing applications or writting new applications for the iRex DR1000/DR800 devices.
Monday, March 8, 2010
Which Libraries do I need?
Sometimes when porting programs it is not clear which libraries you still need. The program build nicely, but does not run on the emulator or DR itself. The trick is to use the readelf-command.
Porting Libraries
When porting exsisting programs to the DR1000, the program itself is mostly not the problem, but the libraries it needs are. From the MobileRead forum I gathered the following receipt:
I assume you will be working in an environment in which you succeeded to build hello-world.
1) Configure
2) Building
3) Creating the installables
4) installing in build environment
You should now be able to use the library for porting other apps.
This ofcourse only works for libabries that come with a configure script.
I assume you will be working in an environment in which you succeeded to build hello-world.
1) Configure
./configure --host=arm-poky-linux-gnueabi --prefix=/usrWith this line you indicate that you are going to build for arm and that the root of the resulting files should go in the /usr folder.
2) Building
makeDuh!...
3) Creating the installables
make install DESTDIR=/home/user/mylibThis creates the stuff that is normally needed to install a library (.so .a) and to use it during building (.h).
cd /home/user/mylib
tar -czf mylib.tar.gz usr
4) installing in build environment
sudo tar -xzvf mylib.tar.gz -C /usr/local/poky/eabi-glibc/arm/arm-poky-linux-gnueabi/This copies the libraries and header files into the correct place of the development environment.
You should now be able to use the library for porting other apps.
This ofcourse only works for libabries that come with a configure script.
Subscribe to:
Posts (Atom)