[Wine] Re: Standalone Wine for console Win32 executables

doh123 wineforum-user at winehq.org
Wed Apr 13 10:01:32 CDT 2011


the problem with just taking a minimal Wine install.. is assuming that the dependencies it needs are already installed on the machine its going to be running on.... i'm talking about stuff like freetype or libjpeg or whatever, not just Wine.

If you just want Wine, you can always build from source setting a different prefix (./configure --prefix=<where to install wine>) for install then when you do the make install it will install it to the folder you specified as a prefix, and you have just Wine in that folder and usable now... even copied from machine to machine, so you'd probably just want to add it as is in a Wine folder along with your program.. then a script that launches by adding the CurrentFolder/Wine/bin to the front of $PATH, then doing wine name.exe to launch.... but you can run into tons of problems between distros and what dependencies they have and where they might put them, and what versions they are.

If you really want to make sure it will never have a problem, you need to get copies of all the libraries that are dependencies and have portable copies of them, and set LD library paths and stuff so it uses the right ones and junk like that, which can get very complicated and confusing.







More information about the wine-users mailing list