To read all comments associated with this story, please click here.
It's not running "under WINE" but using libwine. If you have the Win32 source code, the libwine library provides a native implementation of that API for Linux/UNIX. Thus, you can compile the code as a native application and do away with the overhead of WINE itself.
While I have not done it myself, I have talked to several people that have ported Win32 apps using libwine, and the general consensus is that it is very straight-forward and pretty quick to do. I suspect, for example, if Intuit wanted to make QuickBooks for Linux they could put 2 guys on it and turn it out in a week or two and maintain a common code base between Windows and Linux. Not that they will. Intuit gets thousands of requests for it and their policy is to explicitly ignore all user requests for porting their applications.
Nope.
It's simply a self-contained version of Wine. No Winelib or anything.
From WWN 314,
http://www.winehq.com/?issue=314http://www.winehq.com/?issue=314#Pi...
=================
Many people assume that when porting a Windows app to Linux using Wine, the best thing to do is link Winelib into the application to create a native Linux application. Not so! It's just as effective, and a heck of a lot easier, to run the same binary on both Windows and Wine. So that's what the Picasa team did. Picasa for Linux uses slightly different text messages, but the .exe file is identical for both Windows and Linux.
==================







Member since:
2005-07-06
"ported"? wtf? Making an app run under Wine is *not* 'porting' it. If that is the case, then I've ported all kinds of programs to linux