From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Andrea Corallo <akrl@sdf.org>, larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: Building a tarball with native-compilation support
Date: Fri, 06 Aug 2021 10:37:10 -0400 [thread overview]
Message-ID: <jwv7dgymyt7.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83wnozhzw1.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 06 Aug 2021 09:05:02 +0300")
> Yes, there are valid reasons to have the *.elc files in the tarball:
>
> . They make the build faster, because the step of using only *.el
> for COMPILE_FIRST is avoided;
> . They are a must if the user wants Emacs without native-compilation
> support, and in that case make the build extremely fast;
> . They provide canonical *.elc files produce on a system where most
> of the *.el files can be meaningfully byte-compiled because the
> related functionality is supported.
Interesting. The second point is the one I remembered (it does make
a very substantial difference, indeed). I'm not sure what the first
point means, really (it seems to be just a subset of the second point).
The third point is new to me: which .el files can't be meaningfully
bytecompiled on all systems?
Stefan
next prev parent reply other threads:[~2021-08-06 14:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 6:25 Building a tarball with native-compilation support Eli Zaretskii
2021-08-05 21:55 ` Andrea Corallo via Emacs development discussions.
2021-08-06 6:05 ` Eli Zaretskii
2021-08-06 14:37 ` Stefan Monnier [this message]
2021-08-06 17:41 ` Eli Zaretskii
2021-08-07 13:28 ` Stefan Monnier
2021-08-07 13:35 ` Eli Zaretskii
2021-08-07 6:23 ` Eli Zaretskii
2021-08-07 6:48 ` Eli Zaretskii
2021-08-07 10:32 ` Eli Zaretskii
2021-08-14 7:44 ` Eli Zaretskii
2021-08-17 10:16 ` Andrea Corallo via Emacs development discussions.
2021-08-17 11:44 ` Eli Zaretskii
2021-08-17 21:49 ` Andrea Corallo via Emacs development discussions.
2021-08-18 13:17 ` Eli Zaretskii
2021-08-18 15:03 ` Andrea Corallo via Emacs development discussions.
2021-08-26 13:42 ` Eli Zaretskii
2021-08-27 13:33 ` Andrea Corallo via Emacs development discussions.
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=jwv7dgymyt7.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).