29 |
|
|
30 |
To compile Emacs, you will need either Microsoft Visual C++ 2.0 or |
To compile Emacs, you will need either Microsoft Visual C++ 2.0 or |
31 |
later and nmake, or a Windows port of GCC 2.95 or later with MinGW |
later and nmake, or a Windows port of GCC 2.95 or later with MinGW |
32 |
and W32 API support and a port of GNU make. You can use the Cygwin |
and W32 API support and a port of GNU Make. You can use the Cygwin |
33 |
ports of GCC, but Emacs requires the MinGW headers and libraries to |
ports of GCC, but Emacs requires the MinGW headers and libraries to |
34 |
build (latest versions of the Cygwin toolkit, at least since v1.3.3, |
build (latest versions of the Cygwin toolkit, at least since v1.3.3, |
35 |
include the MinGW headers and libraries as an integral part). |
include the MinGW headers and libraries as an integral part). |
36 |
|
|
37 |
Other compilers may work, but specific reports from people that have |
If you use the MinGW port of GCC and GNU Make to build Emacs, there |
38 |
tried suggest that the Intel C compiler (for example) may produce an |
are some compatibility issues wrt Make and the shell that is run by |
39 |
Emacs executable with strange filename completion behaviour. Unless |
Make, either the standard COMMAND.COM/CMD.EXE supplied with Windows |
40 |
you would like to assist by finding and fixing the cause of any bugs |
or sh.exe., a port of a Unixy shell. For reference, here is a list |
41 |
like this, we recommend the use of the supported compilers mentioned |
of which builds of GNU Make are known to work or not, and whether |
42 |
in the previous paragraph. |
they work in the presence and/or absence of sh.exe, the Cygwin port |
43 |
|
of Bash. Note that any version of Make that is compiled with Cygwin |
44 |
You will also need a copy of the Posix cp, rm and mv programs. These |
will only work with Cygwin tools, due to the use of cygwin style |
45 |
and other useful Posix utilities can be obtained from one of several |
paths. This means Cygwin Make is unsuitable for building parts of |
46 |
projects: |
Emacs that need to invoke Emacs itself (leim and "make bootstrap", |
47 |
|
for example). Also see the Trouble-shooting section below if you |
48 |
* http://www.mingw.org/ ( MinGW ) |
decide to go ahead and use Cygwin make. |
|
* http://www.cygwin.com/ ( Cygwin ) |
|
|
* http://unxutils.sourceforge.net/ ( UnxUtils ) |
|
|
* http://gnuwin32.sourceforge.net/ ( GnuWin32 ) |
|
|
|
|
|
If you build Emacs on Windows 9X or ME, not on Windows 2K/XP or |
|
|
Windows NT, we suggest to install the Cygwin port of Bash. |
|
|
|
|
|
Additional instructions and help for building Emacs on Windows can be |
|
|
found at the Emacs Wiki: |
|
|
|
|
|
http://www.emacswiki.org/cgi-bin/wiki/WThirtyTwoInstallationKit |
|
|
|
|
|
and at this URL: |
|
|
|
|
|
http://ourcomments.org/Emacs/w32-build-emacs.html |
|
|
|
|
|
For reference, here is a list of which builds of GNU make are known |
|
|
to work or not, and whether they work in the presence and/or absence |
|
|
of sh.exe, the Cygwin port of Bash. Note that any version of make |
|
|
that is compiled with Cygwin will only work with Cygwin tools, due to |
|
|
the use of cygwin style paths. This means Cygwin make is unsuitable |
|
|
for building parts of Emacs that need to invoke Emacs itself (leim and |
|
|
"make bootstrap", for example). Also see the Trouble-shooting section |
|
|
below if you decide to go ahead and use Cygwin make. |
|
49 |
|
|
50 |
In addition, using 4NT as your shell is known to fail the build process, |
In addition, using 4NT as your shell is known to fail the build process, |
51 |
at least for 4NT version 3.01. Use cmd.exe, the default NT shell, |
at least for 4NT version 3.01. Use CMD.EXE, the default Windows shell, |
52 |
instead. MSYS sh.exe also appears to cause various problems. If you have |
instead. MSYS sh.exe also appears to cause various problems. If you have |
53 |
MSYS installed, try "make SHELL=cmd.exe" to force the use of cmd.exe |
MSYS installed, try "make SHELL=cmd.exe" to force the use of cmd.exe |
54 |
instead of sh.exe. |
instead of sh.exe. |
78 |
May work if building emacs without leim. |
May work if building emacs without leim. |
79 |
[6] please report if you try this combination. |
[6] please report if you try this combination. |
80 |
|
|
81 |
|
Other compilers may work, but specific reports from people that have |
82 |
|
tried suggest that the Intel C compiler (for example) may produce an |
83 |
|
Emacs executable with strange filename completion behaviour. Unless |
84 |
|
you would like to assist by finding and fixing the cause of any bugs |
85 |
|
like this, we recommend the use of the supported compilers mentioned |
86 |
|
in the previous paragraph. |
87 |
|
|
88 |
|
You will also need a copy of the Posix cp, rm and mv programs. These |
89 |
|
and other useful Posix utilities can be obtained from one of several |
90 |
|
projects: |
91 |
|
|
92 |
|
* http://www.mingw.org/ ( MinGW ) |
93 |
|
* http://www.cygwin.com/ ( Cygwin ) |
94 |
|
* http://unxutils.sourceforge.net/ ( UnxUtils ) |
95 |
|
* http://gnuwin32.sourceforge.net/ ( GnuWin32 ) |
96 |
|
|
97 |
|
If you build Emacs on Windows 9X or ME, not on Windows 2K/XP or |
98 |
|
Windows NT, we suggest to install the Cygwin port of Bash. |
99 |
|
|
100 |
|
Additional instructions and help for building Emacs on Windows can be |
101 |
|
found at the Emacs Wiki: |
102 |
|
|
103 |
|
http://www.emacswiki.org/cgi-bin/wiki/WThirtyTwoInstallationKit |
104 |
|
|
105 |
|
and at this URL: |
106 |
|
|
107 |
|
http://ourcomments.org/Emacs/w32-build-emacs.html |
108 |
|
|
109 |
* Configuring |
* Configuring |
110 |
|
|
111 |
Configuration of Emacs is now handled by running configure.bat in the |
Configuration of Emacs is now handled by running configure.bat in the |