1
- 1. INTRODUCTION
1
+ ## INTRODUCTION
2
2
3
3
Wine is a program which allows running Microsoft Windows programs
4
4
(including DOS, Windows 3.x, Win32, and Win64 executables) on Unix.
@@ -11,163 +11,160 @@ Wine is free software, released under the GNU LGPL; see the file
11
11
LICENSE for the details.
12
12
13
13
14
- 2. QUICK START
14
+ ## QUICK START
15
15
16
16
From the top-level directory of the Wine source (which contains this file),
17
17
run:
18
18
19
+ ```
19
20
./configure
20
21
make
22
+ ```
21
23
22
24
Then either install Wine:
23
25
26
+ ```
24
27
make install
28
+ ```
25
29
26
30
Or run Wine directly from the build directory:
27
31
32
+ ```
28
33
./wine notepad
34
+ ```
29
35
30
- Run programs as " wine program". For more information and problem
36
+ Run programs as ` wine program ` . For more information and problem
31
37
resolution, read the rest of this file, the Wine man page, and
32
38
especially the wealth of information found at https://www.winehq.org .
33
39
34
40
35
- 3. REQUIREMENTS
41
+ ## REQUIREMENTS
36
42
37
43
To compile and run Wine, you must have one of the following:
38
44
39
- Linux version 2.0.36 or later
40
- FreeBSD 8.0 or later
41
- Solaris x86 9 or later
42
- NetBSD-current
43
- Mac OS X 10.8 or later
45
+ - Linux version 2.6.22 or later
46
+ - FreeBSD 12.4 or later
47
+ - Solaris x86 9 or later
48
+ - NetBSD-current
49
+ - Mac OS X 10.8 or later
44
50
45
51
As Wine requires kernel-level thread support to run, only the operating
46
52
systems mentioned above are supported. Other operating systems which
47
53
support kernel threads may be supported in the future.
48
54
49
- FreeBSD info:
50
- Wine will generally not work properly on versions before FreeBSD 8.0.
55
+ ** FreeBSD info** :
51
56
See https://wiki.freebsd.org/Wine for more information.
52
57
53
- Solaris info:
58
+ ** Solaris info** :
54
59
You will most likely need to build Wine with the GNU toolchain
55
60
(gcc, gas, etc.). Warning : installing gas does * not* ensure that it
56
61
will be used by gcc. Recompiling gcc after installing gas or
57
62
symlinking cc, as and ld to the gnu tools is said to be necessary.
58
63
59
- NetBSD info:
64
+ ** NetBSD info** :
60
65
Make sure you have the USER_LDT, SYSVSHM, SYSVSEM, and SYSVMSG options
61
66
turned on in your kernel.
62
67
63
- Mac OS X info:
68
+ ** Mac OS X info** :
64
69
You need Xcode/Xcode Command Line Tools or Apple cctools. The
65
70
minimum requirements for compiling Wine are clang 3.8 with the
66
71
MacOSX10.10.sdk and mingw-w64 v8. The MacOSX10.14.sdk and later can
67
72
only build wine64.
68
73
69
-
70
- Supported file systems:
74
+ ** Supported file systems** :
71
75
Wine should run on most file systems. A few compatibility problems
72
76
have also been reported using files accessed through Samba. Also,
73
77
NTFS does not provide all the file system features needed by some
74
78
applications. Using a native Unix file system is recommended.
75
79
76
- Basic requirements:
80
+ ** Basic requirements** :
77
81
You need to have the X11 development include files installed
78
82
(called xorg-dev in Debian and libX11-devel in Red Hat).
79
-
80
- Of course you also need "make" (most likely GNU make).
81
-
83
+ Of course you also need make (most likely GNU make).
82
84
You also need flex version 2.5.33 or later and bison.
83
85
84
- Optional support libraries:
86
+ ** Optional support libraries** :
85
87
Configure will display notices when optional libraries are not found
86
88
on your system. See https://wiki.winehq.org/Recommended_Packages for
87
89
hints about the packages you should install. On 64-bit platforms,
88
90
you have to make sure to install the 32-bit versions of these
89
91
libraries.
90
92
91
93
92
- 4. COMPILATION
94
+ ## COMPILATION
93
95
94
96
To build Wine, do:
95
97
98
+ ```
96
99
./configure
97
100
make
101
+ ```
98
102
99
103
This will build the program "wine" and numerous support libraries/binaries.
100
104
The program "wine" will load and run Windows executables.
101
105
The library "libwine" ("Winelib") can be used to compile and link
102
106
Windows source code under Unix.
103
107
104
- To see compile configuration options, do ./configure --help.
108
+ To see compile configuration options, do ` ./configure --help ` .
105
109
106
110
For more information, see https://wiki.winehq.org/Building_Wine
107
111
108
112
109
- 5. SETUP
113
+ ## SETUP
110
114
111
- Once Wine has been built correctly, you can do " make install" ; this
115
+ Once Wine has been built correctly, you can do ` make install ` ; this
112
116
will install the wine executable and libraries, the Wine man page, and
113
117
other needed files.
114
118
115
119
Don't forget to uninstall any conflicting previous Wine installation
116
- first. Try either " dpkg -r wine" or " rpm -e wine" or " make uninstall"
120
+ first. Try either ` dpkg -r wine ` or ` rpm -e wine ` or ` make uninstall `
117
121
before installing.
118
122
119
- Once installed, you can run the " winecfg" configuration tool. See the
123
+ Once installed, you can run the ` winecfg ` configuration tool. See the
120
124
Support area at https://www.winehq.org/ for configuration hints.
121
125
122
126
123
- 6. RUNNING PROGRAMS
127
+ ## RUNNING PROGRAMS
124
128
125
129
When invoking Wine, you may specify the entire path to the executable,
126
130
or a filename only.
127
131
128
- For example: to run Notepad:
132
+ For example, to run Notepad:
129
133
130
- wine notepad (using the search Path as specified in
131
- wine notepad.exe the registry to locate the file)
134
+ ```
135
+ wine notepad (using the search Path as specified in
136
+ wine notepad.exe the registry to locate the file)
132
137
133
- wine c:\\windows\\notepad.exe (using DOS filename syntax)
138
+ wine c:\\windows\\notepad.exe (using DOS filename syntax)
134
139
135
- wine ~/.wine/drive_c/windows/notepad.exe (using Unix filename syntax)
140
+ wine ~/.wine/drive_c/windows/notepad.exe (using Unix filename syntax)
136
141
137
- wine notepad.exe readme.txt (calling program with parameters)
142
+ wine notepad.exe readme.txt (calling program with parameters)
143
+ ```
138
144
139
145
Wine is not perfect, so some programs may crash. If that happens you
140
146
will get a crash log that you should attach to your report when filing
141
147
a bug.
142
148
143
149
144
- 7. GETTING MORE INFORMATION
150
+ ## GETTING MORE INFORMATION
145
151
146
- WWW: A great deal of information about Wine is available from WineHQ at
152
+ - ** WWW** : A great deal of information about Wine is available from WineHQ at
147
153
https://www.winehq.org/ : various Wine Guides, application database,
148
154
bug tracking. This is probably the best starting point.
149
155
150
- FAQ: The Wine FAQ is located at https://www.winehq.org/FAQ
156
+ - ** FAQ** : The Wine FAQ is located at https://www.winehq.org/FAQ
157
+
158
+ - ** Wiki** : The Wine Wiki is located at https://wiki.winehq.org
151
159
152
- Wiki: The Wine Wiki is located at https://wiki .winehq.org
160
+ - ** Gitlab ** : Wine development is hosted at https://gitlab .winehq.org
153
161
154
- Mailing lists:
162
+ - ** Mailing lists** :
155
163
There are several mailing lists for Wine users and developers;
156
164
see https://www.winehq.org/forums for more information.
157
165
158
- Bugs: Report bugs to Wine Bugzilla at https://bugs.winehq.org
166
+ - ** Bugs** : Report bugs to Wine Bugzilla at https://bugs.winehq.org
159
167
Please search the bugzilla database to check whether your
160
168
problem is already known or fixed before posting a bug report.
161
169
162
- IRC: Online help is available at channel #WineHQ on irc.libera.chat.
163
-
164
- Git: The current Wine development tree is available through Git.
165
- Go to https://www.winehq.org/git for more information.
166
-
167
- If you add something, or fix a bug, please send a patch (preferably
168
- using git-format-patch) to the wine-devel@winehq.org list for
169
- inclusion in the next release.
170
-
171
- --
172
- Alexandre Julliard
173
- julliard@winehq.org
170
+ - ** IRC** : Online help is available at channel ` #WineHQ ` on irc.libera.chat.
0 commit comments