I'm making efforts to let a program which is compiled with winelib run
with
wine uninstalled. This program was for windows initially, I managed to compile it under Linux(Redhat) with winelib. Now I have got the files "program" and "program.exe.so" and they run well on a PC with wine installed, but I want it to run with wine uninstalled.
This will not work. Why would you try to do that anyhow?
I'm guessing it's because he wants to distribute the Winelib app. The folks installing probably won't have Wine on the system.
Which brings up a good point, is there an easy way to distribute one? What comes to mind would be some way to adapt the Wine binary distributions (RPM's, .tgz's) to also install an application at the same time.
--------------- Brian Vincent Copper Mountain Telecom vincentb@coppercolorado.com
On January 5, 2004 11:32 am, Brian Vincent (C) wrote:
Which brings up a good point, is there an easy way to distribute one? What comes to mind would be some way to adapt the Wine binary distributions (RPM's, .tgz's) to also install an application at the same time.
This is not a problem: your app has lots of dependencies anyway, wine will just be one of them. Gnome apps require the Gnome libs, they don't package those with each app, do they? :)
Hi Dimi, --- "Dimitrie O. Paun" dpaun@rogers.com wrote:
This is not a problem: your app has lots of dependencies anyway, wine will just be one of them. Gnome apps require the Gnome libs, they don't package those with each app, do they? :)
Right but...There are going to be problems with this untill WINE 1.0. If the WINE server protocall or API changes the app will break. For the time being the only solution would be to ship WINE with the app. Once we have a 1.0 release of winelib this wont be a issue for any applications linked to 1.x
Thanks Steven
__________________________________ Do you Yahoo!? Find out what made the Top Yahoo! Searches of 2003 http://search.yahoo.com/top2003
On Mon, 05 Jan 2004 09:57:34 -0800, Steven Edwards wrote:
Right but...There are going to be problems with this untill WINE 1.0. If the WINE server protocall or API changes the app will break. For the time being the only solution would be to ship WINE with the app. Once we have a 1.0 release of winelib this wont be a issue for any applications linked to 1.x
Why? WineLib apps don't RPC to the wineserver directly, they go via the win32 API which is stable. If the wineserver protocol changes, that's hidden behind the dlls right?