Hi, Just I want to report that cross-compilation within Unix world works, at least.
I've tried to cross-compilation of FreeType2 (latest version checked-out from CVS) on Linux/x86, for Linux/ARM. $ env CC="arm-cats-linuxelf-gcc" \ ./configure --host=i386-pc-linux-gnu $ make is enough. I've grepped cpp outputs and they didn't include any header files for Linux/x86. # arm-cats-linuxelf is my toolkit targetted to # http://www.simtec.co.uk/products/EB110ATX/ However, configure (generated by autoconf-2.59) complains as: configure: WARNING: If you wanted to set the --build type, don't use --host. If a cross compiler is detected then cross compile mode will be used. I think, current autoconf expects new configuration style $ ./configure \ --build=i386-pc-linux-gnu \ --host=arm-cats-linux-elf But it doesn't work well with current builds/unix/unix-cc.in. Before writing patch about this issue, I have to study about proper cross-compilation setting by autoconf. And, yet I've not tried on cross-compilation between Linux and Cygwin etc. Regards, mpsuzuki On Mon, 24 Oct 2005 23:29:00 +0200 Fredrik Carlbom <[EMAIL PROTECTED]> wrote: >On 10/24/05, Werner LEMBERG <[EMAIL PROTECTED]> wrote: >>Have you tried the CVS version of libtool, together with CVS version >>of autoconf? Cygwin DLL support is still under development and/or >>broken partially, I think. >> >>Similarly, I'm not sure whether cross-compilation of FreeType works at >>all. Any reports (and bugfixes if necessary) are highly welcome. _______________________________________________ Freetype mailing list Freetype@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype