Re: Should Emacs define site-lisp load-path for Dynamically-Loaded Modules?

["Björn Bidar" <bjorn.bidar@thaodan.de>]

"Alfred M. Szmidt" <ams@gnu.org> writes:

>    Recently I have began on packaging Emacs packages for OpenSuSE Linux,
>    many of whom use dynamic modules.
>
>    I noticed that almost all packages that use dynamic modules compile
>    the module after installation and store it in the package directory.
>
>    Emacs define site-lisp for locally installed libraries however the
>    directory is usually contained inside <datadir>.
>
> Might be a good idea to double check
> https://www.gnu.org/prep/standards/html_node/Directory-Variables.html .
>
> The site-lisp directory can be read-only, and should only contain
> architecture-_independent_ files since it sirts under datarootdir.

The link you refer to doesn't contain any reference to site-lisp besides *lispdir*.
I thought it was clear that I don't mean to define site-lisp but define
a second site-lisp as you say your self.

>
>    That makes me ask the questions should there be a second site-lisp for
>    dynamic modules in <libdir> by default?
>
> Are they architecture-dependent?  Are they libraries or other object
> files? Seems so, off the cuff sounds reasonable.

Did you read the manual? Yes dynamic modules are per definition
architecture-dependent after they have been compiled as they use
compiled languages such as C or C++.