comparison nt/README @ 169:15872534500d r20-3b11

Import from CVS: tag r20-3b11
author cvs
date Mon, 13 Aug 2007 09:46:53 +0200
parents 43dd3413c7c7
children a2f645c6b9f8
comparison
equal deleted inserted replaced
168:9851d5c6556e 169:15872534500d
1 Building and Installing XEmacs 1 Building and Installing XEmacs on Windows NT
2 on Windows NT
3 2
4 David Hobley <david_hobley@optusvision.com.au> 3 David Hobley
5 <davidh@wr.com.au> 4 Marc Paquette
6 Marc Paquette <marcpa@cam.org>
7 5
8 You need a compiler package to build and install XEmacs on NT or Win95. 6 Currently XEmacs for NT is in an early stage of development. Only X support
9 Microsoft Visual C++ 4.2 has been successfuly used to build it on NT: we 7 works at the moment, although native GUI/terminal support will be added at a
10 recommend this specific version (VC++ 4.1 has trouble with some macro 8 later date. If anyone wants to help with this, please contact us.
11 definitions in XEmacs sources).
12 9
13 This is an extremely early release. Any help we can provide we will do 10 The port was made much easier by the groundbreaking work of Geoff Voelker
14 so. Note however that, as of XEmacs 20.3 beta4, only X is supported 11 and others who worked on the GNU Emacs port to NT. Their version is available
15 and some things might not work well at first. 12 from http://www.cs.washington.edu/homes/voelker/ntemacs.html
16 13
17 Two methods to try it: jumpstart with pre-compiled X libraries (NT4 14 To get it working you will need:
18 for Intel) or the long route with X11R6.3 re-compiled from scratch.
19 The jumpstart method is not in place yet, but the files will probably
20 appear somewhere at ftp.xemacs.org. Here are some instructions for
21 recompiling X:
22 15
23 1. Get X11R6.3 (Note: you need *a lots* of free space on your drive). 16 1. An X server. MI/X is available on the Internet for free; It is
24 Modify its Win32.cf and site.def configuration files 17 available from: http://www.microimages.com/www/html/freestuf/mixdlfrm.htm
25 to use the single-threaded, statically linked C run-time library 18 2. The MIT X11R6.3 libraries available from: ftp.x.org
26 (libc.lib instead of msvcrt.dll). Samples Win32.cf and site.def are 19 3. You'll need to compile the MIT libraries without multi-thread support.
27 provided in the XEmacs nt/ directory. 20 To do this, there is an example Win32.cf and site.def provided which
28 2. Build X11R6.3 and install it. 21 set the relevant flags. You will also need to apply the patch in
29 3. Apply the following patch to include/X11/Xmd.h in the installed 22 nt/X11.patch in the xc/lib/X11 directory which will fix the DLL definition
30 directory. Note: this could conceivably be better done before 23 file. Once compiled and installed, you will need to apply the following
31 compiling X, but this is the order I (marcpa) used. 24 patch to Xmd.h. This is messy and better solutions would be appreciated.
32 25
33 --- Xmd.h~ Thu Jun 08 23:20:40 1995 26 --- Xmd.h~ Thu Jun 08 23:20:40 1995
34 +++ Xmd.h Sun Mar 16 13:09:10 1997 27 +++ Xmd.h Sun Mar 16 13:09:10 1997
35 @@ -150,8 +150,9 @@ 28 @@ -150,8 +150,9 @@
36 typedef CARD16 BITS16; 29 typedef CARD16 BITS16;
39 +#ifndef WIN32 32 +#ifndef WIN32
40 typedef CARD8 BOOL; 33 typedef CARD8 BOOL;
41 - 34 -
42 +#endif 35 +#endif
43 36
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.
44 54
45 4. Edit the xemacs.mak Makefile and ensure variables point to the 55 Known Problems:
46 correct place. 56 Please look at the TODO list for the current list of problems and people
47 5. copy the files ad2c.sed, config.h, paths.h and xemacs.mak from nt/ 57 working on them.
48 into src/.
49 6. Run nmake using xemacs.mak (nmake -f xemacs.mak) while in src/.
50 7. Manually run the resulting temacs executable to create xemacs:
51 temacs.exe -batch -l loadup.el dump
52 8. You should be able to use MSDEV to run and debug temacs.exe: open a
53 workspace by specifying "Executable files", select "temacs.exe", set
54 the debug "Program arguments" settings (Build->Settings->Debug) to "-batch -l
55 loadup.el run-temacs" and run it. You should be able to open any
56 source file and set a breakpoint in it.
57 58
58 Problems: 59 Any other problems you need clarified, please email us and we will endeavour
59 - Haven't got rid of some symbol problems which may be causing problems. 60 to provide any assistance we can:
60 - Still seems to use fork, which fails without /force option on link. I am
61 trying to work out where it should be removed.
62 - To make it work on X, usage of XtAppAddInput had to be commented out.
63 This is expected to break some parts of XEmacs, so beware.
64 61
65 Any problems/questions, mail us: 62 David Hobley david_hobley@optusvision.com.au -- work email.
63 davidh@wr.com.au -- home account.
66 64
67 David Hobley 65 Marc Paquette marcpa@cam.org -- home account.
68 david_hobley@optusvision.com.au -- work email.
69 davidh@wr.com.au -- home account.
70 66
71 Marc Paquette 67 August Hill awhill@inlink.com
72 marcpa@cam.org -- home account.