[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issues with documentation not compiling when changing lilypond-texi2

From: David Kastrup
Subject: Re: Issues with documentation not compiling when changing lilypond-texi2html.init
Date: Mon, 09 Dec 2013 19:05:15 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

James <address@hidden> 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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]