Do not use this recipe with Cygwin. For building on Cygwin,
use the normal installation instructions, ../INSTALL.
+ If you have a Cygwin or MSYS port of Bash on your Path, you will be
+ better off removing it from PATH. (For details, search for "MSYS
+ sh.exe" below.)
+
1. Change to the `nt' directory (the directory of this file):
cd nt
for example). Also see the Trouble-shooting section below if you
decide to go ahead and use Cygwin make.
- In addition, using 4NT or TCC as your shell is known to fail the build
- process, at least since 4NT version 3.01. Use CMD.EXE, the default
- Windows shell, 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.
+ In addition, using 4NT or TCC as your shell is known to fail the
+ build process, at least since 4NT version 3.01. Use CMD.EXE, the
+ default Windows shell, instead. MSYS sh.exe also appears to cause
+ various problems, e.g., it is known to cause failures in commands
+ like "cmd /c FOO" in the Makefiles, because it thinks "/c" is a
+ Unix-style file name that needs conversion to the Windows format.
+ If you have MSYS installed, try "make SHELL=cmd.exe" to force the
+ use of cmd.exe instead of the MSYS sh.exe.
sh exists no sh
be displayed informing you that "using parameters that include the =
character by enclosing them in quotes will not be supported."
+ You may also use the --cflags and --ldflags options to pass
+ additional parameters to the compiler and linker, respectively; they
+ are frequently used to pass -I and -L flags to specify supplementary
+ include and library directories. If a directory name includes
+ spaces, you will need to enclose it in quotes, as follows
+ -I"C:/Program Files/GnuTLS-2.10.1/include". Note that only the
+ directory name is enclosed in quotes, not the entire argument. Also
+ note that this functionality is only supported if command extensions
+ are available. If command extensions are disabled and you attempt to
+ use this functionality you may see the following warning message
+ "Error in --cflags argument: ... Backslashes and quotes cannot be
+ used with --cflags. Please use forward slashes for filenames and
+ paths (e.g. when passing directories to -I)."
+
N.B. It is normal to see a few error messages output while configure
is running, when gcc support is being tested. These cannot be
suppressed because of limitations in the Windows 9X command.com shell.
For PNG images, we recommend to use versions 1.4.x and later of
libpng, because previous versions had security issues. You can find
precompiled libraries and headers on the GTK download page for
- Windows (http://www.gtk.org/download-windows.html).
+ Windows (http://www.gtk.org/download/win32.php).
Versions 1.4.0 and later of libpng are binary incompatible with
earlier versions, so Emacs will only look for libpng libraries which
* Optional GnuTLS support
- You can build Emacs with GnuTLS support. Put the gnutls/gnutls.h header in
- the include path and link to the appropriate libraries (gnutls.dll and
- gcrypt.dll) with the --lib option.
+ If configure.bat finds the gnutls/gnutls.h file in the include path,
+ Emacs is built with GnuTLS support by default; to avoid that you can
+ pass the argument --without-gnutls.
+
+ In order to support GnuTLS at runtime, a GnuTLS-enabled Emacs must
+ be able to find the relevant DLLs during startup; failure to do so
+ is not an error, but GnuTLS won't be available to the running
+ session.
- You can get pre-built binaries and an installer at
- http://josefsson.org/gnutls4win/.
+ You can get pre-built binaries (including any required DLL and the
+ gnutls.h file) and an installer at http://josefsson.org/gnutls4win/.
* Experimental SVG support