comparison nt/README @ 276:6330739388db r21-0b36

Import from CVS: tag r21-0b36
author cvs
date Mon, 13 Aug 2007 10:30:37 +0200
parents 1f0dabaa0855
children 70ad99077275
comparison
equal deleted inserted replaced
275:a68ae4439f57 276:6330739388db
12 12
13 To get it working you will need: 13 To get it working you will need:
14 14
15 1. You will need Visual C++ V4.2 or later to compile everything. Personally we 15 1. You will need Visual C++ V4.2 or later to compile everything. Personally we
16 have tested V4.2 and V5.0. 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 17 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. 18 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. 19 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 20 2. Grab the latest XEmacs beta from ftp.xemacs.org if necessary. All Win32
24 DOC file, if startup.elc does not exist it will update the elc's and 21 support is in the nt/ subdirectory. You'll also need the xemacs-base
25 then it will dump xemacs. 22 package from the binary-packages subdirectory and you'll probably alsi
26 5. The build process creates debugging and "Source Browser" information for 23 want at least the edit-utils, text-utils, cc-mode and prog-utils packages.
27 use with MS DevStudio. To use this create a new "console" project and set 24 Unpack the packages into, say, c:\src\xemacs\packages.
28 the Project/Settings/Debug executable name to the full path of 25
29 src\xemacs.exe. Remember to close the Source Browser file in DevStudio 26 If you want to build for native GUI:
30 before rebuilding. 27
31 6. If you're going to edit sources I recommend that you first get a copy of 28 1. If you want XPM and toolbar support grab the latest version of the xpm
32 makedepend and make a list of dependencies in the makefile by doing 29 sources (xpm-3.4k.tar.gz at time of writing) and unpack it.
33 "nmake -f xemacs.mak depend". I (jhar) have a hacked-up copy of X11R5 30 Copy nt/xpm.mak from the xemacs distribution to the lib subdirectory of
34 makedepend which I can distribute if anyone wants it. Is there a real 31 the xpm distribution, cd to that directory and build xpm with
35 version anywhere which handles '\' as the path delimiter? 32 `nmake -f xpm.mak`.
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"`,
35 replacing "c:/src/xemacs/packages" with the location of your packages. Note
36 the double quotes and *forward* slashes in that path.
37 If you're building with XPM support, add this to the nmake command line:
38 `HAVE_XPM=1 XPM_DIR=x:\location\of\your\xpm\source\tree`.
39 Nmake will build temacs, the DOC file, update the elc's and dump xemacs.
40 3. The build process creates debugging and "Source Browser" information for
41 use with MS DevStudio. To use this create a new "console" project and
42 under Project/Settings set:
43 Debug: executable name = full path of src\xemacs.exe
44 Link: output file name = full path of src\temacs.exe
45 Browse Info: browse info file name = full path of src\temacs.bsc
46 Remember to close the Source Browser file in DevStudio before rebuilding.
36 47
37 If you want support for X you will need: 48 If you want support for X you will need:
38 49
39 1. An X server. MI/X is available on the Internet for free; It is 50 1. An X server. MI/X is available on the Internet for free; It is
40 available from: http://www.microimages.com/www/html/freestuf/mixdlfrm.htm 51 available from: http://www.microimages.com/www/html/freestuf/mixdlfrm.htm
43 To do this, there is an example Win32.cf and site.def provided which 54 To do this, there is an example Win32.cf and site.def provided which
44 set the relevant flags. You will also need to apply the patch in 55 set the relevant flags. You will also need to apply the patch in
45 nt/X11.patch in the xc/lib/X11 directory which will fix the DLL definition 56 nt/X11.patch in the xc/lib/X11 directory which will fix the DLL definition
46 file. Once compiled and installed, you will need to apply the following 57 file. Once compiled and installed, you will need to apply the following
47 patch to Xmd.h. This is messy and better solutions would be appreciated. 58 patch to Xmd.h. This is messy and better solutions would be appreciated.
59 4. Goto 2 under 'native GUI' above and also supply:
60 `HAVE_X=1 X11_DIR=x:\root\directory\of\your\X11\installation'
61 to the nmake command line.
48 62
49 --- Xmd.h~ Thu Jun 08 23:20:40 1995 63 --- Xmd.h~ Thu Jun 08 23:20:40 1995
50 +++ Xmd.h Sun Mar 16 13:09:10 1997 64 +++ Xmd.h Sun Mar 16 13:09:10 1997
51 @@ -150,8 +150,9 @@ 65 @@ -150,8 +150,9 @@
52 typedef CARD16 BITS16; 66 typedef CARD16 BITS16;