Comment #11 on issue 1852 by julien.r...@gmail.com: manuals needs more explicit dependencies
http://code.google.com/p/lilypond/issues/detail?id=1852
I must admit that I overlooked .texi files because I assumed all such files were included files, not main files. I see now that contributor.texi is a main file which links to many included files, and indeed no .dep file is generated. I immediately see a few ways to possibly fix this:
1) Renaming these main .texi files to .tely would work I think, as lilypond-book would track the dependencies and produce .texi and .dep files, or 2) Changing the build rule for .texi files so that they get processed by lilypond-book, or 3) Using grep, sed, or python to search for @include lines in .texi files and write the corresponding .dep file. This requires adding a step to the build rule.
_______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
