|
900
|
1 Building and Installing XEmacs on Windows 95/98/NT/2000/XP -*- mode:outline -*-
|
|
428
|
2
|
|
|
3 David Hobley
|
|
442
|
4 Marc Paquette
|
|
|
5 Jonathan Harris
|
|
|
6 Ben Wing
|
|
428
|
7
|
|
900
|
8 This is a port of XEmacs to Windows 95/98/NT/2000/XP. If you are looking for a
|
|
916
|
9 port of GNU Emacs, get the latest release of the 21.x series from gnu.org.
|
|
|
10 (At the time of writing, GNU Emacs does not support images but does support
|
|
|
11 Mule.) NT 4.0 or later is required for building on Windows NT. Note that the
|
|
442
|
12 developers typically use NT 4.0 and Windows 2000, and there may possibly be
|
|
827
|
13 problems under Windows 95/98. If so, please report them to
|
|
442
|
14 xemacs-nt@xemacs.org; we are committed to maintaining compatibility with all
|
|
|
15 systems listed.
|
|
428
|
16
|
|
442
|
17 * Required tools and sources
|
|
|
18 ============================
|
|
|
19
|
|
900
|
20 1. You will need Visual C++ V6.0, Visual Studio .NET or later to compile
|
|
|
21 everything.
|
|
428
|
22
|
|
442
|
23 Note that Visual C++ assumes that the environment variables INCLUDE and
|
|
|
24 LIB are set to specify the location of the includes and libraries.
|
|
827
|
25 Your PATH environment variable also needs to include the Visual Studio
|
|
442
|
26 vc\bin and sharedide\bin directories.
|
|
|
27
|
|
900
|
28 Visual C++ V6.0 installs a batch file called vcvars32.bat in
|
|
812
|
29 c:\Program Files\Microsoft Visual Studio\VC98\bin\ (or wherever you
|
|
|
30 installed it) that you can run before building to set up all of these
|
|
|
31 environment variables. Alternatively, you can choose at setup time to
|
|
|
32 have these environment variables automatically set up in the registry,
|
|
|
33 which is generally a good idea.
|
|
428
|
34
|
|
900
|
35 Visual Studio .NET calls this batch file vsvars32.bat and installs it in
|
|
|
36 $Installdir\Common7\Tools, but doesn't offer at install time to
|
|
|
37 automatically set these environment variables up in the registry.
|
|
442
|
38
|
|
|
39 2. Grab the latest XEmacs source from
|
|
|
40
|
|
|
41 ftp://ftp.xemacs.org/pub/xemacs/
|
|
|
42
|
|
|
43 or one of its mirrors listed at http://www.xemacs.org/Download/index.html.
|
|
|
44
|
|
|
45 (NOTE: If you are behind a firewall and have problems with FTP access,
|
|
|
46 the URL http://ftp.xemacs.org/pub/xemacs/ works just as well.)
|
|
|
47
|
|
|
48 You'll also need the packages. You probably want to get the unified
|
|
|
49 packages bundle from
|
|
|
50
|
|
|
51 ftp://ftp.xemacs.org/pub/xemacs/packages/xemacs-sumo.tar.gz
|
|
|
52
|
|
|
53 If you are building with international support, you also need
|
|
|
54
|
|
|
55 ftp://ftp.xemacs.org/pub/xemacs/packages/xemacs-mule-sumo.tar.gz
|
|
|
56
|
|
|
57 Although we don't recommend it, you can also retrieve just the packages
|
|
|
58 you really need if you have an extremely slow net connection or are very
|
|
|
59 short on disk space. You can find the various packages in
|
|
|
60 ftp://ftp.xemacs.org/pub/xemacs/packages/. You will need the xemacs-base
|
|
|
61 package (and mule-base, if building with international support). You'll
|
|
|
62 also need the texinfo package unless you have a copy of makeinfo.exe on
|
|
|
63 your machine. If you want to download additional or updated packages
|
|
|
64 from within XEmacs you'll need the efs, dired and vm packages. You'll
|
|
|
65 probably also want at least the edit-utils, text-modes, fsf-compat,
|
|
|
66 cc-mode, prog-modes and xemacs-devel packages.
|
|
|
67
|
|
|
68 Unpack the packages into "x:\your\choice\XEmacs\xemacs-packages",
|
|
|
69 for example "c:\Program Files\XEmacs\xemacs-packages".
|
|
|
70
|
|
|
71 3. At this point you can choose to build for X and/or for Win32 native GUI.
|
|
|
72 If you only want to build for the Win32 native GUI then skip the next
|
|
|
73 section.
|
|
|
74
|
|
|
75
|
|
|
76 ** Extra tools and sources required for X
|
|
428
|
77
|
|
442
|
78 NOTE: XEmacs has not been tested with X support under the native
|
|
|
79 Windows build for a long, long time! It may not even compile any
|
|
|
80 more. If you are interested in X support, you're better off compiling
|
|
|
81 the Cygwin version of XEmacs, which can handle both Win32 native and X
|
|
|
82 frames (in the same binary, in fact, but not at the same time), and is
|
|
|
83 actively tested with X support.
|
|
|
84
|
|
|
85 If you want support for X you will also need:
|
|
|
86
|
|
|
87 1. An X server. XEmacs has been tested and runs well under MI/X,
|
|
|
88 available from: http://www.microimages.com/mix/. (International aka
|
|
|
89 "Mule" support even works under this X server!) Unfortunately, this is
|
|
|
90 not free, but is trialware; you have to pay $25 if you want to use it
|
|
|
91 for more than 15 days. XEmacs also runs (barely) under the free XWin
|
|
|
92 server that comes as part of the Cygwin XFree86 package, available at
|
|
|
93
|
|
827
|
94 ftp://sources.redhat.com/pub/cygwin/xfree/
|
|
442
|
95
|
|
|
96 or numerous mirrors, such as
|
|
|
97
|
|
827
|
98 ftp://ftp.freesoftware.com/pub/sourceware/cygwin/xfree/
|
|
428
|
99
|
|
442
|
100 There are numerous other X servers available in the same package or at
|
|
|
101 the same location, but unfortunately most of them behave even worse
|
|
|
102 than XWin. If you have any luck with any of these, *PLEASE* email
|
|
|
103 the maintainers at xemacs-nt@xemacs.org, and we'll add the info here.
|
|
|
104
|
|
|
105 2. Source for the MIT X11R6.3 libraries, available from ftp.x.org.
|
|
|
106
|
|
|
107 3. You'll need to compile the MIT libraries without multi-thread support.
|
|
|
108 To do this, there is an example Win32.cf and site.def provided which set
|
|
|
109 the relevant flags. You will also need to apply the patch in nt/X11.patch
|
|
|
110 in the xc/lib/X11 directory which will fix the DLL definition file.
|
|
428
|
111
|
|
442
|
112 Once compiled and installed, you will need to apply the patch in
|
|
|
113 nt/Xmd.patch. This is messy and better solutions would be appreciated.
|
|
|
114
|
|
|
115 4. Goto step 2 under 'Optional libraries' below.
|
|
|
116
|
|
|
117
|
|
|
118 * Optional libraries
|
|
|
119 ====================
|
|
|
120
|
|
827
|
121 1. You really want the XPM library. Grab the latest version of the xpm
|
|
|
122 sources (xpm-3.4k.tar.gz as of 2002-04-27) from
|
|
|
123 ftp://ftp.xemacs.org/pub/xemacs/aux/ and unpack them somewhere. Copy
|
|
|
124 nt\xpm.mak from the xemacs sources to the lib subdirectory of the xpm
|
|
|
125 sources, cd to that directory and build xpm with 'nmake -f xpm.mak'.
|
|
428
|
126
|
|
827
|
127 2. You probably also want PNG image support. Grab the latest versions of
|
|
|
128 zlib and libpng (zlib-1.1.4 and libpng-1.0.9 as of 2002-04-27) from
|
|
|
129 ftp://ftp.xemacs.org/pub/xemacs/aux/, unpack them somewhere and read the
|
|
|
130 respective READMEs for details on how to build them. The following
|
|
817
|
131 build procedure works for zlib-1.1.4 and libpng-1.0.9:
|
|
428
|
132
|
|
817
|
133 cd to the zlib directory and type 'nmake -f msdos\makefile.w32'.
|
|
428
|
134
|
|
|
135 cd to the libpng directory, rename or move the zlib directory to ..\zlib
|
|
817
|
136 and type 'nmake -f scripts\makefile.vcwin32'.
|
|
428
|
137
|
|
|
138 3. If you want TIFF support, grap the latest version of libtiff (tiff-v3.4
|
|
827
|
139 as of 2002-04-27) from ftp://ftp.xemacs.org/pub/xemacs/aux/ and unpack
|
|
442
|
140 it somewhere. Copy nt\tiff.mak from the xemacs sources to the
|
|
|
141 contrib\winnt subdirectory of the tiff sources, cd to that directory and
|
|
|
142 build libtiff with 'nmake -f tiff.mak'. Note: tiff.mak has only been
|
|
444
|
143 verified to work under WinNT, not Win95 or 98. However, the latest
|
|
827
|
144 distribution of libtiff includes a contrib\win95\makefile.w95; that
|
|
|
145 might work.
|
|
428
|
146
|
|
827
|
147 4. If you want JPEG support grab the latest version of jpegsrc (jpeg-6b as
|
|
|
148 of 2002-04-27) from ftp://ftp.xemacs.org/pub/xemacs/aux/ and read the
|
|
442
|
149 README for details on how to build it.
|
|
428
|
150
|
|
442
|
151 5. If you want X-Face support, grab the compface distribution from
|
|
|
152 ftp://ftp.xemacs.org/pub/xemacs/aux/ and unpack it somewhere.
|
|
|
153 Copy nt\compface.mak from xemacs sources to the compface directory.
|
|
|
154 cd to that directory and build libcompface with 'nmake -f compface.mak'.
|
|
428
|
155
|
|
|
156
|
|
442
|
157 * Building
|
|
|
158 ==========
|
|
|
159
|
|
|
160 1. cd to the nt subdirectory of the xemacs distribution and copy the file
|
|
|
161 config.inc.samp to config.inc. Make any necessary modifications. This
|
|
|
162 file controls the options that XEmacs is built with:
|
|
|
163
|
|
|
164 -- If you want international (aka "Mule") support, modify the appropriate
|
|
|
165 line in config.inc as follows:
|
|
|
166
|
|
771
|
167 MULE=1
|
|
428
|
168
|
|
442
|
169 -- If you're building with XPM support, modify the appropriate lines in
|
|
|
170 config.inc as follows:
|
|
|
171
|
|
|
172 HAVE_XPM=1
|
|
|
173 XPM_DIR="x:\location\of\your\xpm\sources"
|
|
|
174
|
|
|
175 and similarly for JPEG and TIFF support.
|
|
428
|
176
|
|
442
|
177 -- If you're building with PNG support, modify the appropriate lines in
|
|
|
178 config.inc as follows:
|
|
|
179
|
|
|
180 HAVE_PNG=1
|
|
|
181 PNG_DIR="x:\location\of\your\png\sources"
|
|
|
182 ZLIB_DIR="x:\location\of\your\zlib\sources"
|
|
|
183
|
|
|
184 -- If you're building with GIF support, modify the appropriate lines in
|
|
|
185 config.inc as follows:
|
|
|
186
|
|
|
187 HAVE_GIF=1
|
|
428
|
188
|
|
442
|
189 -- If you're building with X-Face support, modify the appropriate lines in
|
|
|
190 config.inc as follows:
|
|
|
191
|
|
|
192 HAVE_XFACE=1
|
|
|
193 COMPFACE_DIR="x:\location\of\your\compface\sources"
|
|
|
194
|
|
|
195 -- If you're building for X, modify the appropriate lines in config.inc
|
|
|
196 as follows:
|
|
|
197
|
|
|
198 HAVE_X_WINDOWS=1
|
|
|
199 X11_DIR=x:\root\directory\of\your\X11\installation
|
|
|
200
|
|
|
201 -- By default, XEmacs will expect to find its packages in the
|
|
|
202 subdirectories "site-packages", "mule-packages" and "xemacs-packages"
|
|
|
203 under the directory "c:\Program Files\XEmacs". If you want it to look
|
|
|
204 for these subdirectories elsewhere, modify the appropriate lines in
|
|
|
205 config.inc as follows:
|
|
428
|
206
|
|
442
|
207 PACKAGE_PREFIX="x:\your\package\directory"
|
|
|
208
|
|
|
209 Make sure that the directory pointed to by PACKAGE_PREFIX contains
|
|
|
210 the xemacs-packages directory into which you installed the packages.
|
|
|
211
|
|
|
212 -- XEmacs can build its info files more quickly if you have a copy of the
|
|
|
213 makeinfo program. If you have a copy, modify the appropriate lines in
|
|
|
214 config.inc as follows:
|
|
|
215
|
|
|
216 MAKEINFO="x:\location\of\makeinfo.exe"
|
|
|
217
|
|
|
218 If you don't have a copy of makeinfo then you'll need to have installed
|
|
|
219 the XEmacs texinfo package.
|
|
|
220
|
|
|
221 2. If you want to install XEmacs when you build it, modify the appropriate
|
|
|
222 lines in config.inc as follows (you can also run XEmacs from its build
|
|
|
223 directory):
|
|
|
224
|
|
|
225 INSTALL_DIR="x:\your\installation\directory"
|
|
428
|
226
|
|
442
|
227 (By default, XEmacs will be installed in directories under the directory
|
|
827
|
228 "c:\Program Files\XEmacs\XEmacs-21.5".)
|
|
442
|
229
|
|
|
230 3. If you want to build xemacs on the command line, use
|
|
|
231 `nmake install -f xemacs.mak', or just `nmake -f xemacs.mak' if you want
|
|
|
232 to run XEmacs from its build directory. nmake will build temacs, the DOC
|
|
|
233 file, update the elc's, dump xemacs and (optionally) install the relevant
|
|
|
234 files in the directories under the installation directory.
|
|
|
235
|
|
|
236 If you chose to install XEmacs, the file that you should run to start
|
|
|
237 XEmacs will be installed (by default) as
|
|
827
|
238 "c:\Program Files\XEmacs\XEmacs-21.5\i586-pc-win32\xemacs.exe".
|
|
442
|
239
|
|
827
|
240 To run from the build directory, run the file "src\xemacs.exe" off of the
|
|
442
|
241 root of the build directory.
|
|
|
242
|
|
|
243 You may want to create a shortcut to the file from your Desktop or
|
|
|
244 Start Menu.
|
|
|
245
|
|
900
|
246 4. To build using MS Visual Studio, you can use the workspace file
|
|
827
|
247 `nt/xemacs.dsw'. This was prepared for Visual C++ 6.0. If you have a
|
|
|
248 different version and neither file works, just open up `nt/xemacs.mak'
|
|
900
|
249 from within Visual Studio and it will offer to wrap this Makefile in a
|
|
|
250 workspace file, from which you can build. Assuming you want to run from
|
|
|
251 the build directory (which you will want to do if you are planning on
|
|
|
252 doing any development work on XEmacs), use the following settings in
|
|
827
|
253 Project/Settings...:
|
|
442
|
254
|
|
|
255 Under the General tab:
|
|
|
256
|
|
|
257 Build command line: NMAKE /f xemacs.mak
|
|
|
258 Output file name: ..\src\xemacs.exe
|
|
|
259 Browse info file name: ..\src\temacs.bsc
|
|
|
260
|
|
|
261 Under the Debug tab:
|
|
428
|
262
|
|
442
|
263 Executable for debug session: ..\src\xemacs.exe
|
|
|
264
|
|
|
265
|
|
|
266 If you want to install XEmacs when it's built, change the build command
|
|
|
267 line to "NMAKE install /f xemacs.mak". (You will have to make the same
|
|
|
268 change even if you use the provided workspace nt/xemacs.dsw.)
|
|
|
269
|
|
|
270
|
|
|
271 * Debugging under MS Developer Studio
|
|
|
272 =====================================
|
|
|
273
|
|
|
274 The build process always creates debugging and "Source Browser" information
|
|
|
275 in the source tree for use with DevStudio. However that information is not
|
|
|
276 very useful unless you build a debug version of XEmacs:
|
|
|
277
|
|
|
278 1. Set DEBUG_XEMACS=1 and DEPEND=1 in config.inc and rebuild.
|
|
|
279
|
|
|
280 2. See instructions above for obtaining a workspace file for use with
|
|
|
281 MS Developer Studio. Build and debug your XEmacs this way.
|
|
|
282
|
|
|
283 3. To display the contents of a lisp variable, type Shift-F9 (or use the
|
|
|
284 menu) to bring up the QuickWatch window, type debug_print(variable) and
|
|
|
285 click Recalculate. The output will appear in a console window, as well
|
|
|
286 as in the Debug window in MS Developer Studio.
|
|
|
287
|
|
|
288 4. To view Lisp variables in the "Watch" window wrap the variable in one of
|
|
|
289 the helper functions from the file src\console-msw.c, for example type
|
|
|
290 DSTRING(variable) in the "Watch" window to inspect a Lisp string.
|
|
|
291
|
|
|
292
|
|
|
293 * Known Problems
|
|
|
294 ================
|
|
|
295
|
|
|
296 Please look at the PROBLEMS file for known problems. Any other problems you
|
|
|
297 need clarified, please email us and we will endeavour to provide any
|
|
|
298 assistance we can:
|
|
428
|
299
|
|
|
300 The XEmacs NT Mailing List: xemacs-nt@xemacs.org
|
|
|
301 Subscribe address: xemacs-nt-request@xemacs.org
|
|
|
302
|
|
442
|
303 Ben Wing (current primary MS Windows maintainer; author of the MS Windows
|
|
|
304 Mule code and some of the dialog box code)
|
|
|
305 Andy Piper (MS Windows contributor; author of the Cygwin support and the
|
|
|
306 MS Windows glyph and widget code)
|
|
|
307 Jonathan Harris (MS Windows contributor; author of the MS Windows redisplay
|
|
|
308 and underlying GUI code)
|
|
|
309 Kirill Katsnelson (MS Windows contributor; author of the MS Windows process
|
|
|
310 and printing code and some of the dialog box code;
|
|
|
311 general guru on obscure MS Windows programming topics)
|
|
|
312 David Hobley (early MS Windows contributor)
|
|
|
313 Marc Paquette (early MS Windows contributor)
|
|
|
314 August Hill (early MS Windows contributor)
|
|
428
|
315
|
|
|
316 and others.
|
