mike.king at pvxplus.com
Mon Feb 20 13:33:42 CST 2006
Thanks for all the help.
Seems to me that wine and winelib may not be the way for us to go.
We have a functioning application development language that runs on Windows plus virtually
all flavours of Unix/Linux but the only GUI implementation is Windows. We were looking
for an easy way to port the environment to 'X' windows without having to recode all the
>From your response you mentioned that is was possible to create a wrapper -- that might
work since I have no problem changing the way 'winmain' gets it parameters since this will
be a 'wine' unique implementation.
BTW: Somebody should change the description about notepad and mention that it actually is
a script file.
----- Original Message -----
From: "Segin" <segin2005 at gmail.com>
To: <mike.king at pvxplus.com>
Cc: "Joris Huizer" <jorishuizer at planet.nl>; <wine-devel at winehq.org>
Sent: Sunday, February 19, 2006 7:33 PM
Subject: Re: Winelib
> Joris Huizer wrote:
> > Michael King wrote:
> >> Hi,
> >> I'm looking into porting our graphic application language to Linux
> >> usign WineLib but
> >> having some trouble just getting started.
> >> I downloaded and installed wine-0.9.8-SuSELinux92.i586.rpm for our
> >> SUSE 9.2 system and
> >> then tried to create the 'notepad' program using the instructions
> >> given on
> >> http://www.winehq.org/site/docs/winelib-guide/winelib-getting-started .
> >> Unfortunately after following the instructions I ended up with a
> >> 'notepad.exe.so' not a
> >> simple ./notepad file.
> >> Our goal is to create a true executable file, not a ".so" library
> >> that needs to be invoked
> >> using Wine.
> >> Have the build instructions changed?
> >> Michael F. King
> >> PVX Plus Technologies, Ltd.
> >> www.pvxplus.com
> > With winelib, there is no way to make a "true" executable without any
> > dependencies on wine;
> > you could make a wrapper script so that the user does not have to type
> > 'wine' anymore - this is what winelib used to do, which made the
> > 'notepad' file in the documentation (that part of the documentation is
> > a little out dated I'm affraid)
> > HTH,
> > Joris
> It would also be suitable to make a psudeo-main which calls all the Wine
> init functions, sets up the wineserver, etc., but doing this in my own
> experience has produced a semiworking loader which is unable to pass any
> arguments to the WinMain() funtion of the program. (the passed arguments
> are literally 0)
> You're barking up the wrong tree, and by the way, the little './notepad'
> was a shell script thgat used the 'wine' loader to load the
> notepad.exe.so file.
More information about the wine-devel