Mercurial > hg > xemacs-beta

comparison nt/README @ 314:341dac730539 r21-0b55

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Import from CVS: tag r21-0b55
author cvs
date Mon, 13 Aug 2007 10:44:22 +0200
parents 33bdb3d4b97f
children afd57c14dfc8
comparison
equal deleted inserted replaced
313:2905de29931f 314:341dac730539
28 28
29 3. At this point you can select X or Win32 native GUI support. 29 3. At this point you can select X or Win32 native GUI support.
30 30
31 If you want to build for native GUI: 31 If you want to build for native GUI:
32 32
33 1. If you want XPM and toolbar support grab the latest version of the xpm 33 1. If you want XPM image and toolbar support grab the latest version of the
34 sources (xpm-3.4k.tar.gz at time of writing) and unpack them somewhere. 34 xpm sources (xpm-3.4k.tar.gz at time of writing) and unpack them somewhere.
35 Copy nt\xpm.mak from the xemacs sources to the lib subdirectory of the 35 Copy nt\xpm.mak from the xemacs sources to the lib subdirectory of the
36 xpm sources, cd to that directory and build xpm with `nmake -f xpm.mak`. 36 xpm sources, cd to that directory and build xpm with 'nmake -f xpm.mak'.
37 37
38 2. cd to the nt subdirectory of the xemacs distribution and build xemacs: 38 2. You probably also want PNG image support. Grab the latest versions of zlib
39 and libpng (zlib-1.1.3 and libpng-1.0.2 at time of writing), unpack them
40 somewhere and read the respective READMEs for details on how to build them.
41 The following build procedure works for zlib-1.1.3 and libpng-1.0.2:
42
43 cd to the zlib directory, type 'copy msdos\makefile.w32 Makefile' and
44 then type 'nmake'.
45
46 cd to the libpng directory, rename or move the zlib directory to ..\zlib
47 and type 'nmake -f scripts\makefile.w32'.
48
49 3. If you want JPEG and/or TIFF support grab the latest versions of jpegsrc
50 and/or libtiff and read the respective READMEs for details on how to build
51 them.
52
53 4. cd to the nt subdirectory of the xemacs distribution and build xemacs:
39 `nmake install -f xemacs.mak`, but read on before hitting Enter. 54 `nmake install -f xemacs.mak`, but read on before hitting Enter.
40 55
41 3. If you're building with XPM support, add this to the nmake command line: 56 5. If you're building with XPM support, add this to the nmake command line:
42 HAVE_XPM=1 XPM_DIR="x:\location\of\your\xpm\source\tree" 57 HAVE_XPM=1 XPM_DIR="x:\location\of\your\xpm\sources"
58 and similarly for JPEG and TIFF support.
43 59
44 4. By default, XEmacs will look for packages in 60 If you're building with PNG support, add this to the nmake command line:
61 HAVE_PNG=1 PNG_DIR="x:\location\of\your\png\sources"
62 ZLIB_DIR="x:\location\of\your\zlib\sources"
63
64 If you want to build with GIF support, add this to the nmake command line:
65 HAVE_GIF=1
66
67 6. By default, XEmacs will look for packages in
45 "c:\Program Files\XEmacs\packages". If you want it to look elsewhere, 68 "c:\Program Files\XEmacs\packages". If you want it to look elsewhere,
46 add this to the nmake command line: 69 add this to the nmake command line:
47 PACKAGEPATH="x:\\location\\of\\your\\packages" 70 PACKAGEPATH="x:\\location\\of\\your\\packages"
48 Note the doubled-up backslashes in that path. If you want to change the 71 Note the doubled-up backslashes in that path. If you want to change the
49 package path after you've already built XEmacs, delete the file 72 package path after you've already built XEmacs, delete the file
50 .\obj\emacs.obj and rebuild with the new value of PACKAGEPATH. 73 .\obj\emacs.obj before rebuilding with the new value of PACKAGEPATH.
51 74
52 5. By default, XEmacs will be installed in directories under the directory 75 7. By default, XEmacs will be installed in directories under the directory
53 "c:\Program Files\XEmacs\XEmacs-21.0". If you want to install it 76 "c:\Program Files\XEmacs\XEmacs-21.0". If you want to install it
54 elsewhere, add this to the nmake command line: 77 elsewhere, add this to the nmake command line:
55 INSTALL_DIR="x:\your\installation\directory" 78 INSTALL_DIR="x:\your\installation\directory"
56 79
57 6. Now you can press Enter. nmake will build temacs, the DOC file, update the 80 8. Now you can press Enter. nmake will build temacs, the DOC file, update the
58 elc's, dump xemacs and install the relevant files in the directories under 81 elc's, dump xemacs and install the relevant files in the directories under
59 the installation directory. Unless you set INSTALL_DIR in step 5 above, the 82 the installation directory. Unless you set INSTALL_DIR above, the file that
60 file that you should run to start XEmacs will be installed as 83 you should run to start XEmacs will be installed as
61 "c:\Program Files\XEmacs\XEmacs-21.0\i386-pc-win32\runemacs.exe". You may 84 "c:\Program Files\XEmacs\XEmacs-21.0\i386-pc-win32\runemacs.exe". You may
62 want to create a shortcut to that file from your Desktop or Start Menu. 85 want to create a shortcut to that file from your Desktop or Start Menu.
63 86
64 7. The build process always creates debugging and "Source Browser" information 87 9. The build process always creates debugging and "Source Browser" information
65 in the source tree for use with MS DevStudio. If you actually want to debug 88 in the source tree for use with MS DevStudio. If you actually want to debug
66 XEmacs you should run XEmacs from the source directory instead of from the 89 XEmacs you should run XEmacs from the source directory instead of from the
67 installation directory. You should probably also build a debug version of 90 installation directory. You should probably also build a debug version of
68 XEmacs; to do this start with a clean source tree and add DEBUG_XEMACS=1 to 91 XEmacs; to do this start with a clean source tree and add DEBUG_XEMACS=1 to
69 the nmake command line. You probably don't want to install your debug build 92 the nmake command line. You probably don't want to install your debug build