From: Eli Zaretskii <eliz@gnu.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 45012@debbugs.gnu.org
Subject: bug#45012: 27.1.50; Emacs 27.1 release archive missing emacs-module.h
Date: Sat, 12 Dec 2020 20:37:10 +0200 [thread overview]
Message-ID: <83v9d6euqx.fsf@gnu.org> (raw)
In-Reply-To: <CAArVCkRxaZE2M6MZGkp3woQLoB+Q5KnT-aD=p=Jqkg-wGK5f2Q@mail.gmail.com> (message from Philipp Stephani on Sat, 12 Dec 2020 15:55:46 +0100)
> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Sat, 12 Dec 2020 15:55:46 +0100
> Cc: 45012@debbugs.gnu.org
>
> > > Concretely, I'm using emacs-module.h for my Go bindings to the module
> > > API (https://godoc.org/github.com/phst/emacs). The compilation of the
> > > library naturally requires emacs-module.h, but not Emacs.
> >
> > So you will build the module, but never test it or use it? Is that a
> > reasonably practical use case?
>
> It depends what "you" is. "You" could be a continuous build system
> that's capable of compiling C code, but not of running Emacs. That's
> not far-fetched; compiling C code is far more common than running
> Emacs, and therefore is better supported by build systems.
There's no need to build Emacs, you only need to configure it to get
emacs-module.h generated.
next prev parent reply other threads:[~2020-12-12 18:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 17:52 bug#45012: 27.1.50; Emacs 27.1 release archive missing emacs-module.h Philipp Stephani
2020-12-02 18:10 ` Eli Zaretskii
2020-12-02 18:11 ` Philipp Stephani
2020-12-02 18:33 ` Eli Zaretskii
2020-12-02 18:47 ` Philipp Stephani
2020-12-02 18:53 ` Eli Zaretskii
2020-12-06 17:13 ` Philipp Stephani
2020-12-06 19:12 ` Eli Zaretskii
2020-12-12 14:55 ` Philipp Stephani
2020-12-12 18:37 ` Eli Zaretskii [this message]
2021-01-24 19:01 ` Philipp Stephani
2020-12-12 18:57 ` Eli Zaretskii
2021-01-24 19:02 ` Philipp Stephani
2021-10-11 12:36 ` Stefan Kangas
2021-10-11 15:32 ` Paul Eggert
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83v9d6euqx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=45012@debbugs.gnu.org \
--cc=p.stephani2@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.