unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Retrieving the "include" directory for Emacs Modules
Date: Wed, 11 Dec 2024 15:01:44 +0200	[thread overview]
Message-ID: <86bjxi4blz.fsf@gnu.org> (raw)
In-Reply-To: <jwvcyhy29de.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier via Users list for the GNU Emacs text editor on Tue, 10 Dec 2024 22:23:05 -0500)

> Date: Tue, 10 Dec 2024 22:23:05 -0500
> From:  Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
> 
> >> > As I tried to explain, if emacs-module.h is not installed in its
> >> > intended place, we cannot know where it is installed.
> >> The patch below would make sure that `emacs-module.h` is always
> >> available at `$(data-directory)/include/emacs-module.h`.
> > Sorry, this is wrong. [...] this is a change that will break previous
> > (and correct) behavior.
> 
> I don't see how it would break anything: the .h file is still *also*
> copied to the $(includedir) for those people who want to compile their
> module outside of Emacs.

That makes this easier to accept, but there are still issues.

> > No compiler will look in that directory without a suitable -I option,
> 
> That's OK: the sole purpose of the change is to let ELPA packages call
> `gcc` with such a `-I`!

Let's discuss this in a proper place, not here, okay?  In particular,
I'd like to hear more opinions and data points, from people who don't
necessarily read this forum.



  reply	other threads:[~2024-12-11 13:01 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
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 [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=86bjxi4blz.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).