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