Winelib and C++ static initialization

André Hentschel nerv at dawncrow.de
Thu Aug 27 13:31:51 CDT 2015


Am 27.08.2015 um 01:53 schrieb Luke Dunstan:
> 
> 
> On Thu, 27 Aug 2015 at 00:44 Stefan Dösinger <stefandoesinger at gmail.com <mailto:stefandoesinger at gmail.com>> wrote:

>     > Yes. My hope was that Winelib could be used to help port a legacy
>     > Windows CE 4.x application to Linux (ARM, though I am testing on
>     > x86 right now). Initially I could try compiling on Windows and
>     > running it on Linux, but the real goal would be to port the
>     > application in stages, so changing a few modules at a time to use
>     > Linux APIs while leaving some parts using the Win32 (and MFC) APIs.
>     > Eventually there would be no need for Winelib but I'd expect that
>     > porting all of the code at once would resulting in a lot more
>     > debugging effort because changes would not be localised.
>     Hmm yeah, that sounds like a task where you need winelib. Unfortunately
>     winelib isn't something that gets used a lot, and even less so with C++.
> 
>     Also keep in mind that Wine doesn't target Windows CE applications, so
>     you'll have to invest a lot of time into bridging Windows CE <-> Win32
>     differences.
> 

You could give it a try running it directly in WineCE, you can find it here: https://github.com/AndreRH/wine/tree/winece
BTW, are we talking about python for CE?





More information about the wine-devel mailing list