I found that using standard cross platform options with autoconf worked for me, without having to edit the Makefiles. You do want to use '. init_env' though, to get the paths right, but other than that, it worked fine for me for compiling libusb 1.12 and libptp (and the ptpcam test utility) for the FoxBoard.
If I remember correctly, you should use the --host=cris-axis-linux-gnu and the --prefix options. With this, you can have it compile and "install" the binaries in the "correct" location in the target/cris-axis-linux-gnu temporary root. You can then even do "make image" to thave those binaries included in a new image. I didn't see the need to adapt makefiles and get myself into a lot of trouble just so that building an image would only take a single 'make'. Doing a make of your ported app and then a make image seems reasonable to me. After all, the FoxBoard runs a pretty standard linux system, not some hacked-together-you-need-to-know-about-this-stuff system. Dave --- michelinok <[EMAIL PROTECTED]> wrote: > I wanna compile aMule for the Foxboard (strange idea...), so i-ve done > these steps: > > 1) Downloaded the source > 2) Uncompressed the source into /apps/amule > 3) . init_env > 4) cd apps > 5) cd amule > 6) As suggested in the documentation: > > ./configure --disable-monolithic --with-toolkit=base > --enable-amule-daemon --enable-amulecmd --enable-webserver > > 7) Edited all the makefiles adding at the top: > > AXIS_USABLE_LIBS = GLIBC > include $(AXIS_TOP_DIR)/tools/build/Rules.axis > > 8) make cris-axis-linux-gnu > > Everythings seems going fine... but I cannot locate a valid compiled > source for the foxboard, i can only find the executable for the host > machine (under apps/amule/src). > > Any idea of what i'm doing wrong? > > >
