This is the mail archive of the
mailing list for the Cygwin project.
Re: [Mingw-users] HOWTO setup cygwin's 'gcc -mno-cygwin' using mingw
- To: mingw-users at lists dot sourceforge dot net, cygwin-apps at cygwin dot com
- Subject: Re: [Mingw-users] HOWTO setup cygwin's 'gcc -mno-cygwin' using mingw
- From: Earnie Boyd <earnie_boyd at yahoo dot com>
- Date: Sun, 18 Mar 2001 13:03:57 -0500
- CC: Kees Zeelenberg <c dot zeelenberg at hccnet dot nl>, Paul Sokolovsky <paul-ml at is dot lg dot ua>, Tor Lillqvist <tml at iki dot fi>, "Charles S. Wilson" <cwilson at ece dot gatech dot edu>
- References: <20010318124300.J12880@redhat.com>
- Reply-To: Earnie Boyd <mingw-users at lists dot sourceforge dot net>, cygwin-apps at cygwin dot com
Christopher Faylor wrote:
> I was wondering the other day if all of the cygwin mingw stuff shouldn't
> be installed in its own completely separate /mingw directory as Earnie
> has suggested in another message. Then a person could drop in a mingw
> from mingw.org and have it work with cygwin -- and I could drop the
> mingw part of the cygwin distribution.
Hmm... I've also said that we should actually treat MinGW as a cross
build with target specific libraries before. But that means a separate
build of GCC and friends just for MinGW and that is what the -mno-cygwin
switch is avoiding. However, since this is basically what we're
discussing, providing cross platform libraries, maybe we should just
forget the -mno-cygwin switch and allow 'configure --host=mingw32' to
take care of it.
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com