Mercurial > hg > xemacs-beta
diff nt/README @ 827:28426972f654
[xemacs-hg @ 2002-05-06 14:14:33 by jhar]
Misc win32 native build and doc fixes
author | jhar |
---|---|
date | Mon, 06 May 2002 14:16:31 +0000 |
parents | ece8c2170578 |
children | ac5c14a317f1 |
line wrap: on
line diff
--- a/nt/README Sun May 05 11:33:57 2002 +0000 +++ b/nt/README Mon May 06 14:16:31 2002 +0000 @@ -7,9 +7,9 @@ This is a port of XEmacs to Windows 95/98/NT/2000. If you are looking for a port of GNU Emacs, see http://www.cs.washington.edu/homes/voelker/ntemacs.html. -NT 3.51 or later is required for building on Windows NT. Note that the +NT 4.0 or later is required for building on Windows NT. Note that the developers typically use NT 4.0 and Windows 2000, and there may possibly be -problems under Windows 95/98 and NT 3.51. If so, please report them to +problems under Windows 95/98. If so, please report them to xemacs-nt@xemacs.org; we are committed to maintaining compatibility with all systems listed. @@ -20,7 +20,7 @@ Note that Visual C++ assumes that the environment variables INCLUDE and LIB are set to specify the location of the includes and libraries. - Your PATH environment variable also needs to include the DevStudio + Your PATH environment variable also needs to include the Visual Studio vc\bin and sharedide\bin directories. Visual C++ V5.0 and later install a batch file called vcvars32.bat in @@ -86,11 +86,11 @@ for more than 15 days. XEmacs also runs (barely) under the free XWin server that comes as part of the Cygwin XFree86 package, available at - ftp://sources.redhat.com/pub/cygwin/xfree/ + ftp://sources.redhat.com/pub/cygwin/xfree/ or numerous mirrors, such as - ftp://ftp.freesoftware.com/pub/sourceware/cygwin/xfree/ + ftp://ftp.freesoftware.com/pub/sourceware/cygwin/xfree/ There are numerous other X servers available in the same package or at the same location, but unfortunately most of them behave even worse @@ -113,16 +113,16 @@ * Optional libraries ==================== -1. You really want the XPM library. Grab the latest version of the - xpm sources (xpm-3.4k.tar.gz at time of writing) from - ftp://ftp.xemacs.org/pub/xemacs/aux/ and unpack them somewhere. - Copy nt\xpm.mak from the xemacs sources to the lib subdirectory of the - xpm sources, cd to that directory and build xpm with 'nmake -f xpm.mak'. +1. You really want the XPM library. Grab the latest version of the xpm + sources (xpm-3.4k.tar.gz as of 2002-04-27) from + ftp://ftp.xemacs.org/pub/xemacs/aux/ and unpack them somewhere. Copy + nt\xpm.mak from the xemacs sources to the lib subdirectory of the xpm + sources, cd to that directory and build xpm with 'nmake -f xpm.mak'. -2. You probably also want PNG image support. Grab the latest versions of zlib - and libpng (zlib-1.1.4 and libpng-1.0.9 at time of writing) from - ftp://ftp.xemacs.org/pub/xemacs/aux/, unpack them somewhere and read - the respective READMEs for details on how to build them. The following +2. You probably also want PNG image support. Grab the latest versions of + zlib and libpng (zlib-1.1.4 and libpng-1.0.9 as of 2002-04-27) from + ftp://ftp.xemacs.org/pub/xemacs/aux/, unpack them somewhere and read the + respective READMEs for details on how to build them. The following build procedure works for zlib-1.1.4 and libpng-1.0.9: cd to the zlib directory and type 'nmake -f msdos\makefile.w32'. @@ -131,16 +131,16 @@ and type 'nmake -f scripts\makefile.vcwin32'. 3. If you want TIFF support, grap the latest version of libtiff (tiff-v3.4 - at time of writing) from ftp://ftp.xemacs.org/pub/xemacs/aux/ and unpack + as of 2002-04-27) from ftp://ftp.xemacs.org/pub/xemacs/aux/ and unpack it somewhere. Copy nt\tiff.mak from the xemacs sources to the contrib\winnt subdirectory of the tiff sources, cd to that directory and build libtiff with 'nmake -f tiff.mak'. Note: tiff.mak has only been verified to work under WinNT, not Win95 or 98. However, the latest - distribution of libtiff includes a contrib\win95\makefile.w95; that might - work. + distribution of libtiff includes a contrib\win95\makefile.w95; that + might work. -4. If you want JPEG support grab the latest version of jpegsrc (jpeg-6b at - time of writing) from ftp://ftp.xemacs.org/pub/xemacs/aux/ and read the +4. If you want JPEG support grab the latest version of jpegsrc (jpeg-6b as + of 2002-04-27) from ftp://ftp.xemacs.org/pub/xemacs/aux/ and read the README for details on how to build it. 5. If you want X-Face support, grab the compface distribution from @@ -220,7 +220,7 @@ INSTALL_DIR="x:\your\installation\directory" (By default, XEmacs will be installed in directories under the directory - "c:\Program Files\XEmacs\XEmacs-21.2".) + "c:\Program Files\XEmacs\XEmacs-21.5".) 3. If you want to build xemacs on the command line, use `nmake install -f xemacs.mak', or just `nmake -f xemacs.mak' if you want @@ -230,23 +230,22 @@ If you chose to install XEmacs, the file that you should run to start XEmacs will be installed (by default) as - "c:\Program Files\XEmacs\XEmacs-21.2\i586-pc-win32\xemacs.exe". + "c:\Program Files\XEmacs\XEmacs-21.5\i586-pc-win32\xemacs.exe". - To run from the build directory, run the file "nt\xemacs.exe" off of the + To run from the build directory, run the file "src\xemacs.exe" off of the root of the build directory. You may want to create a shortcut to the file from your Desktop or Start Menu. 4. To build using MS Developer Studio, you can use the workspace file - `nt/xemacs.dsw'. This was prepared for Visual C++ 6.0. If you are using - Visual C++ 5.0, you can use the workspace file `nt/xemacs-vc50.dsw'. If - you have a different version and neither file works, just open up - `nt/xemacs.mak' from within MS Developer Studio and it will offer to wrap - this Makefile in a workspace file, from which you can build. Assuming - you want to run from the build directory (which you will want to do if - you are planning on doing any development work on XEmacs), use the - following settings in Project/Settings...: + `nt/xemacs.dsw'. This was prepared for Visual C++ 6.0. If you have a + different version and neither file works, just open up `nt/xemacs.mak' + from within MS Developer Studio and it will offer to wrap this Makefile + in a workspace file, from which you can build. Assuming you want to run + from the build directory (which you will want to do if you are planning + on doing any development work on XEmacs), use the following settings in + Project/Settings...: Under the General tab: