James <pkx1...@gmail.com> writes: > Hello, > > On 09/12/13 14:03, Carl Peterson wrote: >> When trying to work the Documentation/lilypond-texi2html.init file, I have >> observed that changing this file does not trigger the documentation to >> rebuild when running make. However, >> changing Documentation/css/lilypond-manuals.css triggers the entire >> documentation to rebuild. This seems backwards, since >> lilypond-texi2html.init touches pretty much every part of the >> documentation, and the css file isn't actually involved in compiling >> anything. >> >> The command being run to make the documentation for the website is: >> >> make WEB_TARGETS="offline online" doc >> >> per >> http://lilypond.org/doc/v2.17/Documentation/contributor/debugging-website-and-docs-locally > > Yes the doc build system does have its quirks - the website is built > by the same process as the PDFs. > > http://lilypond.org/doc/v2.17/Documentation/contributor-big-page.html#building-documentation > > I cannot say if that is related to the website, but it is possible.
I think the point was that the content of the css file is not relevant for creating any of the other files: the css is ultimately combined with the other files in the _browser_. So it seems nonsensical to declare it as a dependency for anything but those targets that copy the css file into a target directory. -- David Kastrup _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
