mirror/emacs
1
0
Fork 0
mirror of https://git.savannah.gnu.org/git/emacs.git synced 2024-12-25 10:47:00 +00:00
Code Issues Releases Activity

Add more pointers to ports of Unix tools to Windows, and to the Emacs Wiki

Browse Source 
(which contains building instructions for Windows).  Reword image library
instructions and remove obsolete incompatibility information.
This commit is contained in:
Juanma Barranquero 2005-05-24 10:41:15 +00:00
parent f0a31d7055
commit bd7bdff819
2 changed files with 32 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
nt/ChangeLog
View File

@ -1,3 +1,10 @@
2005-05-24 Juanma Barranquero <lekktu@gmail.com>
* INSTALL: Add more pointers to ports of Unix tools to Windows,
and to the Emacs Wiki (which contains building instructions for
Windows). Reword image library instructions and remove obsolete
incompatibility information.
2005-04-23 David Hunter <hunterd42@comcast.net> (tiny change)
* config.nt (HAVE_PWD_H): Undef.

44
nt/INSTALL
View File

@ -1,7 +1,7 @@
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
@ -21,9 +21,9 @@
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).
@ -34,14 +34,22 @@
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 the Mingw or
Cygwin projects.
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.org/ ( 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
@ -109,9 +117,13 @@
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,
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.
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
@ -120,14 +132,8 @@
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
MinGW, and so are very compatible with GCC/MinGW builds of Emacs (like
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).
the GnuWin32 project. These are built with MinGW, but they can be
used with both GCC/MinGW and MSVC builds of Emacs.
* Building
@ -162,7 +168,7 @@
* 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,