From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Stefan Monnier via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: Retrieving the "include" directory for Emacs Modules
Date: Mon, 23 Dec 2024 03:00:53 +0200 [thread overview]
Message-ID: <18869.4711936236$1734915715@news.gmane.org> (raw)
In-Reply-To: <jwvmsgqjrng.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 20 Dec 2024 10:41:08 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> That's OK: the sole purpose of the change is to let ELPA packages call
>>> `gcc` with such a `-I`!
>> Which is wrong for Unix-like systems except on macOS.
>
> In which sense would it be wrong?
> I can see an argument that such a `-I` would tend to be redundant on
> systems where Emacs was "installed properly", but even on those systems
> I fail to see what would be "wrong" about it.
Headers don't go the Emacs data directory but in the include directory,
usually /usr/include or /usr/local/include.
>> It's debatable if packages should compile their native modules
>> themselves
>
> IME it's what most users expect when they install (via `package.el`)
> packages that come with a module, and it's also what most of the
> developers of those packages want to offer to their users.
> I have no intention to impose such an approach as the only supported way
> to install a module, but I don't see what's debatable about providing
> good support for packages to be able to compile their own modules.
I don't think about imposing anything but keeping in mind that modules
built arbitrary native code which can bring it's own issues especially
when external dependencies come into play.
Most packages which use native modules have to be adjusted to not built
the native module for themselves or from where to load the
native-module, some don't from load-path or no load-path for native
modules (they are not installed to datadir).
I wonder if there's something that could be learned from XEmacs approach
of emodules which were very similar. Especially the idea of ellcc[1] sounds
very good in this context.
--
[1] http://xemacs.org/Documentation/21.5/html/emodules_2.html#Using-ellcc
next prev parent reply other threads:[~2024-12-23 1:00 UTC|newest]
Thread overview: 29+ 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
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
2024-12-19 23:50 ` Björn Bidar
[not found] ` <87ttazmdvc.fsf@>
2024-12-20 7:09 ` Eli Zaretskii
2024-12-20 9:01 ` Basile Starynkevitch
2024-12-23 0:47 ` Björn Bidar
2024-12-20 15:41 ` Stefan Monnier
2024-12-23 1:00 ` Björn Bidar [this message]
2024-12-22 22:17 ` Arsen Arsenović
[not found] <mailman.81.1734714033.1948.help-gnu-emacs@gnu.org>
2024-12-21 20:04 ` Marco Antoniotti
[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='18869.4711936236$1734915715@news.gmane.org' \
--to=bjorn.bidar@thaodan.de \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).