Documentation on W32

[Eli Zaretskii]

> Date: Wed, 26 Sep 2012 16:52:21 -0700
> From: "B. Scott Michel" <scottm at aero.org>

This isn't the right list to discuss these things.

> On 9/15/2012 3:43 AM, Eli Zaretskii wrote:
> >> mingw32 is _not_ broken, far from that.  It is just somewhat slow in
> >> catching up with the latest MS headers and functions, that's all.
> 
> Really slow. Painfully so.

You are welcome to help.

> >> Mingw32 is currently the _only_ package that allows building software
> >> packages that use autoconf on Windows platforms, without extensive
> >> tinkering with the infrastructure (such as the shell used to run the
> >> scripts and Makefiles) or recompiling lots of basic libraries that are
> >> already available in precompiled form from the MinGW site.  That site
> >> provides everything that is needed:
> 
> That's not completely true. You can install MSys independently from
> Mingw32, as the Mingw64 web pages suggest.

Yes, you can, but you need more tinkering to get them work together.
And MSYS isn't a 64-bit environment.

> You'd run into a problem, however, if you didn't specify CC and CXX for
> configure and make because gcc and g++ would be missing.
> 
> That's how my current development environment is configured --
> "CC=x86_64-w64-mingw32-gcc -m32" for 32-bit compiles.

That's a bug in Mingw64, IMO.