DataMuseum.dk

top - metrics - download

    Length: 1273 (0x4f9)
    Types: TextFile
    Names: »README«

└─⟦a0efdde77⟧ Bits:30001252 EUUGD11 Tape, 1987 Spring Conference Helsinki
    └─⟦this⟧ »EUUGD11/gnu-31mar87/emacs/src/README« 
└─⟦a05ed705a⟧ Bits:30007078 DKUUG GNU 2/12/89
    └─⟦46d41b2d0⟧ »./emacs-18.55.tar.Z« 
        └─⟦fa971747f⟧ 
            └─⟦this⟧ »dist-18.55/src/README« 

TextFile

This directory contains the source files for the C component of GNU Emacs.
Nothing in this directory is needed for using Emacs once it is built
and installed, if the dumped Emacs (on Unix systems) or the Emacs
executable and map files (on VMS systems) are copied elsewhere.

On Unix, building is controlled by a makefile called `xmakefile'
that is generated with machine-dependent contents from `ymakefile'
using `cpp'.  `Makefile' just invokes `cpp' to produce `xmakefile'
and then runs `make' on `xmakefile'.

See the file VMSBUILD in this directory for instructions on compiling,
linking and building Emacs on VMS.

The files `*.com' and `temacs.opt' are used on VMS only.
The files `vlimit.h', `ioclt.h' and `param.h' are stubs to
allow compilation on VMS with the minimum amount of #ifdefs.

`uaf.h' contains VMS uaf structure definitions.  This is only needed if
you define READ_SYSUAF.  This should only be done for single-user
systems where you are not overly concerned with security, since it
either requires that you install Emacs with SYSPRV or make SYSUAF.DAT
world readable.  Otherwise, Emacs can determine information about the
current user, but no one else.

`pwd.h' contains definitions for VMS to be able to correctly simulate
`getpwdnam' and `getpwduid'.