On Mon, Jan 25, 2010 at 06:56:02PM +1030, Ron wrote: > On Sun, Jan 24, 2010 at 09:19:33PM +0100, Jens Thiele wrote: > > Okay, then let me try to suggest some description. First a summary: > > > > - there are 2 cross compilers for the mingw32 target > > (gcc-mingw32 and ming32) > > No, there is only gcc. There are now multiple variants of > that being uploaded as binary debs.
To be accurate, there's GCC 4.4 (gcc-mingw32 package) and a fork of GCC 4.2.1 (mingw32 package). > Mingw is the original project to port gcc for windows targets. > Some of the patches for mingw have been pushed into mainline gcc, > but still not all of them. > > [...] > Some projects have already found that gcc-mingw doesn't work for > them, so the patches mingw are carrying clearly aren't all 'optional'. Last time we discussed this, we couldn't figure out anything, other than the existance of a big monolithic set of modifications with undetermined purpose. Has something changed? If it has, I wasn't notified about it. > We have gcc-mingw32 because Robert was too impatient for 64 bit > support and building only the mainline code Worked For Him for > the one thing he needed it for. There's nothing wrong with building GCC for mingw32 targets now that it is officially supported. And yes, GCC 4.4 worked for me and my own needs, but it also seems to work for a lot other people. > There really isn't any other > reason for having it that I'm aware of. Some reasons (other than mine) can be found in: http://gcc.gnu.org/gcc-4.3/changes.html and in: http://gcc.gnu.org/gcc-4.4/changes.html -- Robert Millan "Be the change you want to see in the world" -- Gandhi -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
