Mercurial > hg > xemacs-beta

comparison nt/README @ 827:28426972f654

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[xemacs-hg @ 2002-05-06 14:14:33 by jhar] Misc win32 native build and doc fixes
author jhar
date Mon, 06 May 2002 14:16:31 +0000
parents ece8c2170578
children ac5c14a317f1
comparison
equal deleted inserted replaced
826:6728e641994e 827:28426972f654
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. 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 3.51 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 and NT 3.51. 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 or later to compile everything.
20 20
21 Note that Visual C++ assumes that the environment variables INCLUDE and 21 Note that Visual C++ assumes that the environment variables INCLUDE and
22 LIB are set to specify the location of the includes and libraries. 22 LIB are set to specify the location of the includes and libraries.
23 Your PATH environment variable also needs to include the DevStudio 23 Your PATH environment variable also needs to include the Visual Studio
24 vc\bin and sharedide\bin directories. 24 vc\bin and sharedide\bin directories.
25 25
26 Visual C++ V5.0 and later install a batch file called vcvars32.bat in 26 Visual C++ V5.0 and later install a batch file called vcvars32.bat in
27 c:\Program Files\Microsoft Visual Studio\VC98\bin\ (or wherever you 27 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 28 installed it) that you can run before building to set up all of these
84 "Mule" support even works under this X server!) Unfortunately, this is 84 "Mule" support even works under this X server!) Unfortunately, this is
85 not free, but is trialware; you have to pay $25 if you want to use it 85 not free, but is trialware; you have to pay $25 if you want to use it
86 for more than 15 days. XEmacs also runs (barely) under the free XWin 86 for more than 15 days. XEmacs also runs (barely) under the free XWin
87 server that comes as part of the Cygwin XFree86 package, available at 87 server that comes as part of the Cygwin XFree86 package, available at
88 88
89 ftp://sources.redhat.com/pub/cygwin/xfree/ 89 ftp://sources.redhat.com/pub/cygwin/xfree/
90 90
91 or numerous mirrors, such as 91 or numerous mirrors, such as
92 92
93 ftp://ftp.freesoftware.com/pub/sourceware/cygwin/xfree/ 93 ftp://ftp.freesoftware.com/pub/sourceware/cygwin/xfree/
94 94
95 There are numerous other X servers available in the same package or at 95 There are numerous other X servers available in the same package or at
96 the same location, but unfortunately most of them behave even worse 96 the same location, but unfortunately most of them behave even worse
97 than XWin. If you have any luck with any of these, *PLEASE* email 97 than XWin. If you have any luck with any of these, *PLEASE* email
98 the maintainers at xemacs-nt@xemacs.org, and we'll add the info here. 98 the maintainers at xemacs-nt@xemacs.org, and we'll add the info here.
111 111
112 112
113 * Optional libraries 113 * Optional libraries
114 ==================== 114 ====================
115 115
116 1. You really want the XPM library. Grab the latest version of the 116 1. You really want the XPM library. Grab the latest version of the xpm
117 xpm sources (xpm-3.4k.tar.gz at time of writing) from 117 sources (xpm-3.4k.tar.gz as of 2002-04-27) from
118 ftp://ftp.xemacs.org/pub/xemacs/aux/ and unpack them somewhere. 118 ftp://ftp.xemacs.org/pub/xemacs/aux/ and unpack them somewhere. Copy
119 Copy nt\xpm.mak from the xemacs sources to the lib subdirectory of the 119 nt\xpm.mak from the xemacs sources to the lib subdirectory of the xpm
120 xpm sources, cd to that directory and build xpm with 'nmake -f xpm.mak'. 120 sources, cd to that directory and build xpm with 'nmake -f xpm.mak'.
121 121
122 2. You probably also want PNG image support. Grab the latest versions of zlib 122 2. You probably also want PNG image support. Grab the latest versions of
123 and libpng (zlib-1.1.4 and libpng-1.0.9 at time of writing) from 123 zlib and libpng (zlib-1.1.4 and libpng-1.0.9 as of 2002-04-27) from
124 ftp://ftp.xemacs.org/pub/xemacs/aux/, unpack them somewhere and read 124 ftp://ftp.xemacs.org/pub/xemacs/aux/, unpack them somewhere and read the
125 the respective READMEs for details on how to build them. The following 125 respective READMEs for details on how to build them. The following
126 build procedure works for zlib-1.1.4 and libpng-1.0.9: 126 build procedure works for zlib-1.1.4 and libpng-1.0.9:
127 127
128 cd to the zlib directory and type 'nmake -f msdos\makefile.w32'. 128 cd to the zlib directory and type 'nmake -f msdos\makefile.w32'.
129 129
130 cd to the libpng directory, rename or move the zlib directory to ..\zlib 130 cd to the libpng directory, rename or move the zlib directory to ..\zlib
131 and type 'nmake -f scripts\makefile.vcwin32'. 131 and type 'nmake -f scripts\makefile.vcwin32'.
132 132
133 3. If you want TIFF support, grap the latest version of libtiff (tiff-v3.4 133 3. If you want TIFF support, grap the latest version of libtiff (tiff-v3.4
134 at time of writing) from ftp://ftp.xemacs.org/pub/xemacs/aux/ and unpack 134 as of 2002-04-27) from ftp://ftp.xemacs.org/pub/xemacs/aux/ and unpack
135 it somewhere. Copy nt\tiff.mak from the xemacs sources to the 135 it somewhere. Copy nt\tiff.mak from the xemacs sources to the
136 contrib\winnt subdirectory of the tiff sources, cd to that directory and 136 contrib\winnt subdirectory of the tiff sources, cd to that directory and
137 build libtiff with 'nmake -f tiff.mak'. Note: tiff.mak has only been 137 build libtiff with 'nmake -f tiff.mak'. Note: tiff.mak has only been
138 verified to work under WinNT, not Win95 or 98. However, the latest 138 verified to work under WinNT, not Win95 or 98. However, the latest
139 distribution of libtiff includes a contrib\win95\makefile.w95; that might 139 distribution of libtiff includes a contrib\win95\makefile.w95; that
140 work. 140 might work.
141 141
142 4. If you want JPEG support grab the latest version of jpegsrc (jpeg-6b at 142 4. If you want JPEG support grab the latest version of jpegsrc (jpeg-6b as
143 time of writing) from ftp://ftp.xemacs.org/pub/xemacs/aux/ and read the 143 of 2002-04-27) from ftp://ftp.xemacs.org/pub/xemacs/aux/ and read the
144 README for details on how to build it. 144 README for details on how to build it.
145 145
146 5. If you want X-Face support, grab the compface distribution from 146 5. If you want X-Face support, grab the compface distribution from
147 ftp://ftp.xemacs.org/pub/xemacs/aux/ and unpack it somewhere. 147 ftp://ftp.xemacs.org/pub/xemacs/aux/ and unpack it somewhere.
148 Copy nt\compface.mak from xemacs sources to the compface directory. 148 Copy nt\compface.mak from xemacs sources to the compface directory.
218 directory): 218 directory):
219 219
220 INSTALL_DIR="x:\your\installation\directory" 220 INSTALL_DIR="x:\your\installation\directory"
221 221
222 (By default, XEmacs will be installed in directories under the directory 222 (By default, XEmacs will be installed in directories under the directory
223 "c:\Program Files\XEmacs\XEmacs-21.2".) 223 "c:\Program Files\XEmacs\XEmacs-21.5".)
224 224
225 3. If you want to build xemacs on the command line, use 225 3. If you want to build xemacs on the command line, use
226 `nmake install -f xemacs.mak', or just `nmake -f xemacs.mak' if you want 226 `nmake install -f xemacs.mak', or just `nmake -f xemacs.mak' if you want
227 to run XEmacs from its build directory. nmake will build temacs, the DOC 227 to run XEmacs from its build directory. nmake will build temacs, the DOC
228 file, update the elc's, dump xemacs and (optionally) install the relevant 228 file, update the elc's, dump xemacs and (optionally) install the relevant
229 files in the directories under the installation directory. 229 files in the directories under the installation directory.
230 230
231 If you chose to install XEmacs, the file that you should run to start 231 If you chose to install XEmacs, the file that you should run to start
232 XEmacs will be installed (by default) as 232 XEmacs will be installed (by default) as
233 "c:\Program Files\XEmacs\XEmacs-21.2\i586-pc-win32\xemacs.exe". 233 "c:\Program Files\XEmacs\XEmacs-21.5\i586-pc-win32\xemacs.exe".
234 234
235 To run from the build directory, run the file "nt\xemacs.exe" off of the 235 To run from the build directory, run the file "src\xemacs.exe" off of the
236 root of the build directory. 236 root of the build directory.
237 237
238 You may want to create a shortcut to the file from your Desktop or 238 You may want to create a shortcut to the file from your Desktop or
239 Start Menu. 239 Start Menu.
240 240
241 4. To build using MS Developer Studio, you can use the workspace file 241 4. To build using MS Developer Studio, you can use the workspace file
242 `nt/xemacs.dsw'. This was prepared for Visual C++ 6.0. If you are using 242 `nt/xemacs.dsw'. This was prepared for Visual C++ 6.0. If you have a
243 Visual C++ 5.0, you can use the workspace file `nt/xemacs-vc50.dsw'. If 243 different version and neither file works, just open up `nt/xemacs.mak'
244 you have a different version and neither file works, just open up 244 from within MS Developer Studio and it will offer to wrap this Makefile
245 `nt/xemacs.mak' from within MS Developer Studio and it will offer to wrap 245 in a workspace file, from which you can build. Assuming you want to run
246 this Makefile in a workspace file, from which you can build. Assuming 246 from the build directory (which you will want to do if you are planning
247 you want to run from the build directory (which you will want to do if 247 on doing any development work on XEmacs), use the following settings in
248 you are planning on doing any development work on XEmacs), use the 248 Project/Settings...:
249 following settings in Project/Settings...:
250 249
251 Under the General tab: 250 Under the General tab:
252 251
253 Build command line: NMAKE /f xemacs.mak 252 Build command line: NMAKE /f xemacs.mak
254 Output file name: ..\src\xemacs.exe 253 Output file name: ..\src\xemacs.exe