From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Recursive makefiles
Date: Thu, 29 Aug 2013 00:21:47 +0200 [thread overview]
Message-ID: <87eh9d5udg.fsf@gnu.org> (raw)
In-Reply-To: <20130828214126.GA26655@debian> (Andreas Enge's message of "Wed, 28 Aug 2013 23:41:26 +0200")
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
Andreas Enge <andreas@enge.fr> skribis:
> On Wed, Aug 28, 2013 at 11:09:40PM +0200, Ludovic Courtès wrote:
>> Please don’t do that: the build system purposefully avoids recursive
>> makefiles, to improve parallelism etc. (see
>> <http://miller.emu.id.au/pmiller/books/rmch/>.)
>
> I did it for two reasons:
> - It allows to type "make ps" and "make pdf" in the main directory,
> instead of "cd doc; make pdf; cd ..".
Hmm, there was no Makefile in doc/, so how could “cd doc; make pdf” work?
> - It avoids clutter in the main directory (not checked this time, but I
> think there were a few files guix.* then).
I just tried “make pdf” from 3d1b29a, and, surprise: it doesn’t do
anything. :-)
Turns out that the “doc/guix.pdf:” line in Makefile.am annihilated the
built-in rule. This is “fixed” with:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 513 bytes --]
diff --git a/Makefile.am b/Makefile.am
index 6eb4c0f..710f708 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -210,9 +210,9 @@ DOT_OPTIONS = \
dot -Teps $(DOT_OPTIONS) < "$<" > "$@.tmp"
mv "$@.tmp" "$@"
-doc/guix.pdf: doc/images/bootstrap-graph.png
-doc/guix.info: doc/images/bootstrap-graph.png
-doc/guix.ps: doc/images/bootstrap-graph.eps
+# doc/guix.pdf: doc/images/bootstrap-graph.png
+# doc/guix.info: doc/images/bootstrap-graph.png
+# doc/guix.ps: doc/images/bootstrap-graph.eps
if BUILD_DAEMON
[-- Attachment #3: Type: text/plain, Size: 383 bytes --]
With that, “make pdf” at the top level creates doc/guix.pdf, and leaves
no intermediate files at all at the top level.
Is it an acceptable solution for you (provided the bug above is fixed
nicely)? If so, I’ll prepare a patch.
I feel quite strongly about avoid recursive Makefiles, so I’d prefer to
fix any bugs in the current build system.
Thanks,
Ludo’.
next prev parent reply other threads:[~2013-08-28 22:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1VElgT-0006f7-UH@vcs.savannah.gnu.org>
2013-08-28 21:09 ` Recursive makefiles Ludovic Courtès
2013-08-28 21:41 ` Andreas Enge
2013-08-28 22:21 ` Ludovic Courtès [this message]
2013-08-28 22:25 ` Andreas Enge
2013-08-29 20:04 ` Ludovic Courtès
2013-08-29 20:27 ` Andreas Enge
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=87eh9d5udg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--cc=guix-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/guix.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.