Chris Walters <cjw20...@comcast.net> wrote:
> I am using the equivalent of the Debian cross compiler - without Debian. This
> has been used to cross compile many 32 bit applications from Debian for W32,
> from what I understand. I have managed to cross compile bzip2, lame, libogg,
> libvorbis, vorbis-tools, and a few others - they all work. With most, I only
> needed to set the correct path (to mingw), and specify the tools and target
> and
> run the configure script. I ran into problems with gzip and zlib, however.
>
> Thanks for the link, I will look into it. Though I hate the idea of running
> msys and mingw or anything like that in a W64 environment.
>
> The really annoying thing for me is that if you look at the Mingw64 site on
> sourceforge, they indicate that you can cross compile from a GNU/Linux
> distribution to W32 or W64 - and they give a list of apps that were
> successfully cross compiled, but little in the way of documentation.
GNU autoconf allows to set up "default results" for cross compiling when trying
to test things that need to run on the target.
Some of the basic GNU text utils either return most pessimistic values in case
of a cross compilation or someone did handcraft the related results for MinGW
and publishes such a modified source that probably will no longer compile
correctly on other systems.
BTW: I introduced the cross compilation extensions to schily autoconmf in order
to permit to compile my software for android.
Jörg
--
EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
j...@cs.tu-berlin.de (uni)
joerg.schill...@fokus.fraunhofer.de (work) Blog:
http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
