This is the mail archive of the
mailing list for the Cygwin project.
RE: [avail for test] libtool-devel-20030216-1
- From: "Norman Vine" <nhv at cape dot com>
- To: <cygwin at cygwin dot com>
- Date: Tue, 18 Feb 2003 22:17:28 -0500
- Subject: RE: [avail for test] libtool-devel-20030216-1
- Reply-to: <nhv at cape dot com>
Christopher Faylor writes:
> On Tue, Feb 18, 2003 at 09:26:12PM -0500, Charles Wilson wrote:
> >You can work around this with wrapper scripts (e.g. 'mgcc' contains
> >'exec gcc -mno-cygwin $*') but that's non standard.
> However, it could easily be standard. I could include a
> and a i686-pc-mingw-ld in the gcc distribution. And, I could also alias
> all of the i686-pc-cygwin-* tools to i686-pc-mingw32-*. That
> would provide
> the equivalent of a cross compilation environment for cygwin.
> Then you just have to say
> configure --host=i686-pc-mingw32 --target=i686-pc-mingw32
> and you bypass the arbitrary distinction of having a whole build system,
> based on cygwin which exists just so that uname returns 'mingw',
> or whatever.
> (Yes, I know that MSYS does other things, too, but this does get rid of
> the requirement of using MSYS just to make it easy to use
I use a slightly different technique
I maintain a separate /$MINGW development tree within my $CYGWIN tree
and make sure that $MINGW/bin comes before /bin in $PATH then
./configure --prefix=$MINGW --host=mingw
seems to work fine from a bash shell
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html