Am 12.08.2011 19:05, schrieb Julien Rioux:
I solved this now. The problem is that one cannot simply call
"lilypond-book". This is a python script and no executable, therefore
one needs to start it with python. Furthermore only executables are
automatically found if they are in LyX's PATH variable, therefore one
has to give the full path to lilypond-book.py.
Right, this is what I said in the part of the email which you elided.
What did I elide?
If you already knew this, why do we then not call the script via python in configure.py? I think
this should be corrected. Does it work for you, if you replace in configure.py this line?:
\converter lilypond-book pdflatex "lilypond-book --safe --pdf --latex-program=pdflatex
--lily-output-dir=ly-pdf $$i" ""
by this one:
\converter lilypond-book pdflatex "python lilypond-book.py --safe --pdf --latex-program=pdflatex
--lily-output-dir=ly-pdf $$i" ""
I implemented this now:
http://www.lyx.org/trac/changeset/39479
This might work for your installation but we should think of a better fix.
Strings like
\"C:\\Program Files (x86)\\LilyPond\\usr\\bin\\lilypond-book.py\" are not
portable.
You mean the fixed path? - that was a commit mistake I already corrected. The path is stored in a
variable that is determined at installation time.
So now lilypond-book is correctly executed when viewing the lilypond.lyx
example file as PDF (pdflatex). But there are is bug in LilyPond: I get
during the compilation:
Missing set(['ec/lily-5e700a3e.txt', 'ec/lily-5e700a3e.ly',
'ec/lily-5e700a3e-sy stems.count'])
Removing `D:\LyXSVN\LyX2.0.x\lib\examples\lilypond.tex'
And indeed, there are folders "ec1" to "ec5" but no folder named "ec".
I also get this when using lilypond-book with the command line, so
definitively no LyX problem. Can you please take over and report it to
the LilyPond people or can't you reproduce this with Lilypond 2.14.2?
Sorry, I cannot reproduce. The example file compiles perfectly to both dvi and
pdf.
OK, then I will report this bug to Lilypond.
regards Uwe
