On Wed, Dec 09, 2009 at 02:02:08PM +0200, Nerijus Baliunas wrote:
> On Tue, 1 Dec 2009 17:51:03 +0800 aaron lwe <[email protected]> wrote:
>
> > The configure options I used is:
> > ./configure --prefix=/usr/i686-pc-mingw32/sys-root/mingw
> > --host=i686-pc-mingw32 --build=i686-linux --enable-monolithic
> > --disable-shared --enable-unicode --disable-threads
>
> Isn't it better to use mingw-configure instead of ./configure?
It depends. mingw32-configure is just a convenient helper script.
It's there if you find it helpful, but you don't have to use it.
In many situations it is sufficient just to do:
./configure --host=i686-pc-mingw32
Only the --host parameter is required. It's what triggers cross-
compilation.
You can find out what mingw32-configure would do by using this
command:
rpm --eval '%{_mingw32_configure}'
It expands to a couple of pages of code on my local machine.
BTW the --build parameter that Aaron used really is unnecessary, and
possibly wrong. I can't think of a situation when ./configure
wouldn't be able to correctly determine the current build system.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
New in Fedora 11: Fedora Windows cross-compiler. Compile Windows
programs, test, and build Windows installers. Over 70 libraries supprt'd
http://fedoraproject.org/wiki/MinGW http://www.annexia.org/fedora_mingw
_______________________________________________
fedora-mingw mailing list
[email protected]
https://admin.fedoraproject.org/mailman/listinfo/fedora-mingw
