emacs: nt/INSTALL comparison

comparison nt/INSTALL @ 90185:5b029ff3b08d

Revision: miles@gnu.org--gnu-2005/emacs--unicode--0--patch-55 Merge from emacs--cvs-trunk--0 Patches applied: * emacs--cvs-trunk--0 (patch 320-323) - Update from CVS

author	Miles Bader <miles@gnu.org>
date	Thu, 26 May 2005 05:42:19 +0000
parents	0fe073a08cef 850c9d934e12
children	a1b34dec1104

comparison

equal deleted inserted replaced

-:9e5e2f01c7ab
+:5b029ff3b08d
 		      Building and Installing Emacs
 		on Windows NT/2K/XP and Windows 95/98/ME
-Copyright (c) 2001,2004 Free Software Foundation, Inc.
+Copyright (c) 2001,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,
 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).
 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
+You will also need a copy of the Posix cp, rm and mv programs.  These
-and other useful Posix utilities can be obtained from the Mingw or
+and other useful Posix utilities can be obtained from one of several
-Cygwin projects.
+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 and 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
 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
 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.
 To use the external image support, the DLLs implementing the
-functionality must be found when Emacs is started, either on the PATH,
+functionality must be found when Emacs first needs them, either on the
-or in the same directory as emacs.exe.  Failure to find a library is
+PATH, or in the same directory as emacs.exe.  Failure to find a
-not an error; the associated image format will simply be unavailable.
+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
-GnuWin32 (http://gnuwin32.sourceforge.net).  These are built with
+the GnuWin32 project.  These are built with MinGW, but they can be
-MinGW, and so are very compatible with GCC/MinGW builds of Emacs (like
+used with both GCC/MinGW and MSVC builds of Emacs.
-the official binary tarballs for Windows).  Compatibility with MSVC,
-on the other hand, is still weak and should not be trusted in
-production environments; if you really need an MSVC-compiled Emacs
-with image support, you should try to build the required libraries
-with the same compiler (though it can be extremely non-trivial, and
-we'll be interested on hearing of any such effort).
 * Building
 After running configure, simply run the appropriate `make' program for
 your compiler to build Emacs.  For MSVC, this is nmake; for GCC, it is
 to create a Start menu icon for Emacs.
 * 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,
 cygwin ports of make must run in UNIX mode, either by specifying
 --unix on the command line, or MAKE_MODE=UNIX in the environment.

Mercurial > emacs

comparison nt/INSTALL @ 90185:5b029ff3b08d