To compile and run Wine, you must have one of the following:
Linux version 2.0.36 or above
- FreeBSD 6.2 or later
- Solaris x86 2.5 or later
+ FreeBSD 6.3 or later
+ Solaris x86 9 or later
NetBSD-current
Mac OS X 10.4 or later
it's best to have a current kernel such as 2.4.x or 2.6.x.
FreeBSD info:
- Wine should build on FreeBSD 5.x, but versions before FreeBSD 7.0 will
- generally not work properly. FreeBSD 6.3 has patches available to allow
- Wine to run. See <http://wiki.freebsd.org/Wine> for more information.
-
- More information can be found in the FreeBSD ports tree at
- <ftp://ftp.freebsd.org/pub/FreeBSD/ports/ports/emulators/wine/>.
+ Wine will generally not work properly on versions before FreeBSD
+ 6.3 or 7.0, and FreeBSD 6.3 has additional patches available. See
+ <http://wiki.freebsd.org/Wine> for more information.
Solaris info:
You will most likely need to build Wine with the GNU toolchain
Supported file systems:
- Wine should run on most file systems. However, Wine will fail to start
- if umsdos is used for the /tmp directory. A few compatibility problems have
- also been reported using files accessed through Samba. Also, NTFS does not
- provide all the file system features needed by some applications.
- Using a native Linux file system such as ext3 is recommended.
+ Wine should run on most file systems. A few compatibility problems
+ have also been reported using files accessed through Samba. Also,
+ NTFS does not provide all the file system features needed by some
+ applications. Using a native Linux file system such as ext3 is
+ recommended.
Basic requirements:
You need to have the X11 development include files installed
(called xlib6g-dev in Debian and XFree86-devel in Red Hat).
-Build tool requirements:
- On x86 Systems gcc >= 2.7.2 is required.
- Versions earlier than 2.7.2.3 may have problems when certain files
- are compiled with optimization, often due to problems with header file
- management.
-
Of course you also need "make" (most likely GNU make).
You also need flex version 2.5 or later and bison.
Optional support libraries:
- Run ./configure --verbose to see the optional libraries that could
- be used but aren't found on your system.
+ Configure will display notices when optional libraries are not found
+ on your system. See http://wiki.winehq.org/Recommended_Packages for
+ hints about the packages you should install.
+ On 64-bit platforms you have to make sure to install the 32-bit
+ versions of these libraries; see http://wiki.winehq.org/WineOn64bit
+ for details.
4. COMPILATION
bunzip2 -c patch-file | patch -p1
where "patch-file" is the name of the patch file (something like
-wine-0.9.x.diff.bz2). You can then re-run "./configure", and then
+wine-1.0.x.diff.bz2). You can then re-run "./configure", and then
run "make depend && make".
first. Try either "dpkg -r wine" or "rpm -e wine" or "make uninstall"
before installing.
-See the Support area at http://www.winehq.org/ for configuration
-hints.
-
-In case of library loading errors
-(e.g. "Error while loading shared libraries: libntdll.so"), make sure
-to add the library path to /etc/ld.so.conf and run ldconfig as root.
+Once installed, you can run the "winecfg" configuration tool. See the
+Support area at http://www.winehq.org/ for configuration hints.
6. RUNNING PROGRAMS
When invoking Wine, you may specify the entire path to the executable,
or a filename only.
-For example: to run Solitaire:
+For example: to run Notepad:
- wine sol (using the search Path as specified in
- wine sol.exe the config file to locate the file)
+ wine notepad (using the search Path as specified in
+ wine notepad.exe the config file to locate the file)
- wine c:\\windows\\sol.exe (using DOS filename syntax)
+ wine c:\\windows\\notepad.exe (using DOS filename syntax)
- wine /usr/windows/sol.exe (using Unix filename syntax)
+ wine ~/.wine/drive_c/windows/notepad.exe (using Unix filename syntax)
- wine sol.exe /parameter1 -parameter2 parameter3
+ wine notepad.exe /parameter1 -parameter2 parameter3
(calling program with parameters)
Wine is not yet complete, so several programs may crash. In that crash
IRC: Online help is available at channel #WineHQ on irc.freenode.net.
-GIT: The current Wine development tree is available through GIT.
+Git: The current Wine development tree is available through Git.
Go to http://www.winehq.org/site/git for more information.
Mailing lists:
projects / wine / blobdiff