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 > i686-pc-mingw32-gcc > 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 > --build=i686-pc-cygwin > > 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 > autoconf/libtool)
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 Norman -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/