Am Samstag, 11. Dezember 2010, um 00:38:54 schrieb Graham Percival: > On Sat, Dec 11, 2010 at 12:21:42AM +0100, Francisco Vila wrote: > > 2010/12/10 Graham Percival <gra...@percival-music.ca>: > > > Yes, you'll discover any compile *failures*. But our build system > > > does not rebuild any manual unless the "main" file (in > > > Documentation/*.te??) is touched. Since we only alter those files > > > twice a year or so, there's lots of old docs on kainhofer. > > > > Why not touch everything that is touchable (files, I mean) and force a > > complete compiling, daily? > > If you want to force a complete compile, then I recommend removing > the build directory entirely and starting from scratch. This is > very easy with an out-of-tree build.
Unfortunately, it seems that an out-of-tree build does not work for the docs, only for the binaries. In particular: -) Documentation/out-www/version.itexi is not created, so lilypond-book fails -) Later on, lilypond-book does not find some included *.itely files: All snippets are up to date... Compiling /home/lilypond/build/Documentation/out-www/common-macros.texi... /home/lilypond/build/Documentation/out-www/common-macros.texi is up to date. Processing include: pitches.itely lilypond-book.py: error: file not found: pitches.itely Cheers, Reinhold -- ------------------------------------------------------------------ Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
