[patch]: Decouple cygwin building from in-tree mingw/w32api building

Christopher Faylor cgf-use-the-mailinglist-please@cygwin.com
Sun Oct 21 17:11:00 GMT 2012

On Sun, Oct 21, 2012 at 01:33:20PM +0200, Corinna Vinschen wrote:
>On Oct 19 20:46, Corinna Vinschen wrote:
>>On Oct 19 11:33, Yaakov (Cygwin/X) wrote:
>>>On Fri, 2012-10-19 at 11:21 +0200, Corinna Vinschen wrote:
>>>>Other than that, I think it's good to go in after the 1.7.17 release.
>>>>I'll try to do the release at some point between now and Monday.
>>>I'll include those changes and post a new patch then.
>On second thought...  considering that w32api is now Mingw64 based, and
>considering that building Cygwin with this Mingw64 built w32api works
>fine...  what do you guys think about a "once and for all" approach?
>Is it really necessary to keep supporting a build against the old
>w32api?  What does that buy us apart from added complexity?  Doesn't
>that also mean we have to test our builds against both w32api versions
>as long as we support it?  I, for one, have no real interest to do so.

I had exactly the same thought.  I'm in favor of just doing the

That said, is it time to ask the mingw.org stuff to relocate their
CVS repo?  I could tar up the affected CVS directories for them if


More information about the Cygwin-patches mailing list