Re: Issue 1635 in lilypond: clean up misleading warnings in website build

[lilypond]

Comment #29 on issue 1635 by address@hidden: clean up  
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635

I haven't done an exhaustive file-by-file check of why they don't exist,  
but basically it's because there are links to them in the source files used  
in the website build, but they're only actually built when we make the  
docs.  If, for example, you go to  
/lilypond-git/build/out-website/notation.html and follow any of the links,  
they're not there.  Specific examples of this are some of the .itexi files,  
which come from bibliography source and are only built with make doc, and a  
lot of files containing snippets.  I think identifying the "known not  
there" files is a sound approach - the only alternatives would be to make  
all the files that could be linked to - and that's really running a make  
doc, or modifying the way the extract*.py file follows links, which sounds  
even more tricky.