Corel shipped in fact windows executables with a custom version of Wine. Other companies did winelib ports of their apps. They then recompiled the app using winelib. In theory you take the source and recompile it but usually it is much more work becaues of compiler differences and so on. The disadvantage of winelib binary is that it still needs Wine.
If you want to be independant of wine and it isn't much work to port the app over to GTK and other native stuff, do it. (Gtk works fine on windows too ..)
Roderick Colenbrander
On Thursday 17 April 2003 19:36, Christopher Thielen wrote:
Didn't Corel port Windows apps to Wine so they ran with Corel's special version of Wine? MusicMatch did the same thing with their program. What did they do there, or is it less work to port the app to GTK+?
On Wed, 2003-04-16 at 10:32, Roderick Colenbrander wrote:
When you would recompile your app using winelib, it becomes a so called "winelib" binary. The app still depends on Wine, the only difference is that it isn't a native windows binary anymore. Something an MFC app on Linux is a bit tricky, since you would need to build MFC for Linux (using the MFC source which is shipped with some versions of VStudio). Building it can be hard and not sure how the license is...
I wouldn't port the app to winelib in your case since the only reason you are doing it is not to depend on Wine. Having it not depend on wine is not possible.
Roderick Colenbrander
Hello, I've written an application in MFC which runs beautifully in wine. I'd like to distribute a Winelib version, so Unix users don't need wine. Can I recompile MFC applications with Winelib? Is this possible?
-- chris (chris@luethy.net)