Closed GoogleCodeExporter closed 9 years ago
This is because the LilyPond executable path isn't correct. Just made the
thrown exception reflect this in r8721d344cc64, releasing soon...
Original comment by harmathdenes
on 6 Jul 2011 at 11:21
I'm not sure if this is the point.
The LilyPond executable path is set to /usr/bin/lilypond where the executable
is.
<ctrl>+<t> does its job and compiles the pdf file.
But the init.ly is in /usr/share/lilypond/2.12.3/ly/init.ly. How could this
file be found based on the LilyPond executable path?
Original comment by dirk.kas...@gmail.com
on 6 Jul 2011 at 12:10
Ah, I see, the Ubuntu package sets the directory name to '2.12.3' instead of
'current'. As a workaround, you can manually create a symlink:
$ cd /usr/share/lilypond
$ sudo ln -s 2.12.3 current
Original comment by harmathdenes
on 6 Jul 2011 at 12:22
thx for your help. The workaround works fine.
Original comment by dirk.kas...@gmail.com
on 6 Jul 2011 at 12:27
I'd like to add that Fedora also doesn't have /usr/share/lilypond/current .
Original comment by jvrom...@gmail.com
on 30 Jul 2011 at 2:15
Issue 45 has been merged into this issue.
Original comment by harmathdenes
on 27 Feb 2012 at 10:40
Original issue reported on code.google.com by
dirk.kas...@gmail.com
on 6 Jul 2011 at 11:01Attachments: