Mercurial > hg > xemacs-beta

comparison nt/README @ 384:bbff43aa5eb7 r21-2-7

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Import from CVS: tag r21-2-7
author cvs
date Mon, 13 Aug 2007 11:08:24 +0200
parents 6240c7796c7a
children 7d59cb494b73
comparison
equal deleted inserted replaced
383:6a50c6a581a5 384:bbff43aa5eb7
21 can run before building to set up all of these environment variables. 21 can run before building to set up all of these environment variables.
22 22
23 2. Grab the latest XEmacs source from ftp.xemacs.org if necessary. All Win32 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 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 25 package from the binary-packages subdirectory and you'll probably also
26 want at least the edit-utils, text-utils, cc-mode and prog-utils packages. 26 want at least the edit-utils, text-modes, fsf-compat, cc-mode,
27 Unpack the packages into, say, "c:\Program Files\XEmacs\packages". 27 prog-modes and xemacs-devel packages.
28 Unpack the packages into, say, "c:\Program Files\XEmacs\xemacs-packages".
28 29
29 3. At this point you can select X or Win32 native GUI support. 30 3. At this point you can select X or Win32 native GUI support.
30 31
31 If you want to build for native GUI: 32 If you want to build for native GUI:
32 33
69 ZLIB_DIR="x:\location\of\your\zlib\sources" 70 ZLIB_DIR="x:\location\of\your\zlib\sources"
70 71
71 If you want to build with GIF support, add this to the nmake command line: 72 If you want to build with GIF support, add this to the nmake command line:
72 HAVE_GIF=1 73 HAVE_GIF=1
73 74
74 7. By default, XEmacs will look for packages in 75 7. By default, XEmacs will expect to find its packages in the subdirectories
75 "c:\Program Files\XEmacs\packages". If you want it to look elsewhere, 76 "site-packages", "mule-packages" and "xemacs-packages" under the package
76 add this to the nmake command line: 77 prefix directory "c:\Program Files\XEmacs". If you want it to look for
77 PACKAGEPATH="x:\\location\\of\\your\\packages" 78 these subdirectories elsewhere, add this to the nmake command line:
78 Note the doubled-up backslashes in that path. If you want to change the 79 PACKAGE_PREFIX="x:\your\package\directory"
79 package path after you've already built XEmacs, delete the file 80 If you change your mind and want to alter the package prefix directory
80 .\obj\emacs.obj before rebuilding with the new value of PACKAGEPATH. 81 after you've built XEmacs, delete the file .\obj\emacs.obj and rebuild with
82 the new PACKAGE_PREFIX.
81 83
82 8. By default, XEmacs will be installed in directories under the directory 84 8. By default, XEmacs will be installed in directories under the directory
83 "c:\Program Files\XEmacs\XEmacs-21.0". If you want to install it 85 "c:\Program Files\XEmacs\XEmacs-21.0". If you want to install it elsewhere,
84 elsewhere, add this to the nmake command line: 86 add this to the nmake command line:
85 INSTALL_DIR="x:\your\installation\directory" 87 INSTALL_DIR="x:\your\installation\directory"
86 88
87 9. Now you can press Enter. nmake will build temacs, the DOC file, update the 89 9. Now you can press Enter. nmake will build temacs, the DOC file, update the
88 elc's, dump xemacs and install the relevant files in the directories under 90 elc's, dump xemacs and install the relevant files in the directories under
89 the installation directory. Unless you set INSTALL_DIR above, the file that 91 the installation directory. Unless you set INSTALL_DIR above, the file that
90 you should run to start XEmacs will be installed as 92 you should run to start XEmacs will be installed as
91 "c:\Program Files\XEmacs\XEmacs-21.0\i386-pc-win32\runemacs.exe". You may 93 "c:\Program Files\XEmacs\XEmacs-21.0\i386-pc-win32\runemacs.exe". You may
92 want to create a shortcut to that file from your Desktop or Start Menu. 94 want to create a shortcut to that file from your Desktop or Start Menu.
93 95
94 10. The build process always creates debugging and "Source Browser" information 96 10. The build process always creates debugging and "Source Browser" information
95 in the source tree for use with MS DevStudio. If you actually want to debug 97 in the source tree for use with MS DevStudio. If you actually want to debug