Wineinstall
From Wine-Wiki
[edit] Introduction
T. Spear [Apr 06] noted: ./tools/wineinstall is deprecated and will be removed shortly. Ed: This would be a good indication that you should not be using it.
wineinstall was written to make it easy to completely compile and install from Wine source code. D. Kegel [Aug 06]: It seems to be designed to avoid problem reports from people who don't really know what they're doing, i.e. who don't know what sudo is, who don't realize it's bad to try installing wine from source if you already have it installed as a package, who don't have all the needed packages installed, etc. wine archive
A developer [Aug 06] queried about its status and the resulting discussion seems to allow for it living a little longer. wine archive [But since wine has a new release every 2 weeks, that was a very, very long time ago - dont use it unless a developer recommends it]
[edit] Using wineinstall
After extracting the Wine source code, change (or cd) to the main directory of it and then run (as user):
$ ./tools/wineinstall
Wine will be compiled, installed and then configured (either by providing access to a Windows partition or by creating a properly configured no-windows directory environment).
Cleaning up a mess
T. Spear [in giving advice to clearing remnants of a wineinstall Apr 06]: Your compile problem may have been caused by running [wineinstall]. Please (since you have already run ./tools/wineinstall) do this:
- sudo make uninstall
- make distclean
- rm -rf ~/.wine
- sudo rm -rf ~/.wine
- ./configure
- make dep
- make
- sudo make install
That should kill any remnants of wine lying around the system, and rebuild it from scratch. Once it is installed, just run wineprefixcreate and winecfg to configure and make wine ready for use. Then run your program with wine <program_name> and hope everything works as it does under windows.
