[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: Roumen Petrov
Subject: Re: [OT] Re: 2.2.6: -ofoo.exe creates foo
Date: Wed, 26 Nov 2008 00:53:45 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20081114 SeaMonkey/1.1.13

Michael Haubenwallner wrote:
On Tue, 2008-11-25 at 10:48 +0100, Akim Demaille wrote:
Le 25 nov. 08 à 09:13, Michael Haubenwallner a écrit :

And we have a wrapper around cl.exe and link.exe to have the usual tool chain (including libtool), which we can send if you wish. But it's hackish and not very clean.

Maybe you want to have a look at http://parity.sourceforge.net/

The reporter try to use *-*-pw32 as host.
Now this is not active project and I could not get pw32 to run fine under emulated environment.
In spite of that pw32 run better then msys in emulated environment.
Libtool after 2.2.4(? if i remember well) switch to binary wrappers for cygwin and mingw targets. This eliminate needs to run a host shell and other host binaries under emulated environment. This is reported case - "why -offo.exe creates foo" - the answer is that foo is wrapper shell script and ...(already answered).

The suggestion for "parity" is promising.
For now "parity" lack standard host-triplet.
May be if we configure "parity" for mingw32 target (as example i686-pc-mingw32) we will succeed to get a working cross-environment.

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

Sounds interesting...

Usually this is set by wine rc file

PS: Maybe we should go off-list now...

Really no. It is related to how to run binaries from other operating systems. The above is for linux.


reply via email to

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