From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Retrieving the "include" directory for Emacs Modules
Date: Mon, 09 Dec 2024 16:56:24 +0200 [thread overview]
Message-ID: <86ttbcdhwn.fsf@gnu.org> (raw)
In-Reply-To: <CAKmY7cXOjACgb+p4A1rE=nnKm4=GFq=Oy_Puf5xQfBxG0NfNdw@mail.gmail.com> (message from Marco Antoniotti on Mon, 9 Dec 2024 10:58:57 +0100)
> From: Marco Antoniotti <marcoxa@gmail.com>
> Date: Mon, 9 Dec 2024 10:58:57 +0100
>
> On my Mac, If I install emacs as a "formula" (i.e., not a s an app) things
> seem installed as they should be. OTOH the brew "cask" (which installs a
> .app in the Application directory) seems to create something that Apple
> likes, but that STILL may be told to have a pointer to the include
> directory as it does to the data-directory.
>
> This is obviously something that the brew folks should deal with, but the
> notion of having a variable that tracks the include directory still has
> merit. At least as an extra guideline to people like the brew maintainers.
As I tried to explain, if emacs-module.h is not installed in its
intended place, we cannot know where it is installed. We only know
that from the default installation locations we have in our Makefiles,
but if some distros modify that, we cannot know.
And I still contend that the correct installation should put this file
where all the other header files are, and then the compiler will
always find it. Users who don't want to fight the uphill battle
against brew could simply copy the file to the compiler's include
directory, and be done.
next prev parent reply other threads:[~2024-12-09 14:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.624.1733687129.13738.help-gnu-emacs@gnu.org>
2024-12-09 9:58 ` Retrieving the "include" directory for Emacs Modules Marco Antoniotti
2024-12-09 14:56 ` Eli Zaretskii [this message]
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.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.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
[not found] <mailman.77.1733590872.28947.help-gnu-emacs@gnu.org>
2024-12-08 9:59 ` Marco Antoniotti
2024-12-08 11:40 ` Eli Zaretskii
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
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=86ttbcdhwn.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).