Reinhold, your wrote Tuesday, February 24, 2009 3:25 PM
Am Dienstag, 24. Februar 2009 schrieb Trevor Daniels:
Reinhold
Some recent changes I made in git to the LM don't seem to have
made
it to the version on the kainhofer website, although later
changes
to the NR have. Is anything failing in the generation of the LM?
Actually, yes, a new, clean build is failing when lilypond-book
tries to
process the LM (in particular the templatex.itely), since it can't
find the
orchestra-choir-and-piano-template.ly file (which is in
input/new/):
[...]
All snippets are up to date...
Compiling
/home/lilypond/lilypond/Documentation/user/out-www/working.texi...
/home/lilypond/lilypond/Documentation/user/out-www/working.texi is
up to date.
Processing include: templates.itely
Reading templates.itely...
Dissecting...lilypond-book.py: error: file not found:
orchestra-choir-and-
piano-template.ly
Traceback (most recent call last):
File "/home/lilypond/lilypond/scripts/lilypond-book.py", line
2108, in
<module>
main ()
File "/home/lilypond/lilypond/scripts/lilypond-book.py", line
2090, in main
chunks = do_file (files[0])
[...]
The .ly file is in input/new/, but the call to lilypond-book only
passes
input/, input/lsr/, input/regression/, input/manual/ and
input/tutorial/ as
include directories, but not input/new/. So, of course
lilypond-book does not
find that included file...
That fits exactly! Adding that template to input/new
and the ref to it were the changes I'd made. The template
has to be in input new as the LSR is still on 2.10 and
the template uses nested StaffGroup contexts.
Many thanks!
Trevor
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
