From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Recursive compilation?
Date: Tue, 31 May 2011 18:52:17 -0300 [thread overview]
Message-ID: <jwvmxi2pmo3.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m362oq7g86.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Tue, 31 May 2011 22:44:09 +0200")
> The obvious "gotcha" here is that one probably shouldn't try to
> (recursively) byte-compile files in directories that we don't have write
> access to. So if somebody has set their load-path to my directory, and
> I have an old .elc file there, then this function shouldn't try to
> compile that file, too.
Right, cyclic require loops can definitely happen in such cases.
But they're easy to break.
> The other caveat is that Makefiles typically first mark all files that
> are to be compiled, and then compile them. This would then possibly
> lead to some files being compiled twice. However, that could be worked
> around by `byte-compile-file-recursively' not compiling a file that it's
> been asked to compile if the .elc file is newer than the .el file.
It's also a problem with parallel make.
> I have a feeling that this won't be very difficult to implement, but it
> needs meddling with the C layer, since `require' is a C function. But I
> think it would make compiling Emacs after a "bzr update" a lot less
> likely to break.
Another approach is to build a set of makefile dependencies from the
`require' calls. I did that at some point in the past. It wasn't too
hard to do. But there are also the cases of preloaded files, as well as
autoloaded macros/functions.
I'm personally using a different hack which doesn't solve all those
problems either but is simple and doesn't suffer from as many problems
in my experience: prefer loading the .el file if it's more recent.
Stefan
next prev parent reply other threads:[~2011-05-31 21:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 20:44 Recursive compilation? Lars Magne Ingebrigtsen
2011-05-31 21:52 ` Stefan Monnier [this message]
2011-05-31 22:17 ` Lars Magne Ingebrigtsen
2011-06-01 1:38 ` Stefan Monnier
2011-06-01 11:48 ` Lars Magne Ingebrigtsen
2011-06-01 20:14 ` Dimitri Fontaine
2011-06-03 21:55 ` Lars Magne Ingebrigtsen
2011-06-04 6:29 ` Eli Zaretskii
2011-06-04 15:54 ` Lars Magne Ingebrigtsen
2011-06-04 16:08 ` Eli Zaretskii
2011-06-04 17:50 ` Glenn Morris
2011-06-06 20:05 ` Stefan Monnier
2011-06-09 17:51 ` Lars Magne Ingebrigtsen
2011-06-04 17:48 ` Glenn Morris
2011-06-06 20:46 ` Dimitri Fontaine
2011-06-07 0:23 ` Daniel Colascione
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=jwvmxi2pmo3.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@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 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.