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
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
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.
Segin/Joris 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 GUI interfaces.
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. Regards Mike ----- Original Message ----- From: "Segin" <segin2005(a)gmail.com> To: <mike.king(a)pvxplus.com> Cc: "Joris Huizer" <jorishuizer(a)planet.nl>; <wine-devel(a)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.
Michael King wrote:
Segin/Joris
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 GUI interfaces.
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.
Regards Mike
----- Original Message ----- From: "Segin" <segin2005(a)gmail.com> To: <mike.king(a)pvxplus.com> Cc: "Joris Huizer" <jorishuizer(a)planet.nl>; <wine-devel(a)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.
It would be best to take a look at the source code to the wine-preloader program. It will shed light onto the task at hand.
On Tuesday 21 February 2006 06:33, Michael King wrote:
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 GUI interfaces.
Why should it matter that the program builds to a ".so" file and has to be launched via a script? Even if it only involved libraries, nobody links to static libraries anymore so you would still need external libraries. -- Troy Rollo - wine(a)troy.rollo.name
Troy Thanks for your comments. The issue with using a 'script' file versus a true 'executable' is really a matter of marketing. Our Windows product does run under 'wine' however we have clients that don't consider that acceptable. We are looking at having a "True" X-Windows / Unix / Linux implementation. While my background is technical, I understand that much of a products acceptability is based on market perception. 'Wine' unfortunately is perceived as a emulation, and while that is far from the truth, it still means people will shy away from it as a solution. That being said, if we can find a way to launch a 'winelib' developed version of our system we feel we can prove that 'wine' is the way to go. Using dynamic (.so) libraries is a good concept -- I am just trying to find a way to make a 'wine' version of our product viable for our clients. Sad isn't it ... we may have to look at alternatives only to satsify the marketplace.
From what I have seen so far 'wine' is a great product, I just need to convince others that it's the solution to their requirements.
Regards, Mike King ----- Original Message ----- From: "Troy Rollo" <wine(a)troy.rollo.name> To: <wine-devel(a)winehq.org> Cc: "Michael King" <mike.king(a)pvxplus.com> Sent: Monday, February 20, 2006 8:30 PM Subject: Re: Winelib
On Tuesday 21 February 2006 06:33, Michael King wrote:
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 GUI interfaces.
Why should it matter that the program builds to a ".so" file and has to be launched via a script? Even if it only involved libraries, nobody links to static libraries anymore so you would still need external libraries. -- Troy Rollo - wine(a)troy.rollo.name
Michael King wrote:
Troy
Thanks for your comments. The issue with using a 'script' file versus a true 'executable' is really a matter of marketing.
Than you'll have to do like my father did. ;-) Look in the source tree, You'll see that wine is just wineloader and the real wine is wine-kthread/wine-pthread. Hack on wineloader, first call it what you like than you can hard-code the Winlib to load. Don't forget to force WINEPREFIX to your installation so it will not conflict with the user's regular wine. And the source to that "Mywineloader" will have to be served with code. (LGPL) Free Life Boaz
Boaz Thanks -- that will get me started and supplying the code is not an issue. Regards Mike ----- Original Message ----- From: "Boaz Harrosh" <wine(a)electrozaur.com> To: "Michael King" <mike.king(a)pvxplus.com> Cc: <wine-devel(a)winehq.org> Sent: Tuesday, February 21, 2006 3:13 AM Subject: Re: Winelib
Michael King wrote:
Troy
Thanks for your comments. The issue with using a 'script' file versus a true 'executable' is really a matter of marketing.
Than you'll have to do like my father did. ;-) Look in the source tree, You'll see that wine is just wineloader and the real wine is wine-kthread/wine-pthread. Hack on wineloader, first call it what you like than you can hard-code the Winlib to load. Don't forget to force WINEPREFIX to your installation so it will not conflict with the user's regular wine. And the source to that "Mywineloader" will have to be served with code. (LGPL)
Free Life Boaz
participants (5)
-
Boaz Harrosh -
Joris Huizer -
Michael King -
Segin -
Troy Rollo