|
From: Sisyphus <sis...@op...> - 2007-07-04 00:48:47
|
----- Original Message ----- From: "Hugh McMaster" <das...@gm...> . . > > $ ./configure --host=i686-pc-mingw32 --build=i686-pc-cygwin CC='gcc > -mno-cygwin ' host_alias=i686-pc-mingw32 > > This command will invoke the MinGW compiler under Cygwin. > Does that then result in a "native" Win32 build ? Or does it still produce a "Cygwin" build ? Also how is MinGW (which could be anywhere on the box) located by the above command ? I often need to run './configure' in the MSYS shell - so that I can build various "native" Win32 libraries. Unfortunately MSYS won't work for me on Vista - all I get is a cascade of shells opening up, which terminates with a crash. So, if there's some way I can use Cygwin's shell to run './configure' and still end up with "native" Win32 libraries, I'd probably do just that (assuming Cygwin's shell runs ok on Vista). As it stands, I'm having to build these libraries on an older, slower Windows 2000 box and copy the libraries across - not a very appealing way of going about it, and hence my interest in seeking clarification re the above command. Cheers, Rob |