From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Retrieving the "include" directory for Emacs Modules
Date: Sun, 08 Dec 2024 13:40:00 +0200 [thread overview]
Message-ID: <86seqyflnz.fsf@gnu.org> (raw)
In-Reply-To: <CAKmY7cXFeP0NFxTY3sHsSR8V5=xf0LGELFOJUA_CMCrecC9GZw@mail.gmail.com> (message from Marco Antoniotti on Sun, 8 Dec 2024 10:59:28 +0100)
> From: Marco Antoniotti <marcoxa@gmail.com>
> Date: Sun, 8 Dec 2024 10:59:28 +0100
>
> Sorry Eli
>
> your solution is not portable and it doesn't work on Mac and Windows (29.2)
>
> On Mac the following works
>
> ELISP> (expand-file-name "../include" data-directory)
> "/Applications/Emacs.app/Contents/Resources/include"
>
> On Windows the include folder is "higher" up.
> "C:\Program Files\Emacs\emacs-29.2\include\"
Sorry, I used too few "..". The correct way is
(expand-file-name "../../../../include" data-directory)
> Given that people (like me) are experimenting with emacs modules, I'd lobby
> for the introduction of a 'include-direcotry' variable.
I honestly don't understand why you need this at all. emacs-module.h
is supposed to be installed in the compilers include tree, where the
compiler looks for header files by default. So you shouldn't even
need to know where the header lives, in order to compile a module.
The module's code should just do
#include <emacs-module.h>
and that's it. Or what am I missing?
next prev parent reply other threads:[~2024-12-08 11:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.77.1733590872.28947.help-gnu-emacs@gnu.org>
2024-12-08 9:59 ` Re: Retrieving the "include" directory for Emacs Modules Marco Antoniotti
2024-12-08 11:40 ` Eli Zaretskii [this message]
2024-12-08 15:47 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-12-08 16:39 ` Eli Zaretskii
2024-12-08 16:48 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-12-08 17:46 ` Eli Zaretskii
2024-12-09 14:11 ` Stefan Monnier via Users list for the GNU Emacs text editor
[not found] <mailman.87.1733936470.18564.help-gnu-emacs@gnu.org>
2024-12-13 11:43 ` Marco Antoniotti
2024-12-13 12:23 ` Eli Zaretskii
[not found] <mailman.624.1733687129.13738.help-gnu-emacs@gnu.org>
2024-12-09 9:58 ` Marco Antoniotti
2024-12-09 14:56 ` Eli Zaretskii
2024-12-09 15:50 ` Rudolf Schlatte
2024-12-09 22:10 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-12-10 3:29 ` Eli Zaretskii
2024-12-11 3:23 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-12-11 13:01 ` Eli Zaretskii
[not found] <mailman.606.1733669386.12711.help-gnu-emacs@gnu.org>
2024-12-08 15:18 ` Marco Antoniotti
2024-12-08 15:29 ` Jean Louis
2024-12-08 15:36 ` Marco Antoniotti
2024-12-08 15:50 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-12-08 16:36 ` Eli Zaretskii
2024-12-08 16:30 ` Eli Zaretskii
2024-12-07 16:27 Marco Antoniotti
2024-12-07 16:43 ` Eli Zaretskii
2024-12-07 19:09 ` Björn Bidar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86seqyflnz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).