Re: EOL for Cygwin - Win32 cross compiles
On Mar 11 06:31, Tony Mechelynck wrote: On 09/03/09 11:46, Corinna Vinschen wrote: Make_cyg.mak appears to use $(CC) throughout for compile and link stage anyway. So it should be sufficient (grain/salt) to call CC=i686-pc-mingw32-gcc make -f Make_cyg.mak after the -mno-cygwin option has been removed. I was assuming that the next version of Make_cyg.mak would have i696-pc-mingw32-gcc (instead of gcc) as the default for the CC variable at the same time as -mno-cygwin and -mwindows would be removed from the compiler and linker default arguments respectively. Sure. But the -mwindows option shouldn't be affected by this choice. It's triggering a linker option (--susbsystem) which sets a specific flag in the PE/COFF header of the executable to signal the subsystem the executable is running in, see http://sourceware.org/binutils/docs-2.17/ld/Options.html http://msdn.microsoft.com/en-us/library/fcc1zstk(VS.80).aspx 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 -~--~~~~--~~--~--~---
Re: EOL for Cygwin - Win32 cross compiles
On 09/03/09 11:46, Corinna Vinschen wrote: On Mar 9 07:02, Tony Mechelynck wrote: On 08/03/09 10:53, Corinna Vinschen wrote: 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 Yes, it does. Then IIUC the Make_cyg.mak can remain, with a different compiler name (which is already a variable anyway IIUC), possibly a different linker name (since we will need to use a cross-linker IIUC) removing the -mno-cygwin argument to the compiler and the -mwindows argument to the linker, and no other changes than these (which are rather minor) IIUC. Looks like YUC. Make_cyg.mak appears to use $(CC) throughout for compile and link stage anyway. So it should be sufficient (grain/salt) to call CC=i686-pc-mingw32-gcc make -f Make_cyg.mak after the -mno-cygwin option has been removed. Corinna I was assuming that the next version of Make_cyg.mak would have i696-pc-mingw32-gcc (instead of gcc) as the default for the CC variable at the same time as -mno-cygwin and -mwindows would be removed from the compiler and linker default arguments respectively. Best regards, Tony. -- When the speaker and he to whom he speaks do not understand, that is metaphysics. -- Voltaire --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: EOL for Cygwin - Win32 cross compiles
On 08/03/09 10:53, Corinna Vinschen wrote: 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 Yes, it does. Then IIUC the Make_cyg.mak can remain, with a different compiler name (which is already a variable anyway IIUC), possibly a different linker name (since we will need to use a cross-linker IIUC) removing the -mno-cygwin argument to the compiler and the -mwindows argument to the linker, and no other changes than these (which are rather minor) IIUC. Best regards, Tony. -- Motto of the Electrical Engineer: Working computer hardware is a lot like an erect penis: it stays up as long as you don't fuck with it. --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: EOL for Cygwin - Win32 cross compiles
On 08/03/09 10:45, Corinna Vinschen wrote: On Mar 7 21:15, Matt Wozniski wrote: On Sat, Mar 7, 2009 at 9:05 PM, Tony Mechelynck wrote: The only interest of Make_cyg.mak is to compile Vim binaries which don't need Cygwin to run No, it allows for compiling either mingw OR cygwin binaries (at the moment). And, if you've ever tried to run a ./configure script on cygwin, you'll understand why that's still useful... Huh? Hello? If you have trouble using vim's configure and Makefile on Cygwin, then that's a case of PEBKAC. The vim package in the Cygwin distro is build that way all the time for ages. Please don't spread misinformation about Cygwin. Corinna ...and, people, if, like me, you don't understand the above, go read http://jargonwiki.com/wiki/PEBKAC and have fun. :-D :-D :-D Best regards, Tony. -- (letter from Mark to Mike, about the film's probale certificate) I would like to get back to the Censor and agree to lose the shits, take the odd Jesus Christ out and lose Oh fuck off, but to retain 'fart in your general direction', 'castanets of your testicles' and 'oral sex' and ask him for an 'A' rating on that basis. Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: EOL for Cygwin - Win32 cross compiles
On Mar 9 07:02, Tony Mechelynck wrote: On 08/03/09 10:53, Corinna Vinschen wrote: 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 Yes, it does. Then IIUC the Make_cyg.mak can remain, with a different compiler name (which is already a variable anyway IIUC), possibly a different linker name (since we will need to use a cross-linker IIUC) removing the -mno-cygwin argument to the compiler and the -mwindows argument to the linker, and no other changes than these (which are rather minor) IIUC. Looks like YUC. Make_cyg.mak appears to use $(CC) throughout for compile and link stage anyway. So it should be sufficient (grain/salt) to call CC=i686-pc-mingw32-gcc make -f Make_cyg.mak after the -mno-cygwin option has been removed. 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 -~--~~~~--~~--~--~---
Re: EOL for Cygwin - Win32 cross compiles
On Mar 8 17:57, Matt Wozniski wrote: On Sun, Mar 8, 2009 at 5:40 AM, Corinna Vinschen wrote: You seem to be getting something wrong. When 1.7 gets released, gcc will not support the -mno-cygwin option anymore, but the distro will get a mingw cross-compiler nevertheless. You just have to use the cross-compiler i686-pc-mingw32 explicitely. No, I understood that, and was just failing to make myself clear in the email. The reason I brought this up was to suggest that either Make_cyg.mak be removed entirely, or that it be changed to use a cross-compiler explicitly rather than use the -mno-cygwin switch. If this were to be changed, we'd want to do it now, rather than after Cygwin 1.7's official release. In retrospect, I wasn't terribly clear at all, so sorry for the confusion. No worries, 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 -~--~~~~--~~--~--~---
Re: EOL for Cygwin - Win32 cross compiles
On Mar 8 03:05, Tony Mechelynck wrote: To compile a cygwin build which does require the cygwin1.dll to run, use the top-level Makefile and have it run configure (if it works, I haven't tested it). I'm the vim maintainer for the Cygwin distribution. I'm building the vim package for the Cygwin distro is build using the top-level configure all the time. It works OOTB for at least the last 8 years. 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 -~--~~~~--~~--~--~---
Re: EOL for Cygwin - Win32 cross compiles
On Mar 7 20:35, Matt Wozniski wrote: On Sat, Mar 7, 2009 at 12:35 PM, Tony Mechelynck wrote: That's if you want Vim for Cygwin. You can also use Cygwin to compile (cross-compile, if you want) versions of Vim which don't need Cygwin to run, as explained on my Windows HowTo Hm. Support for using cygwin's gcc to do cross-compile builds is soon to be dropped. Maybe we should remove the option to do this from Make_cyg.mak? Or, at least add a note to the README noting that the option is deprecated and soon to be removed? You seem to be getting something wrong. When 1.7 gets released, gcc will not support the -mno-cygwin option anymore, but the distro will get a mingw cross-compiler nevertheless. You just have to use the cross-compiler i686-pc-mingw32 explicitely. 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 -~--~~~~--~~--~--~---
Re: EOL for Cygwin - Win32 cross compiles
On Mar 7 21:15, Matt Wozniski wrote: On Sat, Mar 7, 2009 at 9:05 PM, Tony Mechelynck wrote: The only interest of Make_cyg.mak is to compile Vim binaries which don't need Cygwin to run No, it allows for compiling either mingw OR cygwin binaries (at the moment). And, if you've ever tried to run a ./configure script on cygwin, you'll understand why that's still useful... Huh? Hello? If you have trouble using vim's configure and Makefile on Cygwin, then that's a case of PEBKAC. The vim package in the Cygwin distro is build that way all the time for ages. Please don't spread misinformation about Cygwin. 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 -~--~~~~--~~--~--~---
Re: EOL for Cygwin - Win32 cross compiles
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 -~--~~~~--~~--~--~---
Re: EOL for Cygwin - Win32 cross compiles
On Mar 8 10:53, Corinna Vinschen wrote: On Mar 8 03:32, Tony Mechelynck wrote: 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 i386-pc-solaris2.11-gcc - 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 i686-pc-mingw32-gcc I assume that was clear but sorry about the typos anyway. 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 -~--~~~~--~~--~--~---
Re: EOL for Cygwin - Win32 cross compiles
On Sun, Mar 8, 2009 at 5:40 AM, Corinna Vinschen wrote: On Mar 7 20:35, Matt Wozniski wrote: On Sat, Mar 7, 2009 at 12:35 PM, Tony Mechelynck wrote: That's if you want Vim for Cygwin. You can also use Cygwin to compile (cross-compile, if you want) versions of Vim which don't need Cygwin to run, as explained on my Windows HowTo Hm. Support for using cygwin's gcc to do cross-compile builds is soon to be dropped. Maybe we should remove the option to do this from Make_cyg.mak? Or, at least add a note to the README noting that the option is deprecated and soon to be removed? You seem to be getting something wrong. When 1.7 gets released, gcc will not support the -mno-cygwin option anymore, but the distro will get a mingw cross-compiler nevertheless. You just have to use the cross-compiler i686-pc-mingw32 explicitely. No, I understood that, and was just failing to make myself clear in the email. The reason I brought this up was to suggest that either Make_cyg.mak be removed entirely, or that it be changed to use a cross-compiler explicitly rather than use the -mno-cygwin switch. If this were to be changed, we'd want to do it now, rather than after Cygwin 1.7's official release. In retrospect, I wasn't terribly clear at all, so sorry for the confusion. ~Matt --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
EOL for Cygwin - Win32 cross compiles
On Sat, Mar 7, 2009 at 12:35 PM, Tony Mechelynck wrote: That's if you want Vim for Cygwin. You can also use Cygwin to compile (cross-compile, if you want) versions of Vim which don't need Cygwin to run, as explained on my Windows HowTo Hm. Support for using cygwin's gcc to do cross-compile builds is soon to be dropped. Maybe we should remove the option to do this from Make_cyg.mak? Or, at least add a note to the README noting that the option is deprecated and soon to be removed? ~Matt --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: EOL for Cygwin - Win32 cross compiles
On Sat, 2009-03-07 at 20:35 -0500, Matt Wozniski wrote: Hm. Support for using cygwin's gcc to do cross-compile builds is soon to be dropped. Why?! Maybe we should remove the option to do this from Make_cyg.mak? Or, at least add a note to the README noting that the option is deprecated and soon to be removed? Not sure why something so useful would be intentionally dropped. My gVim installer for windows is downloaded 5,000 times a month. -- Steve Hall [ digitect dancingpaper com ] --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: EOL for Cygwin - Win32 cross compiles
On 08/03/09 02:35, Matt Wozniski wrote: On Sat, Mar 7, 2009 at 12:35 PM, Tony Mechelynck wrote: That's if you want Vim for Cygwin. You can also use Cygwin to compile (cross-compile, if you want) versions of Vim which don't need Cygwin to run, as explained on my Windows HowTo Hm. Support for using cygwin's gcc to do cross-compile builds is soon to be dropped. Maybe we should remove the option to do this from Make_cyg.mak? Or, at least add a note to the README noting that the option is deprecated and soon to be removed? ~Matt The only interest of Make_cyg.mak is to compile Vim binaries which don't need Cygwin to run, using the -mno-cygwin option of the Cygwin gcc compiler and the appropriate corresponding option of the linker. If Cygwin drops the option, then you should not use Make_cyg.mak but switch (for instance) to MinGW and Make_ming.mak. To compile a cygwin build which does require the cygwin1.dll to run, use the top-level Makefile and have it run configure (if it works, I haven't tested it). Best regards, Tony. -- All the taxes paid over a lifetime by the average American are spent by the government in less than a second. -- Jim Fiebig --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: EOL for Cygwin - Win32 cross compiles
On Sat, Mar 7, 2009 at 9:05 PM, Tony Mechelynck wrote: On 08/03/09 02:35, Matt Wozniski wrote: On Sat, Mar 7, 2009 at 12:35 PM, Tony Mechelynck wrote: That's if you want Vim for Cygwin. You can also use Cygwin to compile (cross-compile, if you want) versions of Vim which don't need Cygwin to run, as explained on my Windows HowTo Hm. Support for using cygwin's gcc to do cross-compile builds is soon to be dropped. Maybe we should remove the option to do this from Make_cyg.mak? Or, at least add a note to the README noting that the option is deprecated and soon to be removed? The only interest of Make_cyg.mak is to compile Vim binaries which don't need Cygwin to run No, it allows for compiling either mingw OR cygwin binaries (at the moment). And, if you've ever tried to run a ./configure script on cygwin, you'll understand why that's still useful... using the -mno-cygwin option of the Cygwin gcc compiler and the appropriate corresponding option of the linker. 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 --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: EOL for Cygwin - Win32 cross compiles
On Sun, 2009-03-08 at 03:05 +0100, Tony Mechelynck wrote: The only interest of Make_cyg.mak is to compile Vim binaries which don't need Cygwin to run, using the -mno-cygwin option of the Cygwin gcc compiler and the appropriate corresponding option of the linker. Hmm, I use only: make -f Make_cyg.mak GUI=yes all via the bash shell and end up with no dependencies. If Cygwin drops the option, then you should not use Make_cyg.mak but switch (for instance) to MinGW and Make_ming.mak. Do these now fully support all gVim's features? I seem to recall several years ago when I moved away from BCC that not all the usual perl, python, tcl, mzscheme, ruby, ole, etc. features were. -- Steve Hall [ digitect dancingpaper com ] --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: EOL for Cygwin - Win32 cross compiles
On 08/03/09 03:15, Matt Wozniski wrote: On Sat, Mar 7, 2009 at 9:05 PM, Tony Mechelynck wrote: On 08/03/09 02:35, Matt Wozniski wrote: On Sat, Mar 7, 2009 at 12:35 PM, Tony Mechelynck wrote: That's if you want Vim for Cygwin. You can also use Cygwin to compile (cross-compile, if you want) versions of Vim which don't need Cygwin to run, as explained on my Windows HowTo Hm. Support for using cygwin's gcc to do cross-compile builds is soon to be dropped. Maybe we should remove the option to do this from Make_cyg.mak? Or, at least add a note to the README noting that the option is deprecated and soon to be removed? The only interest of Make_cyg.mak is to compile Vim binaries which don't need Cygwin to run No, it allows for compiling either mingw OR cygwin binaries (at the moment). And, if you've ever tried to run a ./configure script on cygwin, you'll understand why that's still useful... I stand corrected. using the -mno-cygwin option of the Cygwin gcc compiler and the appropriate corresponding option of the linker. 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. (Of course it should _also_ be possible to compile programs for the cygwin1.dll.) Best regards, Tony. -- To a Real Woman, every ejaculation is premature. --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: EOL for Cygwin - Win32 cross compiles
On Sat, Mar 7, 2009 at 9:32 PM, Tony Mechelynck wrote: On 08/03/09 03:15, Matt Wozniski wrote: On Sat, Mar 7, 2009 at 9:05 PM, Tony Mechelynck wrote: using the -mno-cygwin option of the Cygwin gcc compiler and the appropriate corresponding option of the linker. 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. If removing the option has always been confusing to users, then why can't they leave it in? No, *having* the option has always been confusing to users. Regularly people ask for help on the cygwin mailing lists for programs compiled with the -mno-cygwin flag, not realizing that adding that flag meant that they made a program that wasn't linked against cygwin1.dll and couldn't use any cygwin capabilities. It's pretty confusing to install through cygwin's setup.exe cygwin's gcc, invoke a magical flag to cygwin's compiler, and create a product that's explicitly only supported by mingw and not by cygwin. 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. I never said it wasn't useful, just that it has never worked properly and has no significant advantages over simply compiling with mingw. Compiling native windows programs with Debian's gcc would also be useful, but you're not likely to find a great deal of support for adding a -mno-debian switch to Debian's gcc for that purpose. ~Matt --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: EOL for Cygwin - Win32 cross compiles
On Sat, Mar 7, 2009 at 10:29 PM, Tony Mechelynck wrote: On 08/03/09 03:49, Matt Wozniski wrote: On Sat, Mar 7, 2009 at 9:32 PM, Tony Mechelynck wrote: [...] 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. I never said it wasn't useful, just that it has never worked properly and has no significant advantages over simply compiling with mingw. Compiling native windows programs with Debian's gcc would also be useful, but you're not likely to find a great deal of support for adding a -mno-debian switch to Debian's gcc for that purpose. I'm not asking that much. Debian usually doesn't run under Windows, after all. Cygwin, OTOH, does, which makes it more obvious why it would be useful to use it as a true Unix-like environment, with all the power that that implies, to compile true Windows applications, even if it must then be understood that such true Windows applications won't run in the environment where they were compiled. There's nothing stopping you from setting up your own cross toolchain, which is really what mingw is for, anyway. In fact, this is the more portable (and more unix-y) way to go - you can compile Windows programs on Debian or Cygwin using a cross-compile toolchain, without the need for a half-baked never-fully-implemented magical compiler switch. I never used MinGW (except insofar as the -mno-cygwin compiler is a MinGW-for-Cygwin compiler) but from what I heard when I still had Windows it didn't sound as convincing as Cygwin. Huh? They do different things. Cygwin provides a POSIX emulation layer through cygwin1.dll, mingw provides mappings from POSIX concepts to Windows concepts to try to make it possible to cross-compile POSIX applications. What's there to be convinced about? Either one is the right tool for the job, or the other is. ~Matt --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: EOL for Cygwin - Win32 cross compiles
On 08/03/09 04:40, Matt Wozniski wrote: [...] Huh? They do different things. Cygwin provides a POSIX emulation layer through cygwin1.dll, mingw provides mappings from POSIX concepts to Windows concepts to try to make it possible to cross-compile POSIX applications. What's there to be convinced about? Either one is the right tool for the job, or the other is. ~Matt Sounds like you'd end up convincing me that, if I were still on Windows -- which I'm not -- the right tool for compiling Vim would be MSVC... But I made the switchover to SuSE Linux, and like in fairytale stories, I've lived happily ever after. ;-) Best regards, Tony. -- A student who changes the course of history is probably taking an exam. --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: EOL for Cygwin - Win32 cross compiles
On Sat, Mar 7, 2009 at 9:21 PM, Steve Hall wrote: On Sun, 2009-03-08 at 03:05 +0100, Tony Mechelynck wrote: The only interest of Make_cyg.mak is to compile Vim binaries which don't need Cygwin to run, using the -mno-cygwin option of the Cygwin gcc compiler and the appropriate corresponding option of the linker. If Cygwin drops the option, then you should not use Make_cyg.mak but switch (for instance) to MinGW and Make_ming.mak. The option will be dropped. Do these now fully support all gVim's features? I seem to recall several years ago when I moved away from BCC that not all the usual perl, python, tcl, mzscheme, ruby, ole, etc. features were. Well, the mingw compiler clearly supports them, and must be able to find and link the libraries, if you're able to build with these options using Make_cyg.mak - so, if Make_mingw.mak doesn't support these options, then it's only a matter of fixing up the Makefile (and possibly the README). ~Matt --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
