@@ -27,7 +27,7 @@ Also note that GPTKv2 is currently still in its beta phase; bugs and hiccups are
27
27
28
28
# wine
29
29
30
- # 1. INTRODUCTION
30
+ ## 1. INTRODUCTION
31
31
32
32
Wine is a program which allows running Microsoft Windows programs
33
33
(including DOS, Windows 3.x, Win32, and Win64 executables) on Unix.
@@ -40,7 +40,7 @@ Wine is free software, released under the GNU LGPL; see the file
40
40
LICENSE for the details.
41
41
42
42
43
- # 2. QUICK START
43
+ ## 2. QUICK START
44
44
45
45
From the top-level directory of the Wine source (which contains this file),
46
46
run:
@@ -63,7 +63,7 @@ resolution, read the rest of this file, the Wine man page, and
63
63
especially the wealth of information found at https://www.winehq.org .
64
64
65
65
66
- # 3. REQUIREMENTS
66
+ ## 3. REQUIREMENTS
67
67
68
68
To compile and run Wine, you must have one of the following:
69
69
@@ -77,50 +77,50 @@ As Wine requires kernel-level thread support to run, only the operating
77
77
systems mentioned above are supported. Other operating systems which
78
78
support kernel threads may be supported in the future.
79
79
80
- ## FreeBSD info:
80
+ ### FreeBSD info:
81
81
Wine will generally not work properly on versions before FreeBSD 8.0.
82
82
See https://wiki.freebsd.org/Wine for more information.
83
83
84
- ## Solaris info:
84
+ ### Solaris info:
85
85
You will most likely need to build Wine with the GNU toolchain
86
86
(gcc, gas, etc.). Warning : installing gas does * not* ensure that it
87
87
will be used by gcc. Recompiling gcc after installing gas or
88
88
symlinking cc, as and ld to the gnu tools is said to be necessary.
89
89
90
- ## NetBSD info:
90
+ ### NetBSD info:
91
91
Make sure you have the USER_LDT, SYSVSHM, SYSVSEM, and SYSVMSG options
92
92
turned on in your kernel.
93
93
94
- ## Mac OS X info:
94
+ ### Mac OS X info:
95
95
You need Xcode/Xcode Command Line Tools or Apple cctools. The
96
96
minimum requirements for compiling Wine are clang 3.8 with the
97
97
MacOSX10.10.sdk and mingw-w64 v8. The MacOSX10.14.sdk and later can
98
98
only build wine64.
99
99
100
100
101
- ## Supported file systems:
101
+ ### Supported file systems:
102
102
Wine should run on most file systems. A few compatibility problems
103
103
have also been reported using files accessed through Samba. Also,
104
104
NTFS does not provide all the file system features needed by some
105
105
applications. Using a native Unix file system is recommended.
106
106
107
- ## Basic requirements:
107
+ ### Basic requirements:
108
108
You need to have the X11 development include files installed
109
109
(called xorg-dev in Debian and libX11-devel in Red Hat).
110
110
111
111
Of course you also need "make" (most likely GNU make).
112
112
113
113
You also need flex version 2.5.33 or later and bison.
114
114
115
- ## Optional support libraries:
115
+ ### Optional support libraries:
116
116
Configure will display notices when optional libraries are not found
117
117
on your system. See https://wiki.winehq.org/Recommended_Packages for
118
118
hints about the packages you should install. On 64-bit platforms,
119
119
you have to make sure to install the 32-bit versions of these
120
120
libraries.
121
121
122
122
123
- # 4. COMPILATION
123
+ ## 4. COMPILATION
124
124
125
125
To build Wine, do:
126
126
@@ -139,7 +139,7 @@ To see compile configuration options, do ./configure --help.
139
139
For more information, see https://wiki.winehq.org/Building_Wine
140
140
141
141
142
- # 5. SETUP
142
+ ## 5. SETUP
143
143
144
144
Once Wine has been built correctly, you can do "make install"; this
145
145
will install the wine executable and libraries, the Wine man page, and
@@ -153,7 +153,7 @@ Once installed, you can run the "winecfg" configuration tool. See the
153
153
Support area at https://www.winehq.org/ for configuration hints.
154
154
155
155
156
- # 6. RUNNING PROGRAMS
156
+ ## 6. RUNNING PROGRAMS
157
157
158
158
When invoking Wine, you may specify the entire path to the executable,
159
159
or a filename only.
@@ -176,27 +176,27 @@ will get a crash log that you should attach to your report when filing
176
176
a bug.
177
177
178
178
179
- # 7. GETTING MORE INFORMATION
179
+ ## 7. GETTING MORE INFORMATION
180
180
181
- ## WWW: A great deal of information about Wine is available from WineHQ at
181
+ ### WWW: A great deal of information about Wine is available from WineHQ at
182
182
https://www.winehq.org/ : various Wine Guides, application database,
183
183
bug tracking. This is probably the best starting point.
184
184
185
- ## FAQ: The Wine FAQ is located at https://www.winehq.org/FAQ
185
+ ### FAQ: The Wine FAQ is located at https://www.winehq.org/FAQ
186
186
187
- ## Wiki: The Wine Wiki is located at https://wiki.winehq.org
187
+ ### Wiki: The Wine Wiki is located at https://wiki.winehq.org
188
188
189
- ## Mailing lists:
189
+ ### Mailing lists:
190
190
There are several mailing lists for Wine users and developers;
191
191
see https://www.winehq.org/forums for more information.
192
192
193
- ## Bugs: Report bugs to Wine Bugzilla at https://bugs.winehq.org
193
+ ### Bugs: Report bugs to Wine Bugzilla at https://bugs.winehq.org
194
194
Please search the bugzilla database to check whether your
195
195
problem is already known or fixed before posting a bug report.
196
196
197
- ## IRC: Online help is available at channel #WineHQ on irc.libera.chat.
197
+ ### IRC: Online help is available at channel #WineHQ on irc.libera.chat.
198
198
199
- ## Git: The current Wine development tree is available through Git.
199
+ ### Git: The current Wine development tree is available through Git.
200
200
Go to https://www.winehq.org/git for more information.
201
201
202
202
If you add something, or fix a bug, please send a patch (preferably
0 commit comments