Comment #1 on issue 1852 by [email protected]: manuals needs more
explicit dependencies
http://code.google.com/p/lilypond/issues/detail?id=1852
lilypond-book produces *.dep files tracking the dependencies of *.tely
project files. These are included into the build process in
stepmake/stepmake/generic-targets.make:
-include $(outdir)/dummy.dep $(wildcard $(outdir)/*.dep)
The - suppresses any error messages, the dummy.dep files are always created
empty.
These *.dep files are supposed to be parsed by make and effectively add
dependencies for each input .tely file. The problem is that the dependency
rules in the *.dep files do not match the dependency rules during the build
process.
For example, Documentation/out/usage.dep has
/home/jrioux/git/lilypond/Documentation/out/usage.texi: usage.tely
macros.itexi /home/jrioux/git/lilypond/Documentation/out/version.itexi
common-macros.itexi usage/running.itely usage/updating.itely
usage/lilypond-book.itely usage/external.itely
Notice the mixing of absolute and relative paths. The relative paths are
relative to Documentation, which is good. Adjusting lilypond-book.py to use
a relative path in the target seems to fix the issue.
Attachments:
1852-make-doc-dependencies.patch 650 bytes
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
