Mercurial > hg > xemacs-beta
diff INSTALL @ 388:aabb7f5b1c81 r21-2-9
Import from CVS: tag r21-2-9
author | cvs |
---|---|
date | Mon, 13 Aug 2007 11:09:42 +0200 |
parents | 8626e4521993 |
children | 1f50e6fe4f3f |
line wrap: on
line diff
--- a/INSTALL Mon Aug 13 11:08:51 2007 +0200 +++ b/INSTALL Mon Aug 13 11:09:42 2007 +0200 @@ -444,7 +444,7 @@ By default, XEmacs installs its files in the following directories: `/usr/local/bin' holds the executable programs users normally run - - `xemacs', `etags', `ctags', `b2m', `emacsclient', + `xemacs', `etags', `ctags', `b2m', `emacsclient', `ellcc', `gnuclient', `gnudoit', `gnuattach', and `rcs-checkin'. `/usr/local/lib/xemacs-VERSION/lisp' holds the Emacs Lisp libraries; @@ -483,6 +483,17 @@ kinds of machines share the file system XEmacs is installed on. +`/usr/local/lib/xemacs-VERSION/CONFIGURATION-NAME/modules' holds the Emacs + dynamically loadable modules. These are special programs + typically written in C that can be loaded in much the same + way that Lisp packages are. Not all systems support + dynamic modules, so do not be alarmed if this directory + does not exist or is empty. + + XEmacs searches for modules in this directory, or any + sub-directory of it, and then in + `/usr/local/lib/xemacs/site-modules/*'. + `/usr/local/lib/xemacs-VERSION/info' holds the on-line documentation for XEmacs, known as "info files". @@ -623,6 +634,15 @@ above), is `/usr/local/lib/xemacs-VERSION/CONFIGURATION-NAME' (where VERSION and CONFIGURATION-NAME are as described above). +`moduledir' indicates where XEmacs installs and expects to find + any dynamic modules. Its default value, based on + `archlibdir' (see above) is + `/usr/local/lib/xemacs-VERSION/CONFIGURATION-NAME/modules' + (where VERSION and CONFIGURATION-NAME are as described above). + By their very nature, dynamic loadable modules are architecture- + dependant, and care should be taken not to set this directory + to a system- or architecture-independant directory. + Remember that you must specify any variable values you need each time you run `make' in the top directory. If you run `make' once to build xemacs, test it, and then run `make' again to install the files, you