This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
planetforeveronlinuxusingwinemanual [2012/11/04 18:28] rockfire |
planetforeveronlinuxusingwinemanual [2013/01/22 12:10] (current) rockfire [Setting Up Wine] |
||
---|---|---|---|
Line 11: | Line 11: | ||
- Install Wine build dependencies. On Ubuntu, this is easy :-<code>sudo apt-get build-dep wine1.5</code> | - Install Wine build dependencies. On Ubuntu, this is easy :-<code>sudo apt-get build-dep wine1.5</code> | ||
- | - Download the latest wine from http://sourceforge.net/projects/wine/files/Source/. At the time of writing this is 1.5.16, although the patch should work on most versions since 1.1.39, sometimes with tiny bits of tweaking. Grab the file named wine-1.5.10.tar.bz2 | + | - Download the latest wine from http://sourceforge.net/projects/wine/files/Source/. At the time of writing this is 1.5.17, although the patch should work on most versions since 1.1.39, sometimes with tiny bits of tweaking. Grab the file named wine-1.5.17.tar.bz2 |
- | - Copy and paste the following into a file on your desktop called ee.patch.<code>gedit ~/Desktop/ee.patch</code>And now the content of this file ..<code>diff -crB wine-1.5.16.orig/dlls/wined3d/device.c wine-1.5.16/dlls/wined3d/device.c | + | - Copy and paste the following into a file on your desktop called ee.patch.<code>gedit ~/Desktop/ee.patch</code>And now the content of this file ..<code>diff -crB wine-1.5.17.orig/dlls/wined3d/device.c wine-1.5.17/dlls/wined3d/device.c |
- | *** wine-1.5.16.orig/dlls/wined3d/device.c 2012-10-26 19:12:40.000000000 +0100 | + | *** wine-1.5.17.orig/dlls/wined3d/device.c 2012-10-26 19:12:40.000000000 +0100 |
- | --- wine-1.5.16/dlls/wined3d/device.c 2012-11-04 14:17:29.457321843 +0000 | + | --- wine-1.5.17/dlls/wined3d/device.c 2012-11-04 14:17:29.457321843 +0000 |
*************** | *************** | ||
*** 4990,4997 **** | *** 4990,4997 **** | ||
Line 84: | Line 84: | ||
make</code> This will take a while. If you have a multicore machine, you can speed it up considerably by using "make -j 8" for example to use 8 threads. | make</code> This will take a while. If you have a multicore machine, you can speed it up considerably by using "make -j 8" for example to use 8 threads. | ||
- Now install Wine. This will install to /opt/games/wine-ee.<code>sudo make install</code> | - Now install Wine. This will install to /opt/games/wine-ee.<code>sudo make install</code> | ||
- | - If you are building on a 32 bit VM for a 64 bit host as described above, then this is the point you want to copy all of /opt/games/wine-ee from the VM to your bit 64 bit, otherwise, skip to step 7.<code>tar czf ~/wine-ee-32bit.tgz /opt/games/wine-ee</code> Copy this file from the VM to the target and extract it in the root of your file system so all the files end up in the same place (/opt/games/wine-ee). | + | - If you are building on a 32 bit VM for a 64 bit host as described above, then this is the point you want to copy all of /opt/games/wine-ee from the VM to your bit 64 bit, otherwise, skip to step 8.<code>tar czf ~/wine-ee-32bit.tgz /opt/games/wine-ee</code> Copy this file from the VM to the target and extract it in the root of your file system so all the files end up in the same place (/opt/games/wine-ee). |
- Make sure "winetricks" is installed. You can get it from here - http://wiki.winehq.org/winetricks/ - or just install the one provided with your distributions if available :-<code>sudo apt-get install winetricks</code> | - Make sure "winetricks" is installed. You can get it from here - http://wiki.winehq.org/winetricks/ - or just install the one provided with your distributions if available :-<code>sudo apt-get install winetricks</code> | ||
- Now you need to set up a new WINEPREFIX. Rather than interfere with the default $HOME/.wine prefix, we will create a fresh one.<code># NOTE - You will have to run these 2 commands again if you open a new terminal | - Now you need to set up a new WINEPREFIX. Rather than interfere with the default $HOME/.wine prefix, we will create a fresh one.<code># NOTE - You will have to run these 2 commands again if you open a new terminal |