QUOTE(azalin @ Mar 16 2006, 01:28 AM)
Next step is to try some packages dependant on other libraries.
How do I compile multiple libraries and dependency chains? Should I install compiled libs and headers into /opt/cross/arm or somewhere and maintain a little tree there? Or do I need to use pdaxrom build system for that? Inquiring minds need to know!
I would like to know the same, I succesfully compiled a library (OpenAL) than an app (GemRB) needs I am trying to cross compile, but if I make install for the library I have no clue where it puts it and the configure of the app (GemRB) can not find that the library is installed.
I have some .so, .so.0, .so.0.0.0, .lai, .la and .a files (the .0 and .0.0.0 are symlinks of course) after I did a make, I saw /opt/cross/arm/3.4.5-xscale-softvfp/lib exists and a /opt/cross/arm/3.4.5-xscale-softvfp/armv5tel-cacko-linux/lib/
also where do I need to put the includes? just in
/opt/cross/arm/3.4.5-xscale-softvfp/armv5tel-cacko-linux/include/ and it should
work? The app depends on SDL, OpenAL, Python and zlib, of which I think zlib and SDL are in the SDK, not sure about python so I need to check but it does exist for the PdaXrom so if not in the SDK then I suppose there is a way to convert the ipk back to a set of libraries and includes and copy those in the proper places so that the configure of the app finds them.
/opt/cross/arm/3.4.5-xscale-softvfp/lib/ seems to contain i386 libraries, for instance
libglib-2.0.so.0.800.1: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), not stripped
the other directory
libglib-2.0.so.0.800.1: ELF 32-bit LSB shared object, ARM, version 1 (ARM), not stripped
So my bet is that you should put .so and .a files into
include files into
if the package used "configure" script
you can try
PREFIX=/opt/cross/arm/3.4.5-xscale-softvfp/armv5tel-cacko-linux/ make install
(examine makefile whether it uses PREFIX variable or something)