Reviewers: ,
Message:
Please review.
Description:
Documentation/GNUmakefile: Add dependencies for internals.texi
The texinfo file internals.texi for the Internals Reference is
generated from ly/generate-documentation.ly, which in turn relies on
scm/document*.scm and their recursive dependencies to do the actual
work. In the process, settings encoded in various other files get
documented, e.g. from ly/engraver-init.ly and scm/define-*.scm.
Changes to such files do not necessitate, nor trigger, recompiling the
LilyPond binary; yet the only dependency marked for internals.texi in
Documentation/GNUmakefile was on $(LILYPOND_BINARY).
Fix this, for this is obviously inconvenient when hacking the
Internals Reference.
Rather than tediously maintaining a specific list that grows
incomplete whenever the scope of the IR expands, make internals.texi
depend on $(INIT_LY_SOURCES) and $(SCHEME_SOURCES) altogether, similar
to the rules in make/ly-rules.make.
Please review this at https://codereview.appspot.com/6943053/
Affected files:
M Documentation/GNUmakefile
Index: Documentation/GNUmakefile
diff --git a/Documentation/GNUmakefile b/Documentation/GNUmakefile
index
a3ef4bb6e7c6640249ed9244139374a09a5a2de1..924b391cbbe27bac37597458fffad054c5f88e15
100644
--- a/Documentation/GNUmakefile
+++ b/Documentation/GNUmakefile
@@ -284,7 +284,7 @@ $(outdir)/ly-grammar.txt: $(top-src-dir)/lily/parser.yy
# of internals every time. however, this triggers
# compilation during install, which is a bad thing (tm).
-$(outdir)/internals.texi: $(LILYPOND_BINARY)
+$(outdir)/internals.texi: $(LILYPOND_BINARY) $(INIT_LY_SOURCES)
$(SCHEME_SOURCES)
cd $(outdir) && $(buildscript-dir)/run-and-check "$(LILYPOND_BINARY)
--verbose
$(top-src-dir)/ly/generate-documentation" "generate-documentation.log"
###############################################
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
