Re: The mingw* mess in Debian
On Wed, 09 Nov 2011 at 13:33:14 +0100, Fabian Greffrath wrote:
> is there a reason why we have both a mingw32 and a gcc-mingw32
> package in Debian? Both seem to contain the same, i.e. the GCC from
> the MinGW project (please note they dropped the "32" for a while),
> but the version in gcc-mingw32 is newer than the one in mingw32.
mingw-w64 isn't the same upstream as mingw - it's a separate project
(a fork of mingw, I think?) which targets both 32- and 64-bit Windows.
I believe the rationale for gcc-mingw32 was largely that mingw32 wasn't updated
for a while (it's gcc 4.2 whereas gcc-mingw32 is 4.4), while the rationale
for mingw-w64 is that it's needed for wine-gecko, the browser engine used by
recent versions of Wine to emulate the embeddable Internet Explorer libraries
(MSHTML etc.), although I could be wrong. mingw-w64 seems to be the preferred
version these days?
The mingw32 and mingw32-binutils packages seem to be done as independent
sources, whereas gcc-mingw32 and mingw-w64 use binutils-source and
gcc-4.x-source (where x is currently 4) and patch it, if I'm understanding
gcc-mingw32 now has the same maintainer as mingw-w64 (Stephen Kitt, who has
also worked on Wine 1.2 packaging, although sadly that hasn't made it into
Does mingw have any particular advantages over mingw-w64, I wonder?
* http://mingw-w64.sourceforge.net/ - mingw-w64
* http://www.mingw.org/ - mingw (aka mingw32)
* i686-w64-mingw32 - mingw-w64 for 32-bit Windows
* x86_64-w64-mingw32 - mingw-w64 for 64-bit Windows
* i586-mingw32msvc - mingw32 and gcc-mingw32 for 32-bit Windows
* amd64-mingw32msvc - gcc-mingw32 for 64-bit Windows (removed post-squeeze
in favour of x86_64-w64-mingw32)