Am 16. Juli 2017 02:20:01 MESZ schrieb Karlin High <address@hidden>:
On 7/15/2017 5:58 PM, Urs Liska wrote:
Now this is helpful and points me to the correct issue - which is indeed
an issue with oll-core. Actually this had been discussed arleady a few
months ago, but I don't recall if we came to a conclusion then.
As it stands oll-core does not work properly when the main LilyPond file
is specified as a relative path from the same directory. At some point
oll-core splits the path to the input file into its segments and for
some reason accesses the second-to-last element of this path (= the
directory in which the compiled .ly file resides). However, if you do
"lilypond olltest.ly" this path only has*one* element: the filename itself.
I would consider this a bug in oll-core, but as a workaround you should
always invoke the .ly files with their absolute path or with a relative
path that contains at least one directory.
Best
Urs
Unfortunately, entering full absolute files paths still gives errors
here. Two more log files attached, one with absolute path to LY file,
and another with full path to lilypond.exe as well.
--
Karlin High
Missouri, USA