Mercurial > hg > xemacs-beta

comparison nt/README @ 373:6240c7796c7a r21-2b2

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Import from CVS: tag r21-2b2
author cvs
date Mon, 13 Aug 2007 11:04:06 +0200
parents cc15677e0335
children bbff43aa5eb7
comparison
equal deleted inserted replaced
372:49e1ed2d7ed8 373:6240c7796c7a
8 and others who worked on the GNU Emacs port to NT. Their version is available 8 and others who worked on the GNU Emacs port to NT. Their version is available
9 from http://www.cs.washington.edu/homes/voelker/ntemacs.html 9 from http://www.cs.washington.edu/homes/voelker/ntemacs.html
10 10
11 To get it working you will need: 11 To get it working you will need:
12 12
13 1. You will need Visual C++ V4.2 or later to compile everything. Personally we 13 1. You will need Visual C++ V4.0 or later to compile everything. Personally we
14 have tested V4.2 and V5.0. 14 have tested V4.0, V4.2 and V5.0.
15 Note that Visual C++ assumes a couple of environment variables INCLUDE and 15 Note that Visual C++ assumes a couple of environment variables INCLUDE and
16 LIB to be set which specify the location of the includes and libraries. 16 LIB to be set which specify the location of the includes and libraries.
17 At this point you can select X or Win32 native support. 17 Your PATH environment variable also needs to include the DevStudio vc\bin
18 and sharedide\bin directories.
19 Visual C++ V5.0 installs a batch file called vcvars32.bat in
20 c:\Program Files\DevStudio\VC\bin\ (or wherever you installed it) that you
21 can run before building to set up all of these environment variables.
18 22
19 2. Grab the latest XEmacs source from ftp.xemacs.org if necessary. All Win32 23 2. Grab the latest XEmacs source from ftp.xemacs.org if necessary. All Win32
20 support is in the nt\ subdirectory. You'll also need the xemacs-base 24 support is in the nt\ subdirectory. You'll also need the xemacs-base
21 package from the binary-packages subdirectory and you'll probably also 25 package from the binary-packages subdirectory and you'll probably also
22 want at least the edit-utils, text-utils, cc-mode and prog-utils packages. 26 want at least the edit-utils, text-utils, cc-mode and prog-utils packages.
23 Unpack the packages into, say, "c:\Program Files\XEmacs\packages". 27 Unpack the packages into, say, "c:\Program Files\XEmacs\packages".
24 28
29 3. At this point you can select X or Win32 native GUI support.
25 30
26 If you want to build for native GUI: 31 If you want to build for native GUI:
27 32
28 1. If you want XPM and toolbar support grab the latest version of the xpm 33 1. If you want XPM image and toolbar support grab the latest version of the
29 sources (xpm-3.4k.tar.gz at time of writing) and unpack them somewhere. 34 xpm sources (xpm-3.4k.tar.gz at time of writing) and unpack them somewhere.
30 Copy nt\xpm.mak from the xemacs sources to the lib subdirectory of the 35 Copy nt\xpm.mak from the xemacs sources to the lib subdirectory of the
31 xpm sources, cd to that directory and build xpm with `nmake -f xpm.mak`. 36 xpm sources, cd to that directory and build xpm with 'nmake -f xpm.mak'.
32 37
33 2. cd to the nt subdirectory of the xemacs distribution and build xemacs: 38 2. You probably also want PNG image support. Grab the latest versions of zlib
39 and libpng (zlib-1.1.3 and libpng-1.0.2 at time of writing), unpack them
40 somewhere and read the respective READMEs for details on how to build them.
41 The following build procedure works for zlib-1.1.3 and libpng-1.0.2:
42
43 cd to the zlib directory, type 'copy msdos\makefile.w32 Makefile' and
44 then type 'nmake'.
45
46 cd to the libpng directory, rename or move the zlib directory to ..\zlib
47 and type 'nmake -f scripts\makefile.w32'.
48
49 3. If you want TIFF support, grap the latest version of libtiff (tiff-v3.4
50 at time of writing) and unpack it somewhere. Copy nt\tiff.mak from the
51 xemacs sources to the contrib\winnt subdirectory of the tiff sources,
52 cd to that directory and build libtiff with 'nmake -f tiff.mak'. Note:
53 tiff.mak has only been verified to work under WinNT, not Win95 or 98.
54 However, the lastest distribution of libtiff includes a
55 contrib\win95\makefile.w95; that might work.
56
57 4. If you want JPEG support grab the latest version of jpegsrc (jpeg-6b at
58 time of writing) and read the README for details on how to build it.
59
60 5. cd to the nt subdirectory of the xemacs distribution and build xemacs:
34 `nmake install -f xemacs.mak`, but read on before hitting Enter. 61 `nmake install -f xemacs.mak`, but read on before hitting Enter.
35 62
36 3. If you're building with XPM support, add this to the nmake command line: 63 6. If you're building with XPM support, add this to the nmake command line:
37 HAVE_XPM=1 XPM_DIR="x:\location\of\your\xpm\source\tree" 64 HAVE_XPM=1 XPM_DIR="x:\location\of\your\xpm\sources"
65 and similarly for JPEG and TIFF support.
38 66
39 4. By default, XEmacs will look for packages in 67 If you're building with PNG support, add this to the nmake command line:
68 HAVE_PNG=1 PNG_DIR="x:\location\of\your\png\sources"
69 ZLIB_DIR="x:\location\of\your\zlib\sources"
70
71 If you want to build with GIF support, add this to the nmake command line:
72 HAVE_GIF=1
73
74 7. By default, XEmacs will look for packages in
40 "c:\Program Files\XEmacs\packages". If you want it to look elsewhere, 75 "c:\Program Files\XEmacs\packages". If you want it to look elsewhere,
41 add this to the nmake command line: 76 add this to the nmake command line:
42 PACKAGEPATH="x:\\location\\of\\your\\packages" 77 PACKAGEPATH="x:\\location\\of\\your\\packages"
43 Note the doubled-up backslashes in that path. If you want to change the 78 Note the doubled-up backslashes in that path. If you want to change the
44 package path after you've already built XEmacs, delete the file 79 package path after you've already built XEmacs, delete the file
45 .\obj\emacs.obj and rebuild with the new value of PACKAGEPATH. 80 .\obj\emacs.obj before rebuilding with the new value of PACKAGEPATH.
46 81
47 5. By default, XEmacs will be installed in directories under the directory 82 8. By default, XEmacs will be installed in directories under the directory
48 "c:\Program Files\XEmacs\XEmacs-21.0". If you want to install it 83 "c:\Program Files\XEmacs\XEmacs-21.0". If you want to install it
49 elsewhere, add this to the nmake command line: 84 elsewhere, add this to the nmake command line:
50 INSTALL_DIR="x:\your\installation\directory" 85 INSTALL_DIR="x:\your\installation\directory"
51 86
52 6. Now you can press Enter. nmake will build temacs, the DOC file, update the 87 9. Now you can press Enter. nmake will build temacs, the DOC file, update the
53 elc's, dump xemacs and install the relevant files in the directories under 88 elc's, dump xemacs and install the relevant files in the directories under
54 the installation directory. Unless you set INSTALL_DIR in step 5 above, the 89 the installation directory. Unless you set INSTALL_DIR above, the file that
55 file that you should run to start XEmacs will be installed as 90 you should run to start XEmacs will be installed as
56 "c:\Program Files\XEmacs\XEmacs-21.0\i386-pc-win32\runemacs.exe". You may 91 "c:\Program Files\XEmacs\XEmacs-21.0\i386-pc-win32\runemacs.exe". You may
57 want to create a shortcut to that file from your Desktop or Start Menu. 92 want to create a shortcut to that file from your Desktop or Start Menu.
58 93
59 7. The build process always creates debugging and "Source Browser" information 94 10. The build process always creates debugging and "Source Browser" information
60 in the source tree for use with MS DevStudio. If you actually want to debug 95 in the source tree for use with MS DevStudio. If you actually want to debug
61 XEmacs you should run XEmacs from the source directory instead of from the 96 XEmacs you should run XEmacs from the source directory instead of from the
62 installation directory. You should probably also build a debug version of 97 installation directory. You should probably also build a debug version of
63 XEmacs; to do this start with a clean source tree and add DEBUG_XEMACS=1 to 98 XEmacs; to do this start with a clean source tree and add DEBUG_XEMACS=1 to
64 the nmake command line. You probably don't want to install your debug build 99 the nmake command line. You probably don't want to install your debug build