Re: [Mingw-w64-public] Release policy , relationship to other mingw projects.

[NightStrike <nig...@gm...>]

On Sun, Mar 15, 2009 at 4:57 PM, Arthur Norman <ac...@ca...> wrote:
>>>  Are there any efforts to arrange for such an integration in the near
>>>  future?
>>
>> The way that mingw.org packages things is too
>> confusing for my tastes.  However, we have not yet begun to port
>> things like msys, or to try compiling msys on/for Win64.  I personally
>> feel that the msys environment is sub-par, and if you need that much
>> in the way of gnu tools, you're better off going with cygwin.
>>
> I will stick a thought in here, but I am naturally aware that ANY move that
> consolidates mingw-w64 with other code is liable to be both a tecnical and a
> political mountain of pretty substantial magnitude, so my "wish" here is
> something I would see as a long-term ideal and probably not a short term
> easy action.
>
> I would like to fetch one package and then have
>   gcc foo.c -o foocygwin               32-bit cygwin
>   gcc -mno-cygwin foo.c -o foow32      32-bit native windows
>   gcc -mno-cygwin -m64 foo.c -o foow64 64-bit native windows
> with all that happening effortlessly with an easy click or two in the
> options about what I fetch when I fetch the whole cygwin environment that I
> like to have so I can use all the other associated GNU and Unix-style tools.
>
> So if there was any prospect that the cygwin people would be willing to fold
> your stuff into the multi-lib scheme that they already have that supports
> mingw-w32 that would give a very comfortable experience for people like me.
>
> Meanwhile what you have right now is still GREAT!
>            Arthur

We are working on multilib support, and have already lined up cygwin
support.  The only reason cygwin doesn't provide our toolchains yet is
that I haven't found the time to give them the files for it.  I'm
trying to keep my head above water :)