This is the mail archive of the
mailing list for the Cygwin project.
Re: GCC -mno-cygwin vs mingw32-gcc cross environment.
- To: egor duda <cygwin-apps at cygwin dot com>
- Subject: Re: GCC -mno-cygwin vs mingw32-gcc cross environment.
- From: Earnie Boyd <earnie_boyd at yahoo dot com>
- Date: Fri, 20 Apr 2001 14:30:06 -0400
- References: <3AE07A27.3AAC7BE5@yahoo.com> <email@example.com>
- Reply-To: Cygwin Apps <cygwin-apps at cygwin dot com>
egor duda wrote:
> Friday, 20 April, 2001 Earnie Boyd firstname.lastname@example.org wrote:
> EB> I've just successfully completed building a Cygwin native cross build
> EB> environment for --target=mingw32. While I'm cleaning up the code
> EB> modifications I would like to ask if we should consider deprecating the
> EB> -mno-cygwin switch in favor of the cross environment?
> EB> I would rather see the cross build environment become standard because
> EB> it is a natural for autoconfiguration. You just add --host=mingw32 to
> EB> the configuration scripts instead of needing to do CC='gcc -mno-cygwin'
> EB> configure ... .
> EB> Comments?
> -mno-cygwin is currently used when building parts of cygwin itself. we
> must be dealing with it somehow.
> i don't think we should deprecate -mno-cygwin (i believe it's quite
> handy sometimes) but rather discourage using it when it's natural to
> configure with --host=mingw32
Perhaps this will help with understanding what I said:
I.E.: Deprecate != remove.
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com