unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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, "T.V Raman" <raman@google.com>
Subject: bug#48743: 28.0.50; batch-native-compile should produce .elc files as well
Date: Mon, 31 May 2021 13:41:28 +0000	[thread overview]
Message-ID: <xjfbl8rkol3.fsf@sdf.org> (raw)
In-Reply-To: <831r9o47y9.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 30 May 2021 17:22:54 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Sun, 30 May 2021 06:57:54 -0700 (PDT)
>> From:  "T.V Raman" via "Bug reports for GNU Emacs,
>>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>> 
>> 
>> 1. Large packages that span multiple files can have build-order
>>    dependencies e.g. files containing macros need to be built and
>>    loaded when compiling the rest of the package.
>
> I became stuck right here at the 1st item: what do you mean by "files
> containing macros need to be built and loaded"?  For the "loaded"
> part, we use 'require' and 'eval-when-compile', and these work with
> *.el files exactly as they do with *.elc or *.eln.  So what exactly is
> the problem you are alluding to here, and in particularly what happens
> when you "build" these files with macros that requires them to be
> built?
>
> Without understanding this, I cannot follow the rest of your
> description.
>
> (Andrea, I hope you are following this.)

Hi Eli,

yes I'm following this thread, trying ATM to make my mind on what's the
real issue.

  Andrea





  parent reply	other threads:[~2021-05-31 13:41 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 [this message]
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
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

  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=xjfbl8rkol3.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 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).