Mercurial > hg > xemacs-beta
comparison nt/README @ 298:70ad99077275 r21-0b47
Import from CVS: tag r21-0b47
author | cvs |
---|---|
date | Mon, 13 Aug 2007 10:39:40 +0200 |
parents | 6330739388db |
children | 33bdb3d4b97f |
comparison
equal
deleted
inserted
replaced
297:deca3c1083ac | 298:70ad99077275 |
---|---|
1 Building and Installing XEmacs on Windows NT | 1 Building and Installing XEmacs on Windows NT |
2 | 2 |
3 David Hobley | 3 David Hobley |
4 Marc Paquette | 4 Marc Paquette |
5 Jonathan Harris | 5 Jonathan Harris |
6 | |
7 Currently XEmacs for Win32 is in an early stage of development. | |
8 | 6 |
9 The port was made much easier by the groundbreaking work of Geoff Voelker | 7 The port was made much easier by the groundbreaking work of Geoff Voelker |
10 and others who worked on the GNU Emacs port to NT. Their version is available | 8 and others who worked on the GNU Emacs port to NT. Their version is available |
11 from http://www.cs.washington.edu/homes/voelker/ntemacs.html | 9 from http://www.cs.washington.edu/homes/voelker/ntemacs.html |
12 | 10 |
15 1. You will need Visual C++ V4.2 or later to compile everything. Personally we | 13 1. You will need Visual C++ V4.2 or later to compile everything. Personally we |
16 have tested V4.2 and V5.0. | 14 have tested V4.2 and V5.0. |
17 Note that Visual C++ assumes a couple of environment variables INCLUDE and | 15 Note that Visual C++ assumes a couple of environment variables INCLUDE and |
18 LIB to be set which specify the location of the includes and libraries. | 16 LIB to be set which specify the location of the includes and libraries. |
19 At this point you can select X or Win32 native support. | 17 At this point you can select X or Win32 native support. |
20 2. Grab the latest XEmacs beta from ftp.xemacs.org if necessary. All Win32 | 18 |
21 support is in the nt/ subdirectory. You'll also need the xemacs-base | 19 2. Grab the latest XEmacs source from ftp.xemacs.org if necessary. All Win32 |
22 package from the binary-packages subdirectory and you'll probably alsi | 20 support is in the nt\ subdirectory. You'll also need the xemacs-base |
21 package from the binary-packages subdirectory and you'll probably also | |
23 want at least the edit-utils, text-utils, cc-mode and prog-utils packages. | 22 want at least the edit-utils, text-utils, cc-mode and prog-utils packages. |
24 Unpack the packages into, say, c:\src\xemacs\packages. | 23 Unpack the packages into, say, "c:\Program Files\XEmacs\packages". |
24 | |
25 | 25 |
26 If you want to build for native GUI: | 26 If you want to build for native GUI: |
27 | 27 |
28 1. If you want XPM and toolbar support grab the latest version of the xpm | 28 1. If you want XPM and toolbar support grab the latest version of the xpm |
29 sources (xpm-3.4k.tar.gz at time of writing) and unpack it. | 29 sources (xpm-3.4k.tar.gz at time of writing) and unpack them somewhere. |
30 Copy nt/xpm.mak from the xemacs distribution to the lib subdirectory of | 30 Copy nt\xpm.mak from the xemacs sources to the lib subdirectory of the |
31 the xpm distribution, cd to that directory and build xpm with | 31 xpm sources, cd to that directory and build xpm with `nmake -f xpm.mak`. |
32 `nmake -f xpm.mak`. | 32 |
33 2. cd to the nt subdirectory of the xemacs distribution and build xemacs: | 33 2. cd to the nt subdirectory of the xemacs distribution and build xemacs: |
34 `nmake -f xemacs.mak HAVE_MSW=1 PATH_PACKAGEPATH="c:/src/xemacs/packages"`, | 34 `nmake install -f xemacs.mak`, but read on before hitting Enter. |
35 replacing "c:/src/xemacs/packages" with the location of your packages. Note | 35 |
36 the double quotes and *forward* slashes in that path. | 36 3. If you're building with XPM support, add this to the nmake command line: |
37 If you're building with XPM support, add this to the nmake command line: | 37 HAVE_XPM=1 XPM_DIR="x:\location\of\your\xpm\source\tree" |
38 `HAVE_XPM=1 XPM_DIR=x:\location\of\your\xpm\source\tree`. | 38 |
39 Nmake will build temacs, the DOC file, update the elc's and dump xemacs. | 39 4. By default, XEmacs will look for packages in |
40 3. The build process creates debugging and "Source Browser" information for | 40 "c:\Program Files\XEmacs\packages". If you want it to look elsewhere, |
41 use with MS DevStudio. To use this create a new "console" project and | 41 add this to the nmake command line: |
42 under Project/Settings set: | 42 PACKAGEPATH="x:\\location\\of\\your\\packages" |
43 Note the doubled-up backslashes in that path. If you want to change the | |
44 package path after you've already built XEmacs, delete the file | |
45 .\obj\emacs.obj and rebuild with the new value of PACKAGEPATH. | |
46 | |
47 5. By default, XEmacs will be installed in directories under the directory | |
48 "c:\Program Files\XEmacs\XEmacs-21.0". If you want to install it | |
49 elsewhere, add this to the nmake command line: | |
50 INSTALL_DIR="x:\your\installation\directory" | |
51 | |
52 6. Now you can press Enter. nmake will build temacs, the DOC file, update the | |
53 elc's, dump xemacs and install the relevant files in the directories under | |
54 the installation directory. Unless you set INSTALL_DIR in step 5 above, the | |
55 file that you should run to start XEmacs will be installed as | |
56 "c:\Program Files\XEmacs\XEmacs-21.0\i386-pc-win32\runemacs.exe". You may | |
57 want to create a shortcut to that file from your Desktop or Start Menu. | |
58 | |
59 7. The build process always creates debugging and "Source Browser" information | |
60 in the source tree for use with MS DevStudio. If you actually want to debug | |
61 XEmacs you should run XEmacs from the source directory instead of from the | |
62 installation directory. You should probably also build a debug version of | |
63 XEmacs; to do this start with a clean source tree and add DEBUG_XEMACS=1 to | |
64 the nmake command line. You probably don't want to install your debug build | |
65 so you should tell nmake to build the 'all' target instead of the 'install' | |
66 target. | |
67 | |
68 To make use of the debugging and "Source Browser" information, create a new | |
69 "console" project in MS DevStudio and, under Project/Settings, set: | |
43 Debug: executable name = full path of src\xemacs.exe | 70 Debug: executable name = full path of src\xemacs.exe |
44 Link: output file name = full path of src\temacs.exe | 71 Link: output file name = full path of src\temacs.exe |
45 Browse Info: browse info file name = full path of src\temacs.bsc | 72 Browse Info: browse info file name = full path of src\temacs.bsc |
46 Remember to close the Source Browser file in DevStudio before rebuilding. | 73 Remember to close the Source Browser file in DevStudio before rebuilding. |
47 | 74 |
75 | |
48 If you want support for X you will need: | 76 If you want support for X you will need: |
49 | 77 |
50 1. An X server. MI/X is available on the Internet for free; It is | 78 1. An X server. MI/X is available on the Internet for free; It is |
51 available from: http://www.microimages.com/www/html/freestuf/mixdlfrm.htm | 79 available from: http://www.microimages.com/www/html/freestuf/mixdlfrm.htm |
80 | |
52 2. The MIT X11R6.3 libraries available from: ftp.x.org | 81 2. The MIT X11R6.3 libraries available from: ftp.x.org |
82 | |
53 3. You'll need to compile the MIT libraries without multi-thread support. | 83 3. You'll need to compile the MIT libraries without multi-thread support. |
54 To do this, there is an example Win32.cf and site.def provided which | 84 To do this, there is an example Win32.cf and site.def provided which |
55 set the relevant flags. You will also need to apply the patch in | 85 set the relevant flags. You will also need to apply the patch in |
56 nt/X11.patch in the xc/lib/X11 directory which will fix the DLL definition | 86 nt/X11.patch in the xc/lib/X11 directory which will fix the DLL definition |
57 file. Once compiled and installed, you will need to apply the following | 87 file. Once compiled and installed, you will need to apply the following |
58 patch to Xmd.h. This is messy and better solutions would be appreciated. | 88 patch to Xmd.h. This is messy and better solutions would be appreciated. |
59 4. Goto 2 under 'native GUI' above and also supply: | 89 |
60 `HAVE_X=1 X11_DIR=x:\root\directory\of\your\X11\installation' | 90 4. Goto 2 under 'native GUI' above and add this to the nmake command line: |
61 to the nmake command line. | 91 HAVE_X=1 X11_DIR=x:\root\directory\of\your\X11\installation |
62 | 92 |
63 --- Xmd.h~ Thu Jun 08 23:20:40 1995 | 93 --- Xmd.h~ Thu Jun 08 23:20:40 1995 |
64 +++ Xmd.h Sun Mar 16 13:09:10 1997 | 94 +++ Xmd.h Sun Mar 16 13:09:10 1997 |
65 @@ -150,8 +150,9 @@ | 95 @@ -150,8 +150,9 @@ |
66 typedef CARD16 BITS16; | 96 typedef CARD16 BITS16; |