Re: [Mingw-users] More mingw Linux->Windows

[Aaron W. L. <aar...@aa...>]

Garthy wrote:

> Should be the last non-comment line in the prior attached script.
> As mentioned in the prior post, I could fix this, fix the next
> bug etc. I went down that road and got nowhere. Hence looking for
> a "standard", recommended, or approved way. Every solution offered
> thus far has been unique, generally complex, and often fixed to
> a particular revision. If you've encountered an easy solution, do
> share. :)

Well, I didn't see your attachment.  Its my suspicion, though, that your
build script is doing something other than 'make' such as 'make all-gcc'
or something.

> The advantage of a script is that it makes a complex build
> procedure repeatable. I think mingw might fall under that
> category, though to be honest I would love to be proven wrong. :)

I don't think theres anything complex about it.  Setting up the build
for a cross compiler shouldn't take any longer than a native compiler,
and will probably be only take a percent of the time the whole build takes.

All you need to build is a crossassembler and crosslinker, from
binutils, then the crosscompiler, from gcc, then any libraries, if
necessary.  All you need to do to make binutils and gcc cross is use the
--target configure option; it should 'just work'.  Don't try to
bootstrap; just type 'make.'  Any errors you get here are bugs, and
should be reported.

For the libraries, I always just use binary libraries built natively;
but I would suspect that the procedure would be the same for
mingw-runtime and w32api: just pass --target to configure.

The GCC installation instructions have some additional information on
crosscompiling that might be useful to read.

Aaron W. LaFramboise