all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "T.V Raman" <raman@google.com>, Andrea Corallo <akrl@sdf.org>
Cc: 48743@debbugs.gnu.org
Subject: bug#48743: 28.0.50; batch-native-compile should produce .elc files as well
Date: Sun, 30 May 2021 17:22:54 +0300	[thread overview]
Message-ID: <831r9o47y9.fsf@gnu.org> (raw)
In-Reply-To: <20210530135754.DE34AC2054B@raman-glaptop.localdomain> (bug-gnu-emacs@gnu.org)

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





  reply	other threads:[~2021-05-30 14:22 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 [this message]
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
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=831r9o47y9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=48743@debbugs.gnu.org \
    --cc=akrl@sdf.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.