Commit | Line | Data |
---|---|---|
a917e3f2 JB |
1 | Building and Installing Emacs on Windows |
2 | (from 95 to 7 and beyond) | |
a4a9692d | 3 | |
ab422c4d | 4 | Copyright (C) 2001-2013 Free Software Foundation, Inc. |
7f6d64f8 | 5 | See the end of the file for license conditions. |
4b994b84 | 6 | |
67aeda8d GM |
7 | *** This method of building Emacs is no longer supported. *** |
8 | Instead, see INSTALL.MSYS. | |
9 | ||
0939da72 EZ |
10 | * For the impatient |
11 | ||
12 | Here are the concise instructions for configuring and building the | |
195e32b7 EZ |
13 | native Windows binary of Emacs, for those who want to skip the |
14 | complex explanations and ``just do it'': | |
0939da72 | 15 | |
029e4603 RS |
16 | Do not use this recipe with Cygwin. For building on Cygwin, |
17 | use the normal installation instructions, ../INSTALL. | |
18 | ||
79869f9a | 19 | Do not use these instructions with MSYS environment. For building |
89559104 EZ |
20 | the native Windows binary with MinGW and MSYS, follow the |
21 | instructions in the file INSTALL.MSYS in this directory. | |
22 | ||
23 | For building without MSYS, if you have a Cygwin or MSYS port of Bash | |
24 | on your Path, you will be better off removing it from PATH. (For | |
25 | details, search for "MSYS sh.exe" below.) | |
a8f91761 | 26 | |
0939da72 EZ |
27 | 1. Change to the `nt' directory (the directory of this file): |
28 | ||
29 | cd nt | |
30 | ||
a6fc3b5c EZ |
31 | 2. Run configure.bat. |
32 | ||
33 | 2a.If you use MSVC, set up the build environment by running the | |
34 | SetEnv.cmd batch file from the appropriate SDK directory. (Skip | |
35 | this step if you are using MinGW.) For example: | |
36 | ||
37 | "C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\SetEnv.cmd" /x86 /Debug | |
38 | ||
3ed8598c | 39 | if you are going to compile a debug version, or |
a6fc3b5c EZ |
40 | |
41 | "C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\SetEnv.cmd" /x86 /Release | |
42 | ||
43 | if you are going to compile an optimized version. | |
44 | ||
45 | 2b.From the COMMAND.COM/CMD.EXE command prompt type: | |
0939da72 EZ |
46 | |
47 | configure | |
48 | ||
a6fc3b5c | 49 | From a Unixy shell prompt: |
0939da72 EZ |
50 | |
51 | cmd /c configure.bat | |
52 | or | |
53 | command.com /c configure.bat | |
54 | ||
55 | 3. Run the Make utility suitable for your environment. If you build | |
a6fc3b5c | 56 | with the Microsoft's Visual C compiler: |
0939da72 EZ |
57 | |
58 | nmake | |
59 | ||
60 | For the development environments based on GNU GCC (MinGW, MSYS, | |
ac70d20b JR |
61 | Cygwin - but see notes about Cygwin make below), depending on how |
62 | Make is called, it could be: | |
0939da72 EZ |
63 | |
64 | make | |
ac70d20b JR |
65 | or |
66 | mingw32-make | |
0939da72 EZ |
67 | or |
68 | gnumake | |
69 | or | |
70 | gmake | |
71 | ||
ee6f37f2 | 72 | (If you are building from Bazaar, say "make bootstrap" or "nmake |
e84b63f1 EZ |
73 | bootstrap" instead, and avoid using Cygwin make.) |
74 | ||
75 | With GNU Make, you can use the -j command-line option to have | |
76 | Make execute several commands at once, like this: | |
77 | ||
7a43121e EZ |
78 | gmake -j 2 |
79 | ||
80 | (With versions of GNU Make before 3.82, you need also set the | |
81 | XMFLAGS variable, like this: | |
82 | ||
ecfd8ceb | 83 | gmake -j 2 XMFLAGS="-j 2" |
e84b63f1 | 84 | |
7a43121e EZ |
85 | The XMFLAGS variable overrides the default behavior of version |
86 | 3.82 and older of GNU Make on Windows, whereby recursive Make | |
87 | invocations reset the maximum number of simultaneous commands to | |
88 | 1. The above command allows up to 4 simultaneous commands at | |
89 | once in the top-level Make, and up to 3 in each one of the | |
90 | recursive Make's.) | |
0939da72 | 91 | |
ee6f37f2 KF |
92 | 4. Generate the Info manuals (only if you are building out of Bazaar, |
93 | and if you have makeinfo.exe installed): | |
0939da72 EZ |
94 | |
95 | make info | |
96 | ||
97 | (change "make" to "nmake" if you use MSVC). | |
98 | ||
99 | 5. Install the produced binaries: | |
100 | ||
101 | make install | |
102 | ||
103 | That's it! | |
104 | ||
105 | If these short instructions somehow fail, read the rest of this | |
106 | file. | |
107 | ||
108 | * Preliminaries | |
109 | ||
195e32b7 | 110 | If you want to build a Cygwin port of Emacs, use the instructions in |
0d801288 | 111 | the INSTALL file in the main Emacs directory (the parent of this |
195e32b7 EZ |
112 | directory). These instructions are for building a native Windows |
113 | binary of Emacs. | |
114 | ||
12d70bbb EZ |
115 | If you used WinZip to unpack the distribution, we suggest to |
116 | remove the files and unpack again with a different program! | |
117 | WinZip is known to create some subtle and hard to debug problems, | |
177c0ea7 | 118 | such as converting files to DOS CR-LF format, not creating empty |
12d70bbb | 119 | directories, etc. We suggest to use djtarnt.exe from the GNU FTP |
970b321f EZ |
120 | site. For modern formats, such as .tar.xz, we suggest bsdtar.exe |
121 | from the libarchive package; its precompiled Windows binaries are | |
122 | available from this site: | |
12d70bbb | 123 | |
970b321f EZ |
124 | http://sourceforge.net/projects/ezwinports/files/ |
125 | ||
126 | In addition to this file, if you build a development snapshot, you | |
127 | should also read INSTALL.BZR in the parent directory. | |
589a591b | 128 | |
0939da72 EZ |
129 | * Supported development environments |
130 | ||
bbf5b365 | 131 | To compile Emacs, you will need either Microsoft Visual C++ 2.0, or |
a6fc3b5c | 132 | later and nmake, or a Windows port of GCC 2.95 or later with MinGW |
b46a6a83 | 133 | and Windows API support and a port of GNU Make. You can use the Cygwin |
a6fc3b5c EZ |
134 | ports of GCC, but Emacs requires the MinGW headers and libraries to |
135 | build (latest versions of the Cygwin toolkit, at least since v1.3.3, | |
136 | include the MinGW headers and libraries as an integral part). | |
ecfd8ceb | 137 | |
0939da72 | 138 | The rest of this file assumes you have a working development |
a6fc3b5c | 139 | environment. If you just installed such an environment, try |
0939da72 | 140 | building a trivial C "Hello world" program, and see if it works. If |
5376eb82 EZ |
141 | it doesn't work, resolve that problem first! If you use Microsoft |
142 | Visual Studio .NET 2003, don't forget to run the VCVARS32.BAT batch | |
143 | file from the `Bin' subdirectory of the directory where you have | |
a6fc3b5c EZ |
144 | installed VS.NET. With other versions of MSVC, run the SetEnv.cmd |
145 | batch file from the `Bin' subdirectory of the directory where you | |
146 | have the SDK installed. | |
0939da72 | 147 | |
6c72c0c7 EZ |
148 | If you use the MinGW port of GCC and GNU Make to build Emacs, there |
149 | are some compatibility issues wrt Make and the shell that is run by | |
150 | Make, either the standard COMMAND.COM/CMD.EXE supplied with Windows | |
6d96d18f | 151 | or sh.exe, a port of a Unixy shell. For reference, below is a list |
6c72c0c7 EZ |
152 | of which builds of GNU Make are known to work or not, and whether |
153 | they work in the presence and/or absence of sh.exe, the Cygwin port | |
1640b452 | 154 | of Bash. Note that any version of Make that is compiled with Cygwin |
6d96d18f | 155 | will only work with Cygwin tools, due to the use of Cygwin style |
6c72c0c7 EZ |
156 | paths. This means Cygwin Make is unsuitable for building parts of |
157 | Emacs that need to invoke Emacs itself (leim and "make bootstrap", | |
158 | for example). Also see the Trouble-shooting section below if you | |
159 | decide to go ahead and use Cygwin make. | |
b147d297 | 160 | |
6c06b142 EZ |
161 | In addition, using 4NT or TCC as your shell is known to fail the |
162 | build process, at least since 4NT version 3.01. Use CMD.EXE, the | |
163 | default Windows shell, instead. MSYS sh.exe also appears to cause | |
164 | various problems, e.g., it is known to cause failures in commands | |
165 | like "cmd /c FOO" in the Makefiles, because it thinks "/c" is a | |
166 | Unix-style file name that needs conversion to the Windows format. | |
167 | If you have MSYS installed, try "make SHELL=cmd.exe" to force the | |
168 | use of cmd.exe instead of the MSYS sh.exe. | |
177c0ea7 | 169 | |
4bcec9a2 EZ |
170 | sh exists no sh |
171 | ||
fc813ef6 | 172 | cygwin b20.1 make (3.75): fails[1, 5] fails[2, 5] |
4bcec9a2 EZ |
173 | MSVC compiled gmake 3.77: okay okay |
174 | MSVC compiled gmake 3.78.1: okay okay | |
175 | MSVC compiled gmake 3.79.1: okay okay | |
bf95665f | 176 | mingw32/gcc-2.92.2 make (3.77): okay okay[4] |
fc813ef6 JR |
177 | cygwin compiled gmake 3.77: fails[1, 5] fails[2, 5] |
178 | cygwin compiled make 3.78.1: fails[5] fails[2, 5] | |
179 | cygwin compiled make 3.79.1: fails[3, 5] fails[2?, 5] | |
16fb735f EZ |
180 | cygwin compiled make 3.80: okay[6] fails?[7] |
181 | cygwin compiled make 3.81: fails fails?[7] | |
177c0ea7 | 182 | mingw32 compiled make 3.79.1: okay okay |
16fb735f EZ |
183 | mingw32 compiled make 3.80: okay okay[7] |
184 | mingw32 compiled make 3.81: okay okay[8] | |
4bcec9a2 EZ |
185 | |
186 | Notes: | |
187 | ||
188 | [1] doesn't cope with makefiles with DOS line endings, so must mount | |
189 | emacs source with text!=binary. | |
190 | [2] fails when needs to invoke shell commands; okay invoking gcc etc. | |
fc813ef6 | 191 | [3] requires LC_MESSAGES support to build; cannot build with early |
a917e3f2 | 192 | versions of Cygwin. |
4bcec9a2 | 193 | [4] may fail on Windows 9X and Windows ME; if so, install Bash. |
fc813ef6 JR |
194 | [5] fails when building leim due to the use of cygwin style paths. |
195 | May work if building emacs without leim. | |
16fb735f EZ |
196 | [6] need to uncomment 3 lines in nt/gmake.defs that invoke `cygpath' |
197 | (look for "cygpath" near line 85 of gmake.defs). | |
198 | [7] not recommended; please report if you try this combination. | |
199 | [8] tested only on Windows XP. | |
4bcec9a2 | 200 | |
6c72c0c7 EZ |
201 | Other compilers may work, but specific reports from people that have |
202 | tried suggest that the Intel C compiler (for example) may produce an | |
5739d6f8 | 203 | Emacs executable with strange filename completion behavior. Unless |
6c72c0c7 EZ |
204 | you would like to assist by finding and fixing the cause of any bugs |
205 | like this, we recommend the use of the supported compilers mentioned | |
206 | in the previous paragraph. | |
207 | ||
a917e3f2 JB |
208 | You will also need a copy of the POSIX cp, rm and mv programs. These |
209 | and other useful POSIX utilities can be obtained from one of several | |
6c72c0c7 EZ |
210 | projects: |
211 | ||
0939da72 | 212 | * http://gnuwin32.sourceforge.net/ ( GnuWin32 ) |
6c72c0c7 EZ |
213 | * http://www.mingw.org/ ( MinGW ) |
214 | * http://www.cygwin.com/ ( Cygwin ) | |
215 | * http://unxutils.sourceforge.net/ ( UnxUtils ) | |
6c72c0c7 | 216 | |
a917e3f2 JB |
217 | If you build Emacs on 16-bit versions of Windows (9X or ME), we |
218 | suggest to install the Cygwin port of Bash. That is because the | |
219 | native Windows shell COMMAND.COM is too limited; the Emacs build | |
220 | procedure tries very hard to support even such limited shells, but | |
221 | as none of the Windows developers of Emacs work on Windows 9X, we | |
222 | cannot guarantee that it works without a more powerful shell. | |
6c72c0c7 EZ |
223 | |
224 | Additional instructions and help for building Emacs on Windows can be | |
225 | found at the Emacs Wiki: | |
226 | ||
0939da72 | 227 | http://www.emacswiki.org/cgi-bin/wiki/WThirtyTwoInstallationKit |
6c72c0c7 | 228 | |
309c91ff | 229 | and on these URLs: |
6c72c0c7 | 230 | |
0939da72 | 231 | http://ourcomments.org/Emacs/w32-build-emacs.html |
309c91ff EZ |
232 | http://derekslager.com/blog/posts/2007/01/emacs-hack-3-compile-emacs-from-cvs-on-windows.ashx |
233 | ||
ee6f37f2 KF |
234 | Both of those pages were written before Emacs switched from CVS to |
235 | Bazaar, but the parts about building Emacs still apply in Bazaar. | |
236 | The second URL has instructions for building with MSVC, as well as | |
237 | with MinGW, while the first URL covers only MinGW, but has more | |
238 | details about it. | |
6c72c0c7 | 239 | |
6d76a603 | 240 | * Configuring |
a4a9692d | 241 | |
da179dd0 | 242 | Configuration of Emacs is now handled by running configure.bat in the |
0939da72 | 243 | `nt' subdirectory. It will detect which compiler you have available, |
da179dd0 AI |
244 | and generate makefiles accordingly. You can override the compiler |
245 | detection, and control optimization and debug settings, by specifying | |
246 | options on the command line when invoking configure. | |
a4a9692d | 247 | |
da179dd0 | 248 | To configure Emacs to build with GCC or MSVC, whichever is available, |
0939da72 | 249 | simply change to the `nt' subdirectory and run `configure.bat' with no |
da179dd0 | 250 | options. To see what options are available, run `configure --help'. |
23636b09 EZ |
251 | Do NOT use the --no-debug option to configure.bat unless you are |
252 | absolutely sure the produced binaries will never need to be run under | |
253 | a debugger. | |
a4a9692d | 254 | |
4a1a6b5b BK |
255 | Because of limitations of the stock Windows command shells, special |
256 | care is needed to pass some characters in the arguments of the | |
257 | --cflags and --ldflags options. Backslashes should not be used in | |
258 | file names passed to the compiler and linker via these options. Use | |
259 | forward slashes instead. If the arguments to these two options | |
260 | include the `=' character, like when passing a -DFOO=bar preprocessor | |
261 | option, the argument with the `=' character should be enclosed in | |
262 | quotes, like this: | |
263 | ||
264 | configure --cflags "-DFOO=bar" | |
265 | ||
266 | Support for options that include the `=' character require "command | |
267 | extensions" to be enabled. (They are enabled by default, but your | |
268 | system administrator could have changed that. See "cmd /?" for | |
269 | details.) If command extensions are disabled, a warning message might | |
270 | be displayed informing you that "using parameters that include the = | |
271 | character by enclosing them in quotes will not be supported." | |
6072fed4 | 272 | |
d429d8e9 BK |
273 | You may also use the --cflags and --ldflags options to pass |
274 | additional parameters to the compiler and linker, respectively; they | |
275 | are frequently used to pass -I and -L flags to specify supplementary | |
276 | include and library directories. If a directory name includes | |
277 | spaces, you will need to enclose it in quotes, as follows | |
278 | -I"C:/Program Files/GnuTLS-2.10.1/include". Note that only the | |
279 | directory name is enclosed in quotes, not the entire argument. Also | |
280 | note that this functionality is only supported if command extensions | |
281 | are available. If command extensions are disabled and you attempt to | |
282 | use this functionality you may see the following warning message | |
283 | "Error in --cflags argument: ... Backslashes and quotes cannot be | |
284 | used with --cflags. Please use forward slashes for filenames and | |
285 | paths (e.g. when passing directories to -I)." | |
3ed8598c | 286 | |
17d4e22c AI |
287 | N.B. It is normal to see a few error messages output while configure |
288 | is running, when gcc support is being tested. These cannot be | |
a917e3f2 | 289 | suppressed because of limitations in the Windows 9X command.com shell. |
17d4e22c | 290 | |
591cbed1 EZ |
291 | You are encouraged to look at the file config.log which shows details |
292 | for failed tests, after configure.bat finishes. Any unexplained failure | |
293 | should be investigated and perhaps reported as a bug (see the section | |
294 | about reporting bugs in the file README in this directory and in the | |
295 | Emacs manual). | |
296 | ||
bfd889ed JR |
297 | * Optional image library support |
298 | ||
3dfbc6d8 | 299 | In addition to its "native" image formats (pbm and xbm), Emacs can |
8bc63b1a | 300 | handle other image types: xpm, tiff, gif, png, jpeg and experimental |
707a78b2 | 301 | support for svg. |
6d96d18f | 302 | |
8bc63b1a JR |
303 | To build Emacs with support for them, the corresponding headers must |
304 | be in the include path when the configure script is run. This can | |
305 | be setup using environment variables, or by specifying --cflags | |
306 | -I... options on the command-line to configure.bat. The configure | |
307 | script will report whether it was able to detect the headers. If | |
308 | the results of this testing appear to be incorrect, please look for | |
309 | details in the file config.log: it will show the failed test | |
310 | programs and compiler error messages that should explain what is | |
311 | wrong. (Usually, any such failures happen because some headers are | |
312 | missing due to bad packaging of the image support libraries.) | |
bfd889ed | 313 | |
a917e3f2 JB |
314 | Note that any file path passed to the compiler or linker must use |
315 | forward slashes; using backslashes will cause compiler warnings or | |
316 | errors about unrecognized escape sequences. | |
317 | ||
3dfbc6d8 | 318 | To use the external image support, the DLLs implementing the |
bd7bdff8 JB |
319 | functionality must be found when Emacs first needs them, either on the |
320 | PATH, or in the same directory as emacs.exe. Failure to find a | |
321 | library is not an error; the associated image format will simply be | |
322 | unavailable. Note that once Emacs has determined that a library can | |
323 | not be found, there's no way to force it to try again, other than | |
2e288d54 | 324 | restarting. See the variable `dynamic-library-alist' to configure the |
bd7bdff8 | 325 | expected names of the libraries. |
3dfbc6d8 JB |
326 | |
327 | Some image libraries have dependencies on one another, or on zlib. | |
328 | For example, tiff support depends on the jpeg library. If you did not | |
329 | compile the libraries yourself, you must make sure that any dependency | |
5739d6f8 | 330 | is in the PATH or otherwise accessible and that the binaries are |
3dfbc6d8 JB |
331 | compatible (for example, that they were built with the same compiler). |
332 | ||
333 | Binaries for the image libraries (among many others) can be found at | |
a74722ee JR |
334 | the GnuWin32 project. PNG, JPEG and TIFF libraries are also |
335 | included with GTK, which is installed along with other Free Software | |
336 | that requires it. These are built with MinGW, but they can be used | |
337 | with both GCC/MinGW and MSVC builds of Emacs. See the info on | |
55fcf5c6 EZ |
338 | http://ourcomments.org/Emacs/w32-build-emacs.html, under "How to Get |
339 | Images Support", for more details about installing image support | |
340 | libraries. Note specifically that, due to some packaging snafus in | |
341 | the GnuWin32-supplied image libraries, you will need to download | |
342 | _source_ packages for some of the libraries in order to get the | |
343 | header files necessary for building Emacs with image support. | |
bfd889ed | 344 | |
a74722ee JR |
345 | If GTK 2.0 is installed, addpm will arrange for its image libraries |
346 | to be on the DLL search path for Emacs. | |
347 | ||
5be1c984 EZ |
348 | For PNG images, we recommend to use versions 1.4.x and later of |
349 | libpng, because previous versions had security issues. You can find | |
350 | precompiled libraries and headers on the GTK download page for | |
df6d30f3 | 351 | Windows (http://www.gtk.org/download/win32.php). |
5be1c984 EZ |
352 | |
353 | Versions 1.4.0 and later of libpng are binary incompatible with | |
354 | earlier versions, so Emacs will only look for libpng libraries which | |
355 | are compatible with the version it was compiled against. That | |
356 | version is given by the value of the Lisp variable `libpng-version'; | |
3d4cad2c | 357 | e.g., 10403 means version 1.4.3. The variable `dynamic-library-alist' |
5be1c984 EZ |
358 | is automatically set to name only those DLL names that are known to |
359 | be compatible with the version given by `libpng-version'. If PNG | |
360 | support does not work for you even though you have the support DLL | |
361 | installed, check the name of the installed DLL against | |
3d4cad2c | 362 | `dynamic-library-alist' and the value of `libpng-version', and |
5be1c984 EZ |
363 | download compatible DLLs if needed. |
364 | ||
fd4af8d9 TZ |
365 | * Optional GnuTLS support |
366 | ||
0898ca10 JB |
367 | If configure.bat finds the gnutls/gnutls.h file in the include path, |
368 | Emacs is built with GnuTLS support by default; to avoid that you can | |
369 | pass the argument --without-gnutls. | |
fd4af8d9 | 370 | |
0898ca10 JB |
371 | In order to support GnuTLS at runtime, a GnuTLS-enabled Emacs must |
372 | be able to find the relevant DLLs during startup; failure to do so | |
373 | is not an error, but GnuTLS won't be available to the running | |
374 | session. | |
375 | ||
376 | You can get pre-built binaries (including any required DLL and the | |
8dc96b40 | 377 | header files) at http://sourceforge.net/projects/ezwinports/files/. |
fd4af8d9 | 378 | |
9078ead6 EZ |
379 | * Optional libxml2 support |
380 | ||
381 | If configure.bat finds the libxml/HTMLparser.h file in the include path, | |
382 | Emacs is built with libxml2 support by default; to avoid that you can | |
383 | pass the argument --without-libxml2. | |
384 | ||
385 | In order to support libxml2 at runtime, a libxml2-enabled Emacs must | |
386 | be able to find the relevant DLLs during startup; failure to do so | |
387 | is not an error, but libxml2 features won't be available to the | |
388 | running session. | |
389 | ||
390 | One place where you can get pre-built Windows binaries of libxml2 | |
391 | (including any required DLL and the header files) is here: | |
392 | ||
393 | http://sourceforge.net/projects/ezwinports/files/ | |
394 | ||
395 | To compile Emacs with libxml2 from that site, you will need to pass | |
396 | the "--cflags -I/path/to/include/libxml2" option to configure.bat, | |
397 | because libxml2 header files are installed in the include/libxml2 | |
398 | subdirectory of the directory where you unzip the binary | |
399 | distribution. Other binary distributions might use other | |
400 | directories, although include/libxml2 is the canonical place where | |
401 | libxml2 headers are installed on Posix platforms. | |
402 | ||
403 | You will also need to install the libiconv "development" tarball, | |
404 | because the libiconv headers need to be available to the compiler | |
405 | when you compile with libxml2 support. A MinGW port of libiconv can | |
406 | be found on the MinGW site: | |
407 | ||
408 | http://sourceforge.net/projects/mingw/files/MinGW/Base/libiconv/ | |
409 | ||
410 | You need the libiconv-X.Y.Z-N-mingw32-dev.tar.lzma tarball from that | |
411 | site. | |
412 | ||
8bc63b1a JR |
413 | * Experimental SVG support |
414 | ||
415 | SVG support is currently experimental, and not built by default. | |
416 | Specify --with-svg and ensure you have all the dependencies in your | |
1640b452 | 417 | include path. Unless you have built a minimalist librsvg yourself |
8bc63b1a | 418 | (untested), librsvg depends on a significant chunk of GTK+ to build, |
1640b452 | 419 | plus a few Gnome libraries, libxml2, libbz2 and zlib at runtime. The |
8bc63b1a JR |
420 | easiest way to obtain the dependencies required for building is to |
421 | download a pre-bundled GTK+ development environment for Windows. | |
422 | GTK puts its header files all over the place, so you will need to | |
423 | run pkgconfig to list the include path you will need (either passed | |
424 | to configure.bat as --cflags options, or set in the environment). | |
425 | ||
426 | To use librsvg at runtime, ensure that librsvg and its dependencies | |
427 | are on your PATH. If you didn't build librsvg yourself, you will | |
428 | need to check with where you downloaded it from for the | |
429 | dependencies, as there are different build options. If it is a | |
430 | short list, then it most likely only lists the immediate | |
431 | dependencies of librsvg, but the dependencies themselves have | |
432 | dependencies - so don't download individual libraries from GTK+, | |
1640b452 | 433 | download and install the whole thing. If you think you've got all |
8bc63b1a JR |
434 | the dependencies and SVG support is still not working, check your |
435 | PATH for other libraries that shadow the ones you downloaded. | |
436 | Libraries of the same name from different sources may not be | |
437 | compatible, this problem was encountered with libbzip2 from GnuWin32 | |
438 | with libcroco from gnome.org. | |
439 | ||
440 | If you can see etc/images/splash.svg, then you have managed to get | |
441 | SVG support working. Congratulations for making it through DLL hell | |
1640b452 | 442 | to this point. You'll probably find that some SVG images crash |
8bc63b1a JR |
443 | Emacs. Problems have been observed in some images that contain |
444 | text, they seem to be a problem in the Windows port of Pango, or | |
445 | maybe a problem with the way Cairo or librsvg is using it that | |
446 | doesn't show up on other platforms. | |
447 | ||
a0d363f4 GM |
448 | * Optional extra runtime checks |
449 | ||
450 | The configure.bat option --enable-checking builds Emacs with some | |
451 | optional extra runtime checks and assertions enabled. This may be | |
452 | useful for debugging. | |
453 | ||
454 | * Optional extra libraries | |
455 | ||
456 | You can pass --lib LIBNAME option to configure.bat to cause Emacs to | |
457 | link with the specified library. You can use this option more than once. | |
458 | ||
6d76a603 | 459 | * Building |
a4a9692d | 460 | |
da179dd0 AI |
461 | After running configure, simply run the appropriate `make' program for |
462 | your compiler to build Emacs. For MSVC, this is nmake; for GCC, it is | |
ee6f37f2 | 463 | GNU make. (If you are building out of Bazaar, say "make bootstrap" or |
0939da72 | 464 | "nmake bootstrap" instead.) |
a4a9692d | 465 | |
da179dd0 AI |
466 | As the files are compiled, you will see some warning messages |
467 | declaring that some functions don't return a value, or that some data | |
468 | conversions will be lossy, etc. You can safely ignore these messages. | |
469 | The warnings may be fixed in the main FSF source at some point, but | |
470 | until then we will just live with them. | |
a4a9692d | 471 | |
e84b63f1 EZ |
472 | With GNU Make, you can use the -j command-line option to have Make |
473 | execute several commands at once, like this: | |
474 | ||
475 | gmake -j 4 XMFLAGS="-j 3" | |
476 | ||
477 | The XMFLAGS variable overrides the default behavior of GNU Make on | |
478 | Windows, whereby recursive Make invocations reset the maximum number | |
479 | of simultaneous commands to 1. The above command allows up to 4 | |
480 | simultaneous commands at once in the top-level Make, and up to 3 in | |
481 | each one of the recursive Make's; you can use other numbers of jobs, | |
482 | if you wish. | |
483 | ||
ee6f37f2 KF |
484 | If you are building from Bazaar, the following commands will produce |
485 | the Info manuals (which are not part of the Bazaar sources): | |
0939da72 EZ |
486 | |
487 | make info | |
488 | or | |
489 | nmake info | |
490 | ||
c6911ab9 EZ |
491 | Note that you will need makeinfo.exe (from the GNU Texinfo package) |
492 | in order for this command to succeed. | |
493 | ||
6d76a603 | 494 | * Installing |
a4a9692d | 495 | |
0fc7be80 EZ |
496 | To install Emacs after it has compiled, simply run `nmake install' |
497 | or `make install', depending on which version of the Make utility | |
498 | do you have. | |
a4a9692d | 499 | |
da179dd0 AI |
500 | By default, Emacs will be installed in the location where it was |
501 | built, but a different location can be specified either using the | |
502 | --prefix option to configure, or by setting INSTALL_DIR when running | |
503 | make, like so: | |
a4a9692d | 504 | |
da179dd0 | 505 | make install INSTALL_DIR=D:/emacs |
a4a9692d | 506 | |
0fc7be80 EZ |
507 | (for `nmake', type "nmake install INSTALL_DIR=D:/emacs" instead). |
508 | ||
da179dd0 AI |
509 | The install process will run addpm to setup the registry entries, and |
510 | to create a Start menu icon for Emacs. | |
a4a9692d | 511 | |
5739d6f8 JR |
512 | * Make targets |
513 | ||
514 | The following make targets may be used by users building the source | |
ee6f37f2 | 515 | distribution, or users who have checked out of Bazaar after |
5739d6f8 JR |
516 | an initial bootstrapping. |
517 | ||
518 | make | |
519 | Builds Emacs from the available sources and pre-compiled lisp files. | |
520 | ||
521 | make install | |
522 | Installs programs to the bin directory, and runs addpm to create | |
523 | Start Menu icons. | |
524 | ||
525 | make clean | |
526 | Removes object and executable files produced by the build process in | |
527 | the current configuration. After make clean, you can rebuild with | |
528 | the same configuration using make. | |
529 | ||
530 | make distclean | |
531 | In addition to the files removed by make clean, this also removes | |
532 | Makefiles and other generated files to get back to the state of a | |
1640b452 | 533 | freshly unpacked source distribution. Note that this will not remove |
5739d6f8 JR |
534 | installed files, or the results of builds performed with different |
535 | compiler or optimization options than the current configuration. | |
536 | After make distclean, it is necessary to run configure.bat followed | |
537 | by make to rebuild. | |
538 | ||
539 | make cleanall | |
540 | Removes object and executable files that may have been created by | |
541 | previous builds with different configure options, in addition to | |
542 | the files produced by the current configuration. | |
543 | ||
544 | make realclean | |
545 | Removes the installed files in the bin subdirectory in addition to | |
546 | the files removed by make cleanall. | |
547 | ||
e3aef5c6 CS |
548 | make dist |
549 | Builds Emacs from the available sources and pre-compiled lisp files. | |
550 | Packages Emacs binaries as full distribution and barebin distribution. | |
5739d6f8 | 551 | |
ee6f37f2 | 552 | The following targets are intended only for use with the Bazaar sources. |
5739d6f8 JR |
553 | |
554 | make bootstrap | |
555 | Creates a temporary emacs binary with lisp source files and | |
556 | uses it to compile the lisp files. Once the lisp files are built, | |
557 | emacs is redumped with the compiled lisp. | |
558 | ||
559 | make recompile | |
ee6f37f2 | 560 | Recompiles any changed lisp files after an update. This saves |
5739d6f8 JR |
561 | doing a full bootstrap after every update. If this or a subsequent |
562 | make fail, you probably need to perform a full bootstrap, though | |
563 | running this target multiple times may eventually sort out the | |
564 | interdependencies. | |
565 | ||
566 | make maintainer-clean | |
567 | Removes everything that can be recreated, including compiled lisp | |
ee6f37f2 | 568 | files, to get back to the state of a fresh Bazaar tree. After make |
5739d6f8 JR |
569 | maintainer-clean, it is necessary to run configure.bat and make |
570 | bootstrap to rebuild. Occasionally it may be necessary to run this | |
ee6f37f2 | 571 | target after an update. |
5739d6f8 | 572 | |
e3aef5c6 CS |
573 | * Creating binary distributions |
574 | ||
575 | Binary distributions (full and barebin distributions) can be | |
576 | automatically built and packaged from source tarballs or a bzr | |
577 | checkout. | |
578 | ||
579 | When building Emacs binary distributions, the --distfiles argument | |
580 | to configure.bat specifies files to be included in the bin directory | |
581 | of the binary distributions. This is intended for libraries that are | |
582 | not built as part of Emacs, e.g. image libraries. | |
583 | ||
584 | For example, specifying | |
585 | ||
586 | --distfiles D:\distfiles\libXpm.dll | |
587 | ||
588 | results in libXpm.dll being copied from D:\distfiles to the | |
589 | bin directory before packaging starts. | |
590 | ||
591 | Multiple files can be specified using multiple --distfiles arguments: | |
592 | ||
593 | --distfiles D:\distfiles\libXpm.dll --distfiles C:\jpeglib\jpeg.dll | |
594 | ||
595 | For packaging the binary distributions, the 'dist' make target uses | |
596 | 7-Zip (http://www.7-zip.org), which must be installed and available | |
597 | on the Windows Path. | |
598 | ||
5739d6f8 | 599 | |
6d76a603 | 600 | * Trouble-shooting |
a4a9692d | 601 | |
da179dd0 | 602 | The main problems that are likely to be encountered when building |
b46a6a83 | 603 | Emacs stem from using an old version of GCC, or old MinGW or Windows API |
a917e3f2 | 604 | headers. Additionally, Cygwin ports of GNU make may require the Emacs |
da179dd0 AI |
605 | source tree to be mounted with text!=binary, because the makefiles |
606 | generated by configure.bat necessarily use DOS line endings. Also, | |
a917e3f2 | 607 | Cygwin ports of make must run in UNIX mode, either by specifying |
da179dd0 | 608 | --unix on the command line, or MAKE_MODE=UNIX in the environment. |
a4a9692d | 609 | |
da179dd0 AI |
610 | When configure runs, it attempts to detect when GCC itself, or the |
611 | headers it is using, are not suitable for building Emacs. GCC version | |
612 | 2.95 or later is needed, because that is when the Windows port gained | |
613 | sufficient support for anonymous structs and unions to cope with some | |
a25fe288 | 614 | definitions from winnt.h that are used by addsection.c. |
b46a6a83 | 615 | Older versions of the Windows API headers that come with Cygwin and MinGW |
a25fe288 | 616 | may be missing some definitions required by Emacs, or broken in other |
4a00b4b3 | 617 | ways. In particular, uniscribe APIs were added to MinGW CVS only on |
a25fe288 | 618 | 2006-03-26, so releases from before then cannot be used. |
a4a9692d | 619 | |
591cbed1 EZ |
620 | When in doubt about correctness of what configure did, look at the file |
621 | config.log, which shows all the failed test programs and compiler | |
622 | messages associated with the failures. If that doesn't give a clue, | |
623 | please report the problems, together with the relevant fragments from | |
624 | config.log, as bugs. | |
625 | ||
4bcec9a2 EZ |
626 | If configure succeeds, but make fails, install the Cygwin port of |
627 | Bash, even if the table above indicates that Emacs should be able to | |
628 | build without sh.exe. (Some versions of Windows shells are too dumb | |
629 | for Makefile's used by Emacs.) | |
630 | ||
8481e41e | 631 | If you are using certain Cygwin builds of GCC, such as Cygwin version |
6d76a603 AI |
632 | 1.1.8, you may need to specify some extra compiler flags like so: |
633 | ||
634 | configure --with-gcc --cflags -mwin32 --cflags -D__MSVCRT__ | |
315746cc | 635 | --ldflags -mwin32 |
6d76a603 | 636 | |
8481e41e EZ |
637 | However, the latest Cygwin versions, such as 1.3.3, don't need those |
638 | switches; you can simply use "configure --with-gcc". | |
639 | ||
6d76a603 AI |
640 | We will attempt to auto-detect the need for these flags in a future |
641 | release. | |
642 | ||
643 | * Debugging | |
a4a9692d | 644 | |
da179dd0 AI |
645 | You should be able to debug Emacs using the debugger that is |
646 | appropriate for the compiler you used, namely DevStudio or Windbg if | |
23636b09 EZ |
647 | compiled with MSVC, or GDB if compiled with GCC. (GDB for Windows |
648 | is available from the MinGW site, http://www.mingw.org/download.shtml.) | |
3a817827 EZ |
649 | |
650 | When Emacs aborts due to a fatal internal error, Emacs on Windows | |
651 | pops up an Emacs Abort Dialog asking you whether you want to debug | |
652 | Emacs or terminate it. If Emacs was built with MSVC, click YES | |
653 | twice, and Windbg or the DevStudio debugger will start up | |
654 | automatically. If Emacs was built with GCC, first start GDB and | |
655 | attach it to the Emacs process with the "gdb -p EMACS-PID" command, | |
656 | where EMACS-PID is the Emacs process ID (which you can see in the | |
657 | Windows Task Manager), type the "continue" command inside GDB, and | |
658 | only then click YES on the abort dialog. This will pass control to | |
659 | the debugger, and you will be able to debug the cause of the fatal | |
660 | error. | |
da179dd0 | 661 | |
034ea24d EZ |
662 | The single most important thing to find out when Emacs aborts or |
663 | crashes is where did that happen in the Emacs code. This is called | |
664 | "backtrace". | |
665 | ||
666 | Emacs on Windows uses more than one thread. When Emacs aborts due | |
667 | to a fatal error, the current thread may not be the application | |
668 | thread running Emacs code. Therefore, to produce a meaningful | |
e9fce1ac | 669 | backtrace from a debugger, you need to instruct it to show the |
034ea24d EZ |
670 | backtrace for every thread. With GDB, you do it like this: |
671 | ||
672 | (gdb) thread apply all backtrace | |
673 | ||
674 | To run Emacs under a debugger to begin with, simply start it from | |
675 | the debugger. With GDB, chdir to the `src' directory (if you have | |
676 | the source tree) or to a directory with the `.gdbinit' file (if you | |
677 | don't have the source tree), and type these commands: | |
678 | ||
679 | C:\whatever\src> gdb x:\path\to\emacs.exe | |
680 | (gdb) run <ARGUMENTS TO EMACS> | |
681 | ||
682 | Thereafter, use Emacs as usual; you can minimize the debugger | |
683 | window, if you like. The debugger will take control if and when | |
684 | Emacs crashes. | |
685 | ||
da179dd0 AI |
686 | Emacs functions implemented in C use a naming convention that reflects |
687 | their names in lisp. The names of the C routines are the lisp names | |
688 | prefixed with 'F', and with dashes converted to underscores. For | |
689 | example, the function call-process is implemented in C by | |
690 | Fcall_process. Similarly, lisp variables are prefixed with 'V', again | |
691 | with dashes converted to underscores. These conventions enable you to | |
692 | easily set breakpoints or examine familiar lisp variables by name. | |
693 | ||
694 | Since Emacs data is often in the form of a lisp object, and the | |
3a817827 EZ |
695 | Lisp_Object type is difficult to examine manually in a debugger, |
696 | Emacs provides a helper routine called debug_print that prints out a | |
697 | readable representation of a Lisp_Object. If you are using GDB, | |
698 | there is a .gdbinit file in the src directory which provides | |
699 | definitions that are useful for examining lisp objects. Therefore, | |
700 | the following tips are mainly of interest when using MSVC. | |
701 | ||
702 | The output from debug_print is sent to stderr, and to the debugger | |
703 | via the OutputDebugString routine. The output sent to stderr should | |
704 | be displayed in the console window that was opened when the | |
705 | emacs.exe executable was started. The output sent to the debugger | |
706 | should be displayed in its "Debug" output window. | |
da179dd0 AI |
707 | |
708 | When you are in the process of debugging Emacs and you would like to | |
5739d6f8 | 709 | examine the contents of a Lisp_Object variable, pop up the QuickWatch |
da179dd0 AI |
710 | window (QuickWatch has an eyeglass symbol on its button in the |
711 | toolbar). In the text field at the top of the window, enter | |
712 | debug_print(<variable>) and hit return. For example, start and run | |
713 | Emacs in the debugger until it is waiting for user input. Then click | |
714 | on the Break button in the debugger to halt execution. Emacs should | |
715 | halt in ZwUserGetMessage waiting for an input event. Use the Call | |
716 | Stack window to select the procedure w32_msp_pump up the call stack | |
717 | (see below for why you have to do this). Open the QuickWatch window | |
718 | and enter debug_print(Vexec_path). Evaluating this expression will | |
719 | then print out the contents of the lisp variable exec-path. | |
720 | ||
721 | If QuickWatch reports that the symbol is unknown, then check the call | |
722 | stack in the Call Stack window. If the selected frame in the call | |
723 | stack is not an Emacs procedure, then the debugger won't recognize | |
724 | Emacs symbols. Instead, select a frame that is inside an Emacs | |
725 | procedure and try using debug_print again. | |
726 | ||
727 | If QuickWatch invokes debug_print but nothing happens, then check the | |
728 | thread that is selected in the debugger. If the selected thread is | |
729 | not the last thread to run (the "current" thread), then it cannot be | |
730 | used to execute debug_print. Use the Debug menu to select the current | |
731 | thread and try using debug_print again. Note that the debugger halts | |
732 | execution (e.g., due to a breakpoint) in the context of the current | |
733 | thread, so this should only be a problem if you've explicitly switched | |
734 | threads. | |
4b994b84 | 735 | |
7f6d64f8 GM |
736 | \f |
737 | This file is part of GNU Emacs. | |
4b994b84 | 738 | |
eef0be9e | 739 | GNU Emacs is free software: you can redistribute it and/or modify |
7f6d64f8 | 740 | it under the terms of the GNU General Public License as published by |
eef0be9e GM |
741 | the Free Software Foundation, either version 3 of the License, or |
742 | (at your option) any later version. | |
4b994b84 | 743 | |
7f6d64f8 GM |
744 | GNU Emacs is distributed in the hope that it will be useful, |
745 | but WITHOUT ANY WARRANTY; without even the implied warranty of | |
746 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the | |
747 | GNU General Public License for more details. | |
748 | ||
749 | You should have received a copy of the GNU General Public License | |
eef0be9e | 750 | along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>. |