|
From: | Urs Liska |
Subject: | Re: ghostscript fails on pdf generation |
Date: | Wed, 7 Jun 2017 16:02:00 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 |
Am 07.06.2017 um 15:54 schrieb N.
Andrew Walsh:
What happens when you are invoking LilyPond (and not only gs) from the command line?
I think Lilypond should use its own. This somewhat looks like being related to https://github.com/wbsoft/frescobaldi/pull/926 where I added support for adding LilyPond's library path to the lilypond invocation from Frescobaldi. However, my questions and investigations on the lists didn't turn out anything interesting with regard to LilyPond installed by the package managers, so I didn't handle the case specifically. How exactly is LilyPond registered in Frescobaldi for you? Maybe if it is only calling "lilypond" (i.e. without an absolute path to the executable) there may be something to be done about it. Ah, wait: are you using Frescobaldi's 3.0.0 release or run it from Git? My patch was only applied after the latest release ... Best Urs
-- address@hidden https://openlilylib.org http://lilypondblog.org |
[Prev in Thread] | Current Thread | [Next in Thread] |