This is the mail archive of the
mailing list for the Cygwin project.
Re: GCC -mno-cygwin vs mingw32-gcc cross environment.
- To: "Cygwin Apps" <cygwin-apps at cygwin dot com>
- Subject: Re: GCC -mno-cygwin vs mingw32-gcc cross environment.
- From: "Travis Howell" <kirben at optushome dot com dot au>
- Date: Sat, 21 Apr 2001 11:05:48 +1000
- References: <3AE07A27.3AAC7BE5@yahoo.com>
Note I'm not a developer but compile a few projects under Cygwin and
I may be in the minority but I recently started using the -mno-cygwin switch
following intructions on Cygwin mailing list since it currently has
advantage of GCC 2.95.3 and find it works better than recent native mingw32
I don't mean to insult mingw developers but recent native mingw32 tools
really seem to be lagging behind and often seem to have problems in updates
(Like unstable shared libs, missing make, GCC unable to find _G_config.h)
which can waste time. Also not all mingw32 projects use configure for win32
I think a small package addition like ming32 extras which Danny Smith
provided would be easier.
----- Original Message -----
From: "Earnie Boyd" <firstname.lastname@example.org>
To: "Cygwin Apps" <email@example.com>
Sent: Saturday, April 21, 2001 4:04 AM
Subject: GCC -mno-cygwin vs mingw32-gcc cross environment.
> I've just successfully completed building a Cygwin native cross build
> environment for --target=mingw32. While I'm cleaning up the code
> modifications I would like to ask if we should consider deprecating the
> -mno-cygwin switch in favor of the cross environment?
> I would rather see the cross build environment become standard because
> it is a natural for autoconfiguration. You just add --host=mingw32 to
> the configuration scripts instead of needing to do CC='gcc -mno-cygwin'
> configure ... .
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com