Werner LEMBERG ... > Of course, there are other 'classical' tools, like setting up a proper > Makefile that automatically re-generates all out-of-date LilyPond PDFs > (you would then simply say `make`, never calling LilyPond or LaTeX > directly). Programmers are used to that, but other people are > probably not enthused to learn how to call `make` and how to create > Makefiles...
It is not that easy to the depenancies right, lilypond files can have \include's, and it can also call external scheme code. Here is a try to find depenancies: https://aspodata.se/git/musik/bin/depend_ly > The biggest advantage of using `lilypond-book` or `lyluatex` is to > have both the text and the music source code in the same input file. > However, this is just a convenience, it is not a necessity. Yes, convenient for small projects. With larger projects, it is nice to have lilypond code in separate files, so that the files don't get to large, and you can check each lilypond snippet independently for correctness. Regards, /Karl Hammar
