Re: Retrieving the "include" directory for Emacs Modules

[Marco Antoniotti <marcoxa@gmail.com>]

Hi

Again, Stefan makes the right observation.  An Emacs "installation is
"proper" depending on the local rules.  Even on Linux when you use snap.

Therefore, the proposal is to add include-directory to the list of the
following ones

lisp-directory
data-directory
exec-directory
source-directory
doc-directory
user-emacs-directory
trash-directory

Adding an em: prefix (or a more traditional em- one) would be a plus.

With that you can then use

EM_INCLUDE_DIR="`emacs --batch --eval '(princ include-directory)'`"

in your build scripts.

I am not subscribed to the help-gnu-devel mailing list.  Please pass it on
there.

All the best

Marco



> Those under /usr/lib are looked in by the relevant compilers (they are
> include directories private to those compilers, hard-coded into them
> when they are built).  Those under /usr/share are private to the
> relevant packages, and are either examples or test suites (thus AFAIU
> unrelated to the issue at hand here).  Those under /usr/src are what I
> mentioned: private headers needed to build a package.

Indeed, they each have their own reason to exist.  And this is in Debian,
i.e. a distribution which is very careful to install things in the one
central place where they belong.
Other relevant cases will look very different:
Emacs.app, AppImages, Snap packages, etc...


        Stefan

-- 
Marco Antoniotti
Somewhere over the Rainbow