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:	<5.0.2.1.0.20010422134844.009fa420@bastion.datatask.com.au>
X-Sender:	ecognito1 AT foobar DOT com (Unverified)
X-Mailer:	QUALCOMM Windows Eudora Version 5.0.2
Date:	Sun, 22 Apr 2001 14:04:34 +1000
To:	cygwin-apps AT cygwin DOT com
From:	E <ecognito1 AT earthcorp DOT com>
Subject:	Re: GCC -mno-cygwin vs mingw32-gcc cross environment.
Mime-Version:	1.0

 > On Fri, Apr 20, 2001 at 02:04:23PM -0400, Earnie Boyd wrote:
 > >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?

Not remembering precisely how cross-compiler installations are layed out in 
the file system, but could a possible alternative be to have symbollic 
links such as:

ln -s /usr/bin/gcc /usr/bin/i686-pc-mingw32-gcc.exe

And all the rest that you normally have, and when GCC/G++ or whatever 
binutil sees this, it implicitly adds the -mno-cygwin switch?

That would take care of the configure --target=mingw32 stuff for you 
without needing to install a whole other set of binaries and toolchains.

There's probably a whole lot of cons with this that I'm not aware of (not 
having used cross-compilers a great deal) but thought I'd offer it as a 
suggestion.

E.

- Raw text -