From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: bug-gnu-emacs@gnu.org, dann@ics.uci.edu
Subject: Re: please make byte compiling during bootstrap take advantage of make -j
Date: Thu, 08 May 2008 15:34:55 -0400 [thread overview]
Message-ID: <hmd4nwlhcw.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <uzlr1ccly.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 08 May 2008 13:30:01 +0300")
Eli Zaretskii wrote:
> Yes, include is non-portable.
Is there a good reference for what is portable? Ideally, for what
Emacs wants to support...
In the GNU Make manual, "Features of GNU make" seems only to say that
including multiple files with a single include is a GNU extension.
And in the section "Old-Fashioned Suffix Rules", it says that "Suffix
rules cannot have any prerequisites of their own", yet we have:
.el.elc: $(lisp)/subdirs.el
in lisp/Makefile.
> I think you can safely have a full list of all .el files, and let the
> no-byte-compile tag take care of which ones are actually compiled.
Yes, that seems to work.
> You could use the list of .el files with .el=.elc construct.
Can I portably use this kind of thing:
lispfiles1 = $(lisp)/*.el
lispfiles2 = $(lisp)/*/*.el
elcfiles1 = $(lispfiles1:.el=.elc)
elcfiles2 = $(lispfiles2:.el=.elc)
compile: $(elcfiles1) $(elcfiles2)
?
next prev parent reply other threads:[~2008-05-08 19:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18495.14322.3139.653674@fencepost.gnu.org>
2008-05-04 17:35 ` please make byte compiling during bootstrap take advantage of make -j Dan Nicolaescu
2008-05-04 18:49 ` Eli Zaretskii
2008-05-05 18:15 ` Glenn Morris
2008-05-07 3:05 ` Glenn Morris
2008-05-07 9:47 ` Eli Zaretskii
2008-05-07 22:33 ` Glenn Morris
2008-05-08 10:30 ` Eli Zaretskii
2008-05-08 19:34 ` Glenn Morris [this message]
2008-05-09 6:32 ` Eli Zaretskii
2008-05-09 7:02 ` Dan Nicolaescu
2008-05-09 7:41 ` Eli Zaretskii
2008-05-07 17:34 ` Richard M Stallman
2008-05-29 23:20 ` bug#189: marked as done (please make byte compiling during bootstrap take advantage of make -j) Emacs bug Tracking System
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=hmd4nwlhcw.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=bug-gnu-emacs@gnu.org \
--cc=dann@ics.uci.edu \
--cc=eliz@gnu.org \
/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).