unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>
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: Fri, 20 Dec 2024 10:41:08 -0500	[thread overview]
Message-ID: <jwvmsgqjrng.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87ttazmdvc.fsf@> ("Björn Bidar"'s message of "Fri, 20 Dec 2024 01:50:31 +0200")

>> 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.

> 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.


        Stefan




  parent reply	other threads:[~2024-12-20 15:41 UTC|newest]

Thread overview: 25+ 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-20 15:41             ` Stefan Monnier [this message]
     [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=jwvmsgqjrng.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=bjorn.bidar@thaodan.de \
    --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).