Wine is free software, released under the GNU LGPL; see the file
LICENSE for the details.
+
2. QUICK START
Whenever you compile from source, it is recommended to use the Wine
./tools/wineinstall
-Run programs as "wine [options] program". For more information and
-problem resolution, read the rest of this file, the Wine man page, and
+Run programs as "wine program". For more information and problem
+resolution, read the rest of this file, the Wine man page, and
especially the wealth of information found at http://www.winehq.org.
+
3. REQUIREMENTS
To compile and run Wine, you must have one of the following:
Linux version 2.0.36 or above
- FreeBSD 5.3 or later
+ FreeBSD 6.2 or later
Solaris x86 2.5 or later
NetBSD-current
+ Mac OS X 10.4 or later
As Wine requires kernel-level thread support to run, only the operating
-systems mentioned above are supported.
-Other operating systems which support kernel threads may be supported
-in the future.
+systems mentioned above are supported. Other operating systems which
+support kernel threads may be supported in the future.
Linux info:
While Linux 2.2.x should still work and Linux 2.0.x may still work
(older 2.0.x versions had thread-related crashes),
- it's best to have a current kernel such as 2.4.x.
+ it's best to have a current kernel such as 2.4.x or 2.6.x.
FreeBSD info:
- Wine should build on FreeBSD 4.x and FreeBSD 5.x, but versions before
- FreeBSD 5.3 will generally not work properly.
+ Wine should build on FreeBSD 5.x, but versions before FreeBSD 6.2 will
+ generally not work properly.
More information can be found in the FreeBSD ports tree at
<ftp://ftp.freebsd.org/pub/FreeBSD/ports/ports/emulators/wine/>.
Make sure you have the USER_LDT, SYSVSHM, SYSVSEM, and SYSVMSG options
turned on in your kernel.
+Mac OS X info:
+ You need Xcode 2.4 or later to build properly on x86.
Supported file systems:
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. pgcc currently doesn't work with Wine. The cause of this problem
- is unknown.
+ 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:
- If you want CUPS printing support, please install both cups and cups-devel
- packages.
- Install the libxml2 package to get a functional msxml implementation.
+ Run ./configure --verbose to see the optional libraries that could
+ be used but aren't found on your system.
+
4. COMPILATION
top-level directory of the release (the one containing this README
file). Then do a "make clean", and patch the release with:
- gunzip -c patch-file | patch -p1
+ bunzip2 -c patch-file | patch -p1
where "patch-file" is the name of the patch file (something like
-Wine-yymmdd.diff.gz). You can then re-run "./configure", and then
+wine-0.9.x.diff.bz2). You can then re-run "./configure", and then
run "make depend && make".
+
5. SETUP
Once Wine has been built correctly, you can do "make install"; this
(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.
+
6. RUNNING PROGRAMS
When invoking Wine, you may specify the entire path to the executable,
wine sol.exe /parameter1 -parameter2 parameter3
(calling program with parameters)
-Note: the path of the file will also be added to the path when
- a full name is supplied on the commandline.
-
-Wine is not yet complete, so several programs may crash. Provided you set up
-winedbg correctly according to documentation/debugger.sgml, you will be dropped
-into a debugger so that you can investigate and fix the problem.
-For more information on how to do this, please read the file
-documentation/debugging.sgml.
+Wine is not yet complete, so several programs may crash. In that crash
+you will be dropped into the debugger so that you can investigate and
+fix the problem. For more information on how to do this, please check
+the debugging section of the Wine Developer's Guide.
-You should backup all your important files that you give Wine access
-to, or use a special Wine copy of them, as there have been some cases
-of users reporting file corruption. Do NOT run Explorer, for instance,
-if you don't have a proper backup, as it renames/cripples several
-directories sometimes. Not even other MS apps such as e.g. Messenger are safe,
-as they launch Explorer somehow. This particular corruption (!$!$!$!$.pfr)
-can at least partially be fixed by using
-http://home.nexgo.de/andi.mohr/download/decorrupt_explorer
7. GETTING MORE INFORMATION
Please search the bugzilla database to check whether your
problem is already found before posting a bug report. You can
also post bug reports to comp.emulators.ms-windows.wine.
- Please read the file documentation/bugs.sgml to see what
- information is required.
IRC: Online help is available at channel #WineHQ on irc.freenode.net.
-CVS: The current Wine development tree is available through CVS.
- Go to http://www.winehq.org/cvs for more information.
+GIT: The current Wine development tree is available through GIT.
+ Go to http://www.winehq.org/site/git for more information.
Mailing lists:
- There are several mailing lists for Wine developers; see
- http://www.winehq.org/forums for more information.
+ There are several mailing lists for Wine users and developers;
+ see http://www.winehq.org/forums for more information.
+
+Wiki: The Wine Wiki is located at http://wiki.winehq.org
If you add something, or fix a bug, please send a patch (in 'diff -u'
format) to wine-patches@winehq.org list for inclusion in the next