emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: display word wrapping


From: Juanma Barranquero
Subject: Re: display word wrapping
Date: Thu, 03 Jun 2004 01:47:51 +0200

On Wed, 02 Jun 2004 23:17:21 +0100, Jason Rumney <address@hidden> wrote:

BTW, I'm thinking of making this change to nt/INSTALL.

Comments?

                                                           /L/e/k/t/u



Index: INSTALL
===================================================================
RCS file: /cvsroot/emacs/emacs/nt/INSTALL,v
retrieving revision 1.20
diff -u -2 -r1.20 INSTALL
--- INSTALL     2 Sep 2003 22:36:30 -0000       1.20
+++ INSTALL     2 Jun 2004 23:42:06 -0000
@@ -1,6 +1,6 @@
                      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,2004 Free Software Foundation, Inc.
   See the end of the file for copying permissions.
 
@@ -32,5 +32,5 @@
   in the previous paragraph.
 
-  If you build Emacs on Windows 9X or ME, not on Windows 2000 or
+  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.
 
@@ -91,20 +91,35 @@
 * 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
+  support additional image types: xpm, tiff, gif, png and jpeg.  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.
+
+  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.  (You can also set an application
+  path on the Windows registry by adding an entry to
+  "HKCU\Software\Microsoft\Windows\CurrentVersion\App Paths", but that's
+  *not* recommended unless you know what you're doing.)  Failure to find a
+  library is not an error; the associated image format will simply be
+  unavailable.
+
+  Some image libraries have dependencies on one another, or from 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 MinGW
+  and work better with GCC/MinGW builds of Emacs, like the official binary
+  tarballs for Windows.  Compatibility with MSVC 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





reply via email to

[Prev in Thread] Current Thread [Next in Thread]