-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2/9/2011 05:53, Paul Leder wrote:
> Sorry if this is slightly off-topic - I'm trying to build a standard 
> Linux autoconf project for Windows using mingw-w32-1.0-bin_i686-linux.
> 
> Does anyone happen to know what 'configure' invocation I should use for 
> this? Are '--build' and '--host' sufficient, or do I have to point at 
> local include and lib dirs as well? And can I avoid setting all the 
> CC/etc environment variables by setting a tool prefix? The build host is 
> i686, and the target is either 32-bit or 64-bit W7/Vista/XP.
> 

It depends on the prefix of the toolchain you are using. For example,
using x8_64-w64-mingw32-gcc means using --host=x86_64-w64-mingw32, its
that simple with autotools. The --build option specifies the toolchain
used for building native programs. So if you are cross compiling from
cygwin to win64, you should use --build=i686-pc-cygwin
- --host=x86_64-w64-mingw32.

Once you've set --build and --host, you don't need to set CC and
friends, likewise for the include and lib directories, unless those are
out of the cross compiler search path.

> BTW, I've just converted another makefile-based project from an old 
> mingw native build on Cygwin, to a Linux cross-compile using MinGW-w64. 
> This went like a dream - no problems at all, much easier than the old 
> native build, and a much better version of gcc. Thanks.

You should use autotools, its platform independence and cross compile
support are its best defining qualities.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (MingW32)

iEYEARECAAYFAk1RzqsACgkQp56AKe10wHeYUgCfYuEOlzDcdpof/Pl24kj1X060
Fb8Anj3CN1/E/ZLZdz9RDBAnqUii0Mu9
=zKMW
-----END PGP SIGNATURE-----

Attachment: 0xED74C077.asc
Description: application/pgp-keys

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to