[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [OT] Re: 2.2.6: -ofoo.exe creates foo

From: Michael Haubenwallner
Subject: Re: [OT] Re: 2.2.6: -ofoo.exe creates foo
Date: Wed, 26 Nov 2008 12:56:41 +0100

On Wed, 2008-11-26 at 00:53 +0200, Roumen Petrov wrote:
> > Maybe you want to have a look at http://parity.sourceforge.net/

> The suggestion for "parity" is promising.
> For now "parity" lack standard host-triplet.

Our build environment currently is some "i586-pc-interix*" only, and we
use "i586-pc-winnt" as host-triplet (see below), with some libtool patch
(don't know its status, mduft posted it on libtool<at>gnu<dot>org IIRC).

> May be if we configure "parity" for mingw32 target (as example 
> i686-pc-mingw32) we will succeed to get a working cross-environment.

mingw32 would be wrong, as parity does not use/need mingw-libc, but
msvcrt only, additionally providing some functions/wrappers in some
static library to get better posix-compatibility.

Also, AFAICT, one usual way to create Windows-binaries on Linux is with
a mingw32-targetting cross-gcc (really cross-compiling).

> >> Also, someone ran "echo ':DOSWin:M::MZ::/usr/bin/wine:' > /proc/sys/fs/ 
> >> binfmt_misc/register" so that Windows executable be runnable directly.

> Usually this is set by wine rc file

This seems to allow for reusing the hack we currently do with Interix:

We set both $host _and_ $build to i586-pc-winnt, so we actually do not
"cross"-compile in its usual sense, because the generated (check-)
programs can actually be executed.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]