|
169
|
1 Building and Installing XEmacs on Windows NT
|
|
155
|
2
|
|
169
|
3 David Hobley
|
|
|
4 Marc Paquette
|
|
215
|
5 Jonathan Harris
|
|
155
|
6
|
|
169
|
7 The port was made much easier by the groundbreaking work of Geoff Voelker
|
|
|
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
|
|
|
10
|
|
|
11 To get it working you will need:
|
|
155
|
12
|
|
308
|
13 1. You will need Visual C++ V4.0 or later to compile everything. Personally we
|
|
|
14 have tested V4.0, V4.2 and V5.0.
|
|
213
|
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.
|
|
308
|
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.
|
|
298
|
22
|
|
|
23 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
|
|
|
25 package from the binary-packages subdirectory and you'll probably also
|
|
327
|
26 want at least the edit-utils, text-modes, fsf-compat, cc-mode,
|
|
|
27 prog-modes and xemacs-devel packages.
|
|
|
28 Unpack the packages into, say, "c:\Program Files\XEmacs\xemacs-packages".
|
|
298
|
29
|
|
308
|
30 3. At this point you can select X or Win32 native GUI support.
|
|
276
|
31
|
|
|
32 If you want to build for native GUI:
|
|
|
33
|
|
314
|
34 1. If you want XPM image and toolbar support grab the latest version of the
|
|
|
35 xpm sources (xpm-3.4k.tar.gz at time of writing) and unpack them somewhere.
|
|
298
|
36 Copy nt\xpm.mak from the xemacs sources to the lib subdirectory of the
|
|
314
|
37 xpm sources, cd to that directory and build xpm with 'nmake -f xpm.mak'.
|
|
|
38
|
|
|
39 2. You probably also want PNG image support. Grab the latest versions of zlib
|
|
|
40 and libpng (zlib-1.1.3 and libpng-1.0.2 at time of writing), unpack them
|
|
|
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:
|
|
298
|
43
|
|
314
|
44 cd to the zlib directory, type 'copy msdos\makefile.w32 Makefile' and
|
|
|
45 then type 'nmake'.
|
|
|
46
|
|
|
47 cd to the libpng directory, rename or move the zlib directory to ..\zlib
|
|
|
48 and type 'nmake -f scripts\makefile.w32'.
|
|
|
49
|
|
318
|
50 3. If you want TIFF support, grap the latest version of libtiff (tiff-v3.4
|
|
|
51 at time of writing) and unpack it somewhere. Copy nt\tiff.mak from the
|
|
|
52 xemacs sources to the contrib\winnt subdirectory of the tiff sources,
|
|
|
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 lastest distribution of libtiff includes a
|
|
|
56 contrib\win95\makefile.w95; that might work.
|
|
314
|
57
|
|
318
|
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:
|
|
329
|
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.
|
|
298
|
64
|
|
318
|
65 6. If you're building with XPM support, add this to the nmake command line:
|
|
314
|
66 HAVE_XPM=1 XPM_DIR="x:\location\of\your\xpm\sources"
|
|
|
67 and similarly for JPEG and TIFF support.
|
|
298
|
68
|
|
314
|
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
|
|
327
|
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.
|
|
298
|
84
|
|
318
|
85 8. By default, XEmacs will be installed in directories under the directory
|
|
327
|
86 "c:\Program Files\XEmacs\XEmacs-21.0". If you want to install it elsewhere,
|
|
|
87 add this to the nmake command line:
|
|
298
|
88 INSTALL_DIR="x:\your\installation\directory"
|
|
|
89
|
|
318
|
90 9. Now you can press Enter. nmake will build temacs, the DOC file, update the
|
|
298
|
91 elc's, dump xemacs and install the relevant files in the directories under
|
|
314
|
92 the installation directory. Unless you set INSTALL_DIR above, the file that
|
|
327
|
93 you should run to start XEmacs will be installed as
|
|
298
|
94 "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.
|
|
|
96
|
|
318
|
97 10. The build process always creates debugging and "Source Browser" information
|
|
298
|
98 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
|
|
|
100 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
|
|
|
102 the nmake command line. You probably don't want to install your debug build
|
|
|
103 so you should tell nmake to build the 'all' target instead of the 'install'
|
|
|
104 target.
|
|
|
105
|
|
|
106 To make use of the debugging and "Source Browser" information, create a new
|
|
|
107 "console" project in MS DevStudio and, under Project/Settings, set:
|
|
276
|
108 Debug: executable name = full path of src\xemacs.exe
|
|
|
109 Link: output file name = full path of src\temacs.exe
|
|
|
110 Browse Info: browse info file name = full path of src\temacs.bsc
|
|
|
111 Remember to close the Source Browser file in DevStudio before rebuilding.
|
|
213
|
112
|
|
298
|
113
|
|
213
|
114 If you want support for X you will need:
|
|
|
115
|
|
195
|
116 1. An X server. MI/X is available on the Internet for free; It is
|
|
|
117 available from: http://www.microimages.com/www/html/freestuf/mixdlfrm.htm
|
|
298
|
118
|
|
195
|
119 2. The MIT X11R6.3 libraries available from: ftp.x.org
|
|
298
|
120
|
|
195
|
121 3. You'll need to compile the MIT libraries without multi-thread support.
|
|
|
122 To do this, there is an example Win32.cf and site.def provided which
|
|
|
123 set the relevant flags. You will also need to apply the patch in
|
|
|
124 nt/X11.patch in the xc/lib/X11 directory which will fix the DLL definition
|
|
|
125 file. Once compiled and installed, you will need to apply the following
|
|
|
126 patch to Xmd.h. This is messy and better solutions would be appreciated.
|
|
298
|
127
|
|
|
128 4. Goto 2 under 'native GUI' above and add this to the nmake command line:
|
|
|
129 HAVE_X=1 X11_DIR=x:\root\directory\of\your\X11\installation
|
|
155
|
130
|
|
|
131 --- Xmd.h~ Thu Jun 08 23:20:40 1995
|
|
|
132 +++ Xmd.h Sun Mar 16 13:09:10 1997
|
|
|
133 @@ -150,8 +150,9 @@
|
|
|
134 typedef CARD16 BITS16;
|
|
|
135 typedef CARD8 BYTE;
|
|
|
136
|
|
|
137 +#ifndef WIN32
|
|
|
138 typedef CARD8 BOOL;
|
|
|
139 -
|
|
|
140 +#endif
|
|
195
|
141
|
|
169
|
142 Known Problems:
|
|
|
143 Please look at the TODO list for the current list of problems and people
|
|
|
144 working on them.
|
|
|
145
|
|
|
146 Any other problems you need clarified, please email us and we will endeavour
|
|
|
147 to provide any assistance we can:
|
|
155
|
148
|
|
213
|
149 The XEmacs NT Mailing List: xemacs-nt@xemacs.org
|
|
|
150 Subscribe address: xemacs-nt-request@xemacs.org
|
|
155
|
151
|
|
213
|
152 David Hobley
|
|
|
153 Marc Paquette
|
|
|
154 August Hill
|
|
215
|
155 Jonathan Harris
|
|
155
|
156
|
|
213
|
157 and others.
|
