Mercurial > hg > xemacs-beta

comparison nt/README @ 900:ac5c14a317f1

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[xemacs-hg @ 2002-07-05 19:18:54 by jhar] Document Visual Studio .NET setup
author jhar
date Fri, 05 Jul 2002 19:18:54 +0000
parents 28426972f654
children 26137a2aa3bb
comparison
equal deleted inserted replaced
899:08513f26c519 900:ac5c14a317f1
1 Building and Installing XEmacs on Windows 95/98/NT/2000 -*- mode:outline -*- 1 Building and Installing XEmacs on Windows 95/98/NT/2000/XP -*- mode:outline -*-
2 2
3 David Hobley 3 David Hobley
4 Marc Paquette 4 Marc Paquette
5 Jonathan Harris 5 Jonathan Harris
6 Ben Wing 6 Ben Wing
7 7
8 This is a port of XEmacs to Windows 95/98/NT/2000. If you are looking for a 8 This is a port of XEmacs to Windows 95/98/NT/2000/XP. If you are looking for a
9 port of GNU Emacs, see http://www.cs.washington.edu/homes/voelker/ntemacs.html. 9 port of GNU Emacs, see http://www.cs.washington.edu/homes/voelker/ntemacs.html.
10 NT 4.0 or later is required for building on Windows NT. Note that the 10 NT 4.0 or later is required for building on Windows NT. Note that the
11 developers typically use NT 4.0 and Windows 2000, and there may possibly be 11 developers typically use NT 4.0 and Windows 2000, and there may possibly be
12 problems under Windows 95/98. If so, please report them to 12 problems under Windows 95/98. If so, please report them to
13 xemacs-nt@xemacs.org; we are committed to maintaining compatibility with all 13 xemacs-nt@xemacs.org; we are committed to maintaining compatibility with all
14 systems listed. 14 systems listed.
15 15
16 * Required tools and sources 16 * Required tools and sources
17 ============================ 17 ============================
18 18
19 1. You will need Visual C++ V6.0 or later to compile everything. 19 1. You will need Visual C++ V6.0, Visual Studio .NET or later to compile
20 everything.
20 21
21 Note that Visual C++ assumes that the environment variables INCLUDE and 22 Note that Visual C++ assumes that the environment variables INCLUDE and
22 LIB are set to specify the location of the includes and libraries. 23 LIB are set to specify the location of the includes and libraries.
23 Your PATH environment variable also needs to include the Visual Studio 24 Your PATH environment variable also needs to include the Visual Studio
24 vc\bin and sharedide\bin directories. 25 vc\bin and sharedide\bin directories.
25 26
26 Visual C++ V5.0 and later install a batch file called vcvars32.bat in 27 Visual C++ V6.0 installs a batch file called vcvars32.bat in
27 c:\Program Files\Microsoft Visual Studio\VC98\bin\ (or wherever you 28 c:\Program Files\Microsoft Visual Studio\VC98\bin\ (or wherever you
28 installed it) that you can run before building to set up all of these 29 installed it) that you can run before building to set up all of these
29 environment variables. Alternatively, you can choose at setup time to 30 environment variables. Alternatively, you can choose at setup time to
30 have these environment variables automatically set up in the registry, 31 have these environment variables automatically set up in the registry,
31 which is generally a good idea. 32 which is generally a good idea.
32 33
34 Visual Studio .NET calls this batch file vsvars32.bat and installs it in
35 $Installdir\Common7\Tools, but doesn't offer at install time to
36 automatically set these environment variables up in the registry.
33 37
34 2. Grab the latest XEmacs source from 38 2. Grab the latest XEmacs source from
35 39
36 ftp://ftp.xemacs.org/pub/xemacs/ 40 ftp://ftp.xemacs.org/pub/xemacs/
37 41
236 root of the build directory. 240 root of the build directory.
237 241
238 You may want to create a shortcut to the file from your Desktop or 242 You may want to create a shortcut to the file from your Desktop or
239 Start Menu. 243 Start Menu.
240 244
241 4. To build using MS Developer Studio, you can use the workspace file 245 4. To build using MS Visual Studio, you can use the workspace file
242 `nt/xemacs.dsw'. This was prepared for Visual C++ 6.0. If you have a 246 `nt/xemacs.dsw'. This was prepared for Visual C++ 6.0. If you have a
243 different version and neither file works, just open up `nt/xemacs.mak' 247 different version and neither file works, just open up `nt/xemacs.mak'
244 from within MS Developer Studio and it will offer to wrap this Makefile 248 from within Visual Studio and it will offer to wrap this Makefile in a
245 in a workspace file, from which you can build. Assuming you want to run 249 workspace file, from which you can build. Assuming you want to run from
246 from the build directory (which you will want to do if you are planning 250 the build directory (which you will want to do if you are planning on
247 on doing any development work on XEmacs), use the following settings in 251 doing any development work on XEmacs), use the following settings in
248 Project/Settings...: 252 Project/Settings...:
249 253
250 Under the General tab: 254 Under the General tab:
251 255
252 Build command line: NMAKE /f xemacs.mak 256 Build command line: NMAKE /f xemacs.mak