unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Corallo <akrl@sdf.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 17:46:03 +0300	[thread overview]
Message-ID: <8335u32c7o.fsf@gnu.org> (raw)
In-Reply-To: <xjfbl8rkol3.fsf@sdf.org> (message from Andrea Corallo on Mon, 31 May 2021 13:41:28 +0000)

> From: Andrea Corallo <akrl@sdf.org>
> Cc: "T.V Raman" <raman@google.com>, 48743@debbugs.gnu.org
> Date: Mon, 31 May 2021 13:41:28 +0000
> 
> yes I'm following this thread, trying ATM to make my mind on what's the
> real issue.

Thanks.  Let me try helping you understand what I think is the issue
here.

Suppose you are maintaining a Lisp package which includes a Makefile
used to byte-compile all the Lisp files as part of the installation
procedure of the package.  This Makefile has targets and dependencies
that build *.elc files from *.el files.  How do you modify the
Makefile to produce *.eln files during the build, while maintaining
the dependencies between the Lisp files? the dependencies would mean
that when file1.el is modified, you need to recompile not only that
file1.el, but also file2.el and file3.el.  How do you get new
file2.eln and file3.eln via Makefile rules in this case?

I hope I succeeded to explain the issue.





  reply	other threads:[~2021-05-31 14:46 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 [this message]
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=8335u32c7o.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 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).