cosam
Active Member
That's a good start, but I'd personally use a different prefix if you're planning on doing a "make install" so you can easily see which files get copied (and therefore need including in your package). I have a bunch of CFLAGS set up too which most configure scripts will take from the environment variables. Other than that, it's a case of looking through the other options and enabling/disabling features and specifying paths to libraries/includes where appropriate. That said: does the SDK include pkg-config and the likes? Aliasing that/those would help automate a lot of this configure script stuff.laurens said:In this specific case, ./configure --host=arm-none-linux-gnueabi --prefix-dir=$PNDSDK seems to help, but not sure if it really works quite yet.
Anyway, if you're very lucky you'll get it to build and link just by feeding "configure" the right parameters. In my experience it's however not exactly foolproof. I dare say most of these scripts haven't been tested to destruction and a lot of them fall over when cross-compiling. Be on the lookout for missing object files (usually not hard to compile separately) and expect random linking problems. Sometimes it's easier to do the final linking manually or with a simple script, than mess around getting the build to work in the usual fashion.
Last edited by a moderator: