procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Remove some directories that don't really work now.

Browse source
This commit is contained in:
Richard M. Stallman 1998-04-03 01:52:38 +00:00
parent 9658795ce8
commit 5c46262443
1 changed files with 6 additions and 27 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

33
INSTALL
View file

@ -391,33 +391,7 @@ Here is a complete list of the variables you may want to set.
path variables - `bindir' and `libexecdir'.
The above variables serve analogous purposes in the makefiles for all
GNU software; here are some variables specific to Emacs.
`lispdir' indicates where Emacs installs and expects its Lisp library.
Its default value, based on `datadir' (see above), is
`/usr/local/share/emacs/VERSION/lisp' (where `VERSION' is as
described above).
`locallisppath' indicates where Emacs should search for Lisp files
specific to your site. It should be a colon-separated list of
directories; Emacs checks them in order before checking
`lispdir'. Its default value, based on `datadir' (see above), is
`/usr/local/share/emacs/VERSION/site-lisp:/usr/local/share/emacs/site-lisp'.
`lisppath' is the complete list of directories Emacs should search for
its Lisp files; its default value is the concatenation of
`locallisppath' and `lispdir'. It should be a colon-separated
list of directories; Emacs checks them in the order they
appear.
`etcdir' indicates where Emacs should install and expect the rest of
its architecture-independent data, like the tutorial, DOC
file, and yow database. Its default value, based on `datadir'
(which see), is `/usr/local/share/emacs/VERSION/etc'.
`lockdir' indicates the directory where Emacs keeps track of its
locking information. Its default value, based on
`sharedstatedir' (which see), is `/usr/local/com/emacs/lock'.
GNU software; this variable is specific to Emacs.
`archlibdir' indicates where Emacs installs and expects the executable
files and other architecture-dependent data it uses while
@ -433,6 +407,11 @@ settings persist, you can edit them into the `Makefile' in the top
directory, but be aware that running the `configure' program erases
`Makefile' and rebuilds it from `Makefile.in'.
The path for finding Lisp files is specified in src/paths.h,
a file which is generated by running configure. To change the path,
you can edit the definition of PATH_LOADSEARCH in that file
before you run `make'.
The top-level Makefile stores the variable settings it used in the
Makefiles for the subdirectories, so you don't have to specify them
when running make in the subdirectories.