Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Message-ID: <006d01c0c9ff$33c89240$562fa4cb@brasd1.vic.optushome.com.au>
From: "Travis Howell" <kirben AT optushome DOT com DOT au>
To: "Cygwin Apps" <cygwin-apps AT cygwin DOT com>
References: <3AE07A27 DOT 3AAC7BE5 AT yahoo DOT com>
Subject: Re: GCC -mno-cygwin vs mingw32-gcc cross environment.
Date: Sat, 21 Apr 2001 11:05:48 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200

Note I'm not a developer but compile a few projects under Cygwin and
mingw32.
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
tools.
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
builds.
I think a small package addition like ming32 extras which Danny Smith
provided would be easier.

----- Original Message -----
From: "Earnie Boyd" <earnie_boyd AT yahoo DOT com>
To: "Cygwin Apps" <cygwin-apps AT cygwin DOT 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 ... .
>
> Comments?
>
> Earnie.
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>