Re: cadence font and lilypond-book

[Marc Hohl]

Am 17.03.2015 um 10:57 schrieb Urs Liska:
> Am 17.03.2015 um 10:53 schrieb Marc Hohl:
> > Am 17.03.2015 um 10:27 schrieb Urs Liska:
> > [...]
> > > > does not help here, lilypond-book has ceased to work, obviously.
> > >
> > > I checked the contents of lilypond-book in a number of installations and
> > > have the impression there's a quite serious bug (if I'm not completely
> > > mistaken) as all paths seem to be hardcoded in the script, independently
> > > from the path where LilyPond is actually installed:
> > >
> > > 2.18.2 (binary release)
> > > installation root: /shared/software/lilyponds/lilypond-stable
> > > appends to sys.path:
> > > - /usr/share/lilypond/2.18.2/python
> > > - /usr/lib/lilypond/2.18.2/python
> > > lilypond_binary: /usr/bin/lilypond
> > >
> > > 2.19.16 (binary release)
> > > installations root: /shared/software/lilyponds/lilypond-devel
> > > appends to sys.path:
> > > - /usr/share/lilypond/2.19.16/python
> > > - /usr/lib/lilypond/2.19.16/python
> > > lilypond_binary: /usr/bin/lilypond
> > >
> > > 2.19.18 (build from current master)
> > > build root: ~/git/lilypond/lilypond-builds/current
> > > appends to sys.path:
> > > - / usr/local/share/lilypond/2.19.18/python
> > > - /usr/local/lib/lilypond/2.19.18/python
> > > lilypond_binary: /usr/local/bin/lilypond
> >
> > THanks for checking! I think that there is something fishy with the
> > paths here...
>
> Yes, as I've written on the bug-lilypond thread (forgot to add the
> lilypond-user to CC ...) I think
> the paths should be determined relative to the realpath of the
> lilypond-book script and not use these
> arbitrary hardcoded values.
>
> Could you please provide me with a small example .lytex file so I can
> test it and try to make a patch?

Ok, see the attachments. I cannot test whether cadencetest.lytex 
compiles, since my lilypond-book does not work anymore.

Marc

cadencesong.ly
Description: Text Data

cadencetest.lytex
Description: Text document