Mercurial > hg > xemacs-beta

comparison nt/README @ 371:cc15677e0335 r21-2b1

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