|
|
1.1 ! root 1: How to compile, link and build GNU Emacs under VMS. ! 2: ! 3: ! 4: A runnable Emacs on VMS consists of two files, an exe file and ! 5: a map file. (It also refers to a DOC file in the [-.etc] sibling directory. ! 6: These files are made automatically and kept straight by Emacs version number.) ! 7: ! 8: For an Emacs being built and tested, these files are `temacs.exe' and ! 9: `temacs.dump' in this directory. ! 10: ! 11: For an installed Emacs, these files are `emacs.exe' and ! 12: `emacs.dump' in the directory above this one. These names are known ! 13: only in the file `emacs.com', also in that directory. ! 14: ! 15: Before you can run Emacs or compile or build any part of Emacs, ! 16: you must run `emacs.com'. It sets up logical names that are used ! 17: by everything else. ! 18: ! 19: Before compiling anything on VMS, you must copy `config.h-dist' to `config.h' ! 20: and make sure it is set up for VMS (using files `m-vax.h' and `s-vms.h'. ! 21: Also copy `vmspaths.h' to `paths.h'. `paths.h-dist' is for Unix only. ! 22: (On VMS versions before 4.4, the file names have `_' in place of `-'.) ! 23: ! 24: Execute `compile.com' to recompile all files that need recompilation. ! 25: Alternatively, execute `precomp.com' to define a command `ccom' that ! 26: can be used to recompile individual files. `ccom' works by executing ! 27: `ccom.com'. ! 28: ! 29: If you compile with optimization, note that in compiler version ! 30: 3.0 there is a bug affecting inline functions. So you must specify ! 31: /OPTIMIZE=NOINLINE when compiling `dispnew.c'. ! 32: ! 33: Compilation will give you lots of warnings about symbols longer than 30 ! 34: characters. You must just ignore them. Alternatively, you can ! 35: compile the C program `vms-pp.c' and run all the .c and .h files ! 36: through that program and then compile the results. ! 37: (On VMS versions before 4.4, the program is called `vms_pp.c'.) ! 38: ! 39: **If you use `vms-pp.c', please save the originals .c and .h files ! 40: and distribute them rather than the transformed files ! 41: if you wish to distribute copies of Emacs. Help minimize confusion!** ! 42: ! 43: Execute `link.com' to link the compiled files into `temacs.exe'. ! 44: This process uses `temacs.opt'. You will get lots of linker warnings ! 45: telling you that there were compiler warnings. Just ignore them. ! 46: ! 47: Execute `[-.etc]complink.com' to compile and link the files ! 48: in the [emacs.etc] directory. This must be done before ! 49: `[-.etc]makedoc.com' can be run. ! 50: ! 51: Execute `[-.etc]makedoc.com' to create or update the file `[-.etc]doc.'. ! 52: This must be done if that file does not yet exist or if any of ! 53: the Emacs C sources or preloaded Lisp sources has changed. ! 54: It must be done before `build.com' is run in order to take effect. ! 55: ! 56: Execute `build.com' to run `temacs.exe', initialize it and preload ! 57: some Lisp code, and dump the map file `temacs.dump' containing a copy ! 58: of all the impure storage after initialization. ! 59: ! 60: Execute `testemacs.com' to define the `runtemacs' command ! 61: to run `temacs.exe' with its map file `temacs.dump'. ! 62: ! 63: To install an Emacs, rename `temacs.dump' as `[-]emacs.dump' and ! 64: rename `temacs.exe' as `[-]emacs.exe'.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.