From: Eli Zaretskii <eliz@gnu.org>
To: Ken Brown <kbrown@cornell.edu>
Cc: emacs-devel@gnu.org
Subject: Re: native-compilation: how to force the .eln files to be built
Date: Tue, 13 Apr 2021 05:30:31 +0300 [thread overview]
Message-ID: <83zgy229x4.fsf@gnu.org> (raw)
In-Reply-To: <4d692d01-a87b-8adb-715a-24be9a05a27f@cornell.edu> (message from Ken Brown on Mon, 12 Apr 2021 18:07:53 -0400)
> From: Ken Brown <kbrown@cornell.edu>
> Date: Mon, 12 Apr 2021 18:07:53 -0400
>
> Is there an easy way to force the .eln files to be built if the .elc files are
> up to date?
No, at least not for some value of "easy". (How would you do that for
.elc files?)
> I often have more than one build directory for a given source directory. The
> different build directories might correspond to different configure options or
> different architectures, for example. After building in one directory, the .elc
> files in the source directory are all up to date. If I now build in a different
> directory, the .eln files might be out of date or even non-existent, but they
> don't get (re)built.
I wrote a script that compiles all the preloaded *.el files, and I run
that script in such situations.
next prev parent reply other threads:[~2021-04-13 2:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 22:07 native-compilation: how to force the .eln files to be built Ken Brown
2021-04-13 2:30 ` Eli Zaretskii [this message]
2021-04-13 12:42 ` Ken Brown
2021-04-13 13:58 ` Eli Zaretskii
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=83zgy229x4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kbrown@cornell.edu \
/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).