[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 1635 in lilypond: clean up misleading warnings in website buil
From: |
lilypond |
Subject: |
Re: Issue 1635 in lilypond: clean up misleading warnings in website build |
Date: |
Fri, 29 Apr 2011 12:25:31 +0000 |
Comment #17 on issue 1635 by address@hidden: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
@comment 15 - I can only find winds.itely in build/out and it's put there
(I reckon) by a doc build. I've just nuked my build directory and re-run
configure and make website and there's no trace of winds.itely. I believe
it comes from a snippet build? So - we can't guarantee finding files like
that in a fresh system with a make website.
@comment 16 - I have been tracing these with echo/print statements, and I
have been looking at all the warnings - fire them at a file and view them
in gedit is an easy way to do this. And - the warnings occur because the
files it warns about are not in the search list of the .py file, because
they're in \build\out which generally doesn't exist with a clean build
directory.
The build order is given by:
website: website-texinfo website-css website-pictures website-examples
web-post
website-texinfo: website-version website-xrefs website-bibs
(website texinfo then runs texi2html and mass-link.py)
So the order is version, xrefs, bibs, texinfo itself, css, pictures,
examples.
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, (continued)
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/28
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/28
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/28
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/28
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build,
lilypond <=
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/30
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/30
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/30
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/30
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/30