Mercurial > hg > xemacs-beta

comparison nt/README @ 213:78f53ef88e17 r20-4b5

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Import from CVS: tag r20-4b5
author cvs
date Mon, 13 Aug 2007 10:06:47 +0200
parents a2f645c6b9f8
children 1f0dabaa0855
comparison
equal deleted inserted replaced
212:d8688acf4c5b 213:78f53ef88e17
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 Jonathon Harris
5 6
6 Currently XEmacs for NT is in an early stage of development. Only X support 7 Currently XEmacs for Win32 is in an early stage of development.
7 works at the moment, although native GUI/terminal support will be added at a
8 later date. If anyone wants to help with this, please contact us.
9 8
10 The port was made much easier by the groundbreaking work of Geoff Voelker 9 The port was made much easier by the groundbreaking work of Geoff Voelker
11 and others who worked on the GNU Emacs port to NT. Their version is available 10 and others who worked on the GNU Emacs port to NT. Their version is available
12 from http://www.cs.washington.edu/homes/voelker/ntemacs.html 11 from http://www.cs.washington.edu/homes/voelker/ntemacs.html
13 12
14 To get it working you will need: 13 To get it working you will need:
14
15 1. You will need Visual C++ V4.2 or later to compile everything. Personally we
16 have tested V4.2 and V5.0.
17 2. Grab the latest XEmacs beta from ftp.xemacs.org if necessary. All Win32
18 support is in the nt/ subdirectory.
19 3. Edit the xemacs.mak file and ensure variables point to the correct place.
20 Note that Visual C++ assumes a couple of environment variables INCLUDE and
21 LIB to be set which specify the location of the includes and libraries.
22 At this point you can select X or Win32 native support.
23 4. Run make. I simply use nmake -f xemacs.mak. This will build temacs, the
24 DOC file, if startup.elc does not exist it will update the elc's and
25 then it will dump xemacs.
26 5. The build process creates debugging and "Source Browser" information for
27 use with MS DevStudio. To use this create a new "console" project and set
28 the Project/Settings/Debug executable name to the full path of
29 src\xemacs.exe. Remember to close the Source Browser file in DevStudio
30 before rebuilding.
31 6. If you're going to edit sources I recommend that you first get a copy of
32 makedepend and make a list of dependencies in the makefile by doing
33 "nmake -f xemacs.mak depend". I (jhar) have a hacked-up copy of X11R5
34 makedepend which I can distribute if anyone wants it. Is there a real
35 version anywhere which handles '\' as the path delimiter?
36
37 If you want support for X you will need:
15 38
16 1. An X server. MI/X is available on the Internet for free; It is 39 1. An X server. MI/X is available on the Internet for free; It is
17 available from: http://www.microimages.com/www/html/freestuf/mixdlfrm.htm 40 available from: http://www.microimages.com/www/html/freestuf/mixdlfrm.htm
18 2. The MIT X11R6.3 libraries available from: ftp.x.org 41 2. The MIT X11R6.3 libraries available from: ftp.x.org
19 3. You'll need to compile the MIT libraries without multi-thread support. 42 3. You'll need to compile the MIT libraries without multi-thread support.
32 +#ifndef WIN32 55 +#ifndef WIN32
33 typedef CARD8 BOOL; 56 typedef CARD8 BOOL;
34 - 57 -
35 +#endif 58 +#endif
36 59
37 4. You will need Visual C++ V4.2 or later to compile everything. Personally we
38 have tested V4.2 and V5.0.
39 5. Grab the latest XEmacs beta from ftp.xemacs.org if necessary. All nt
40 support is in the nt/ subdirectory.
41 6. Edit the xemacs.mak file and ensure variables point to the correct place.
42 Note that Visual C++ assumes a couple of environment variables INCLUDE and
43 LIB to be set which specify the location of the includes and libraries.
44 7. Copy the files Emacs.ad.h, config.h and paths.h from nt/ to src/.
45 Note, to rebuild Emacs.ad.h a sed script is run. SED for NT is available
46 from the Virtually Unix site: http://www.itribe.net/virtunix
47 This is not required however in normal operation.
48 8. Run make. I simply use nmake -f xemacs.mak.
49 9. Change directory to the src/ directory and run the temacs executable
50 manually:
51 temacs -batch -l loadup.el dump
52 This will produce an xemacs.exe which can be run in conjunction with your
53 X server.
54 10. Ensure your HOME environment variable is set correctly. Also ensure TERM
55 isn't set anywhere.
56 11. When you build, the DOC file will get created correctly. However I don't
57 update the elc's by default. This means the build will fail on the DOC
58 file if they don't exist. Just use the update-elcs rule and then rebuild.
59
60 Known Problems: 60 Known Problems:
61 Please look at the TODO list for the current list of problems and people 61 Please look at the TODO list for the current list of problems and people
62 working on them. 62 working on them.
63 63
64 Any other problems you need clarified, please email us and we will endeavour 64 Any other problems you need clarified, please email us and we will endeavour
65 to provide any assistance we can: 65 to provide any assistance we can:
66 66
67 David Hobley david_hobley@optusvision.com.au -- work email. 67 The XEmacs NT Mailing List: xemacs-nt@xemacs.org
68 davidh@wr.com.au -- home account. 68 Subscribe address: xemacs-nt-request@xemacs.org
69 69
70 Marc Paquette marcpa@cam.org -- home account. 70 David Hobley
71 Marc Paquette
72 August Hill
73 Jonathon Harris
71 74
72 August Hill awhill@inlink.com 75 and others.