From: Eli Zaretskii <eliz@gnu.org>
To: "T.V Raman" <raman@google.com>, Andrea Corallo <akrl@sdf.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Native Compilation And External Packages
Date: Sat, 29 May 2021 21:47:22 +0300 [thread overview]
Message-ID: <8335u55qdh.fsf@gnu.org> (raw)
In-Reply-To: <p91pmx94cag.fsf@google.com> (raman@google.com)
> From: "T.V Raman" <raman@google.com>
> Cc: emacs-devel@gnu.org
> Date: Sat, 29 May 2021 11:36:55 -0700
>
>
> I'm attaching the output of a native build below that demonstrates:
>
> 1. There are no warnings during build
> 2. Contrary to what I infered from Eli's message, doing a native
> build does not appear to generate any .elc files.
I'm sorry, it is hard for me to understand what you are trying to
accomplish. You post a lot of information, but it isn't clear which
part(s) of that are relevant. So maybe I misunderstood and confused
you.
Anyway, if you want to actually _produce_ the *.elc files, invoke
batch-byte-compile as well. You could also try
batch-byte-native-compile-for-bootstrap, then the *.eln files end up
not in eln-cache.
Andrea, what are your recommendations for a project's Makefiles for
building *.eln files?
prev parent reply other threads:[~2021-05-29 18:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-29 16:28 Native Compilation And External Packages T.V Raman
2021-05-29 16:38 ` Eli Zaretskii
2021-05-29 17:14 ` T.V Raman
2021-05-29 17:36 ` Eli Zaretskii
2021-05-29 18:52 ` Stefan Monnier
2021-05-30 1:58 ` T.V Raman
2021-05-29 18:56 ` Stefan Monnier
2021-05-30 2:06 ` T.V Raman
2021-05-30 3:05 ` T.V Raman
2021-05-29 17:00 ` Stefan Monnier
2021-05-29 17:18 ` T.V Raman
2021-05-29 18:36 ` T.V Raman
2021-05-29 18:47 ` Eli Zaretskii [this message]
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=8335u55qdh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=akrl@sdf.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--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 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).