From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 48743@debbugs.gnu.org, raman@google.com
Subject: bug#48743: 28.0.50; batch-native-compile should produce .elc files as well
Date: Mon, 31 May 2021 18:27:10 +0000 [thread overview]
Message-ID: <xjf35u2lpxd.fsf@sdf.org> (raw)
In-Reply-To: <83pmx625ov.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 31 May 2021 20:06:56 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Andrea Corallo <akrl@sdf.org>
>> Cc: raman@google.com, 48743@debbugs.gnu.org
>> Date: Mon, 31 May 2021 16:56:51 +0000
>>
>> I think the way to do it is to proceed as we do in the current Emacs
>> build that is; express to make only the .elc targets and produce them
>> using `batch-byte-native-compile-for-bootstrap'.
>>
>> This is like `batch-byte-native-compile' but produces also the .elc
>> files.
>>
>> At this point if packages wants to use this function we should probably
>> rename it as is not anymore in use only for our build process.
>
> Yes, we should rename it,
Agree, what should be a good name for that?
> and we should also provide an easy way of
> controlling where the *.eln files are deposited, since currently that
> function is tightly coupled with the Emacs build process and the
> directory structure of the Emacs source tree.
ATM one could push the new target directory in
`native-comp-eln-load-path' maybe using -eval just before invoking the
batch compilation, if this is not sufficient what should be a better
interface to offer?
TIA
Andrea
next prev parent reply other threads:[~2021-05-31 18:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-30 13:57 bug#48743: 28.0.50; batch-native-compile should produce .elc files as well T.V Raman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-30 14:22 ` Eli Zaretskii
2021-05-30 15:02 ` T.V Raman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-30 15:28 ` Eli Zaretskii
2021-05-31 13:41 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-31 14:46 ` Eli Zaretskii
2021-05-31 16:56 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-31 17:06 ` Eli Zaretskii
2021-05-31 18:27 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-05-31 18:48 ` Eli Zaretskii
2021-05-31 18:59 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-31 19:08 ` Eli Zaretskii
2021-06-01 16:13 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-30 16:59 ` Andrea Corallo
2021-11-30 17:11 ` T.V Raman via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=xjf35u2lpxd.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=48743@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=raman@google.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.