Mercurial > hg > xemacs-beta

comparison man/emodules.texi @ 625:33f0f28b945c

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[xemacs-hg @ 2001-07-02 20:45:03 by adrian] [PATCH] Typo fixes for man <8zi7hxlo.fsf@ecf.teradyne.com>
author adrian
date Mon, 02 Jul 2001 20:45:08 +0000
parents 98528da0b7fc
children f72a191f8ecf
comparison
equal deleted inserted replaced
624:59c2a61efa7d 625:33f0f28b945c
651 651
652 The above @file{Makefile} is, in fact, complete, and would compile the 652 The above @file{Makefile} is, in fact, complete, and would compile the
653 sample module, and optionally install it. The @code{--mod-location} 653 sample module, and optionally install it. The @code{--mod-location}
654 argument to @code{ellcc} will produce, on the standard output, the base 654 argument to @code{ellcc} will produce, on the standard output, the base
655 location of the @value{emacs} module directory. Each sub-directory of that 655 location of the @value{emacs} module directory. Each sub-directory of that
656 directory is automatically searched for for modules when they are loaded 656 directory is automatically searched for modules when they are loaded with
657 with @code{load-module}. An alternative location would be 657 @code{load-module}. An alternative location would be
658 @file{/usr/local/lib/xemacs/site-modules}. That path can change 658 @file{/usr/local/lib/xemacs/site-modules}. That path can change depending
659 depending on the options the person who compiled @value{emacs} chose, so you 659 on the options the person who compiled @value{emacs} chose, so you can
660 can always determine the correct site location using the 660 always determine the correct site location using the
661 @code{--mod-site-location} option. This directory is treated the same 661 @code{--mod-site-location} option. This directory is treated the same way
662 way as the main module directory. Each sub-directory within it is 662 as the main module directory. Each sub-directory within it is searched for
663 searched for a given module when the user attempts to load it. The 663 a given module when the user attempts to load it. The valid extensions that
664 valid extensions that the loader attempts to use are @file{.so}, 664 the loader attempts to use are @file{.so}, @file{.ell} and @file{.dll}. You
665 @file{.ell} and @file{.dll}. You can use any of these extensions, 665 can use any of these extensions, although @file{.ell} is the preferred
666 although @file{.ell} is the preferred extension. 666 extension.
667 667
668 @node Link Mode, Other ellcc options, Initialization Mode, Using ellcc 668 @node Link Mode, Other ellcc options, Initialization Mode, Using ellcc
669 @section Link Mode 669 @section Link Mode
670 @cindex linking 670 @cindex linking
671 671