On Mar 8 03:32, Tony Mechelynck wrote: > On 08/03/09 03:15, Matt Wozniski wrote: > > This option will be removed when Cygwin migrates to Cygwin 1.7 / gcc > > 4. See http://www.cygwin.com/ml/cygwin/2008-09/msg00291.html . > > Removing the option has been planned for some time - it has never > > really worked correctly, it provides no significant advantages over > > simply using mingw to compile, and it has historically been very > > confusing to users. > > > > ~Matt > > If removing the option has always been confusing to users, then why > can't they leave it in? The _option_ to compile native-Windows programs > using Cygwin gcc _is_ a useful thing, I can't imagine on what grounds > someone would think the opposite.
Nobody thinks the opposite. Here's the deal: - On Linux, you build Linux binaries using the native gcc - On Solaris, you build Solaris binaries using the native gcc - On Linux, you build Solaris binaries using a cross-compiler called i386-pc-solaris2.11 - On Cygwin you build Cygwin binaries using the native gcc - On Mingw you build Mingw binaries using the native gcc - On Cygwin you build Mingw binaries using a cross-compiler called i686-pc-mingw32 The -mno-cygwin option was always just a hack. You could have put this hack into the Linux i686 compiler as well, but why would you? Same for Cygwin. The -mno-cygwin option will be removed. To build a Mingw binary, which is logically a cross-build, you will need a cross-compiler. With the move to the new Cygwin 1.7 release and the move to the latest gcc-4.x release, the -mno-cygwin option will be replaced by a mingw cross-compiler which will become part of the distro. Does that make sense? Corinna -- Corinna Vinschen Cygwin Project Co-Leader Red Hat --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
