Building and Installing Emacs
- on Windows NT/2000 and Windows 95/98/ME
+ on Windows NT/2K/XP and Windows 95/98/ME
- Copyright (c) 2001 Free Software Foundation, Inc.
+ Copyright (C) 2001, 2002, 2003, 2004, 2005 Free Software Foundation, Inc.
See the end of the file for copying permissions.
If you used WinZip to unpack the distribution, we suggest to
remove the files and unpack again with a different program!
WinZip is known to create some subtle and hard to debug problems,
- such as converting files to DOS CR-LF format, not creating empty
+ such as converting files to DOS CR-LF format, not creating empty
directories, etc. We suggest to use djtarnt.exe from the GNU FTP
site.
+ If you are building out of CVS, then some files in this directory
+ (.bat files, nmake.defs and makefile.w32-in) may need the line-ends
+ fixing first. The easiest way to do this and avoid future conflicts
+ is to run the following command in this (emacs/nt) directory:
+
+ cvs update -kb
+
+ Alternatively, use programs that convert end-of-line format, such as
+ dos2unix and unix2dos available from GnuWin32 or dtou and utod from
+ the DJGPP project.
+
+ In addition to this file, you should also read INSTALL.CVS in the
+ parent directory, and make sure that you have a version of
+ "touch.exe" in your path, and that it will create files that do not
+ yet exist.
+
To compile Emacs, you will need either Microsoft Visual C++ 2.0 or
- 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
and W32 API support and a port of GNU make. You can use the Cygwin
- ports of GCC, but Emacs requires the Mingw headers and libraries to
+ ports of GCC, but Emacs requires the MinGW headers and libraries to
build (latest versions of the Cygwin toolkit, at least since v1.3.3,
include the MinGW headers and libraries as an integral part).
- If you build Emacs on Windows 9X or ME, not on Windows 2000 or
+ Other compilers may work, but specific reports from people that have
+ tried suggest that the Intel C compiler (for example) may produce an
+ Emacs executable with strange filename completion behaviour. Unless
+ you would like to assist by finding and fixing the cause of any bugs
+ like this, we recommend the use of the supported compilers mentioned
+ in the previous paragraph.
+
+ You will also need a copy of the Posix cp, rm and mv programs. These
+ and other useful Posix utilities can be obtained from one of several
+ projects:
+
+ * http://www.mingw.org/ ( MinGW )
+ * 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.
- Please see http://www.mingw.org for pointers to GCC/Mingw binaries.
+ 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
In addition, using 4NT as your shell is known to fail the build process,
at least for 4NT version 3.01. Use cmd.exe, the default NT shell,
- instead.
-
+ instead. MSYS sh.exe also appears to cause various problems. If you have
+ MSYS installed, try "make SHELL=cmd.exe" to force the use of cmd.exe
+ instead of sh.exe.
+
sh exists no sh
cygwin b20.1 make (3.75): fails[1, 5] fails[2, 5]
cygwin compiled gmake 3.77: fails[1, 5] fails[2, 5]
cygwin compiled make 3.78.1: fails[5] fails[2, 5]
cygwin compiled make 3.79.1: fails[3, 5] fails[2?, 5]
- mingw32 compiled make 3.79.1: okay okay
+ mingw32 compiled make 3.79.1: okay okay
+ mingw32 compiled make 3.80: okay unknown[6]
Notes:
[4] may fail on Windows 9X and Windows ME; if so, install Bash.
[5] fails when building leim due to the use of cygwin style paths.
May work if building emacs without leim.
+ [6] please report if you try this combination.
* Configuring
is running, when gcc support is being tested. These cannot be
surpressed because of limitations in the Windows 9x command.com shell.
+ You are encouraged to look at the file config.log which shows details
+ for failed tests, after configure.bat finishes. Any unexplained failure
+ should be investigated and perhaps reported as a bug (see the section
+ about reporting bugs in the file README in this directory and in the
+ Emacs manual).
+
* Optional image library support
- To build Emacs with support for PNG images, the libpng and zlib
- headers must be in the include path when the configure script is
- run. This can be setup using environment variables, or by
- specifying --cflags -I... options on the command-line to
- configure.bat. Similarly, the jpeg-6b, libXpm, tiff and libungif
- headers need to be in the include path for support for those image
- formats to work. The configure script will report whether it was
- able to detect the headers.
-
- To use the PNG support, zlib.dll (or zlibd.dll) and libpng.dll (or
- libpng13.dll, or libpng13d.dll) must be on the PATH or in the same
- directory as emacs.exe when Emacs is started. Similar instructions
- apply for other image libraries. Note that tiff support depends on
- the jpeg library. If you did not compile the libraries yourself, you
- must make sure that the jpeg library you install is the same one
- that the tiff library was compiled against.
+ In addition to its "native" image formats (pbm and xbm), Emacs can
+ handle other image types: xpm, tiff, gif, png and jpeg (postscript is
+ currently unsupported on Windows). To build Emacs with support for
+ them, the corresponding headers must be in the include path when the
+ configure script is run. This can be setup using environment
+ variables, or by specifying --cflags -I... options on the command-line
+ to configure.bat. The configure script will report whether it was
+ able to detect the headers. If the results of this testing appear to be
+ incorrect, please look for details in the file config.log: it will show
+ the failed test programs and compiler error messages that should explain
+ what is wrong. (Usually, any such failures happen because some headers
+ are missing due to bad packaging of the image support libraries.)
+
+ To use the external image support, the DLLs implementing the
+ functionality must be found when Emacs first needs them, either on the
+ PATH, or in the same directory as emacs.exe. Failure to find a
+ library is not an error; the associated image format will simply be
+ unavailable. Note that once Emacs has determined that a library can
+ not be found, there's no way to force it to try again, other than
+ restarting. See the variable `image-library-alist' to configure the
+ expected names of the libraries.
+
+ Some image libraries have dependencies on one another, or on zlib.
+ For example, tiff support depends on the jpeg library. If you did not
+ compile the libraries yourself, you must make sure that any dependency
+ is in the PATH or otherwise accesible and that the binaries are
+ compatible (for example, that they were built with the same compiler).
+
+ Binaries for the image libraries (among many others) can be found at
+ the GnuWin32 project. These are built with MinGW, but they can be
+ used with both GCC/MinGW and MSVC builds of Emacs. See the info on
+ http://ourcomments.org/Emacs/EmacsW32.html for more details about
+ installing image support libraries.
* Building
* Trouble-shooting
The main problems that are likely to be encountered when building
- Emacs stem from using an old version of GCC, or old Mingw or W32 API
+ Emacs stem from using an old version of GCC, or old MinGW or W32 API
headers. Additionally, cygwin ports of GNU make may require the Emacs
source tree to be mounted with text!=binary, because the makefiles
generated by configure.bat necessarily use DOS line endings. Also,
addsection.c relies on. Versions of w32api-xxx.zip from at least
1999-11-18 onwards are okay.
+ When in doubt about correctness of what configure did, look at the file
+ config.log, which shows all the failed test programs and compiler
+ messages associated with the failures. If that doesn't give a clue,
+ please report the problems, together with the relevant fragments from
+ config.log, as bugs.
+
If configure succeeds, but make fails, install the Cygwin port of
Bash, even if the table above indicates that Emacs should be able to
build without sh.exe. (Some versions of Windows shells are too dumb