On Wednesday, March 13, 2002, at 11:57 PM, Gareth wrote:
I have succesfully cross compiled libmad for ARM and now it is time for compiling minimad for ARM as well. I have 2 question really
When compiling minimad normally i do "gcc minmad.c -o mimimad -lmad". -lmad being the bit that tells gcc to use libmad dunring linking. How does -lmad relate to /usr/local/lib/libmad.a? When i try this using the cross compiler it fails.
You should be able to build minimad with just "make minimad". This will link with the library in the libmad subdirectory, which is usually more appropriate than the installed /usr/local/lib/libmad.a especially when cross-compiling.
I want to develop in Code Worrior for ARM. I have made a new project and added minimad to it. Then i added mad.h and the ARM compiled libmad.a to the include path. Now when i try to compile it comes up with loads of errors about not being able to open include files. I have tried adding each individual include file to the path but the list get longer as more files are included! Is there something fundamental i am missing out?
I don't know much about Code Warrior for ARM but a lot probably depends on the target environment. minimad assumes a POSIX environment, so it may not be the most appropriate thing to try to build.
You might take a look at the madplay project I made for MS VC++. I managed to build madplay under Win32 (which is not POSIX) with an appropriately tailored config.h.
-- Rob Leslie rob@mars.org