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
-~----------~----~----~----~------~----~------~--~---
