Am 15.07.2017 um 23:02 schrieb Karlin High: > On 7/15/2017 2:38 AM, Urs Liska wrote: >> Can >> it be that >> a) >> you now have*both* oll-core and oll-core-master directories withing C:\oll > Yes, that is how I had it. The zip folder from Github produced > oll-core-master, and I wasn't aware it needed renaming to just oll-core.
Well, I hadn't been aware of this problem, too. So I'll have to properly document this ASAP. > >> and b) >> olltest.ly has the line >> \include "oll-core-master/package.ily" in it? >> >> because: >> >>> C:\Users\karlin\Music\LilyPond\olltest>lilypond -I C:\oll\ olltest.ly >>> GNU LilyPond 2.19.62 >>> Processing `olltest.ly' >>> Parsing... >>> C:/oll/oll-core-master/package.ily:57:2: error: GUILE signaled an >> This indicates that the file C:/oll/oll-core-master/package.ily has >> successfully been found - but we don't want that at all. >> >> So if my assessment is correct you should fix the include in olltest.ly >> and rerun. >> >> Thanks for taking the time narrowing this issue down. >> >> Urs > Rename and cleanup done; now everything from Gituhub is in > C:\oll\oll-core\ and I'm compiling this code... > > % File is at C:\Users\karlin\Music\LilyPond\olltest\olltest.ly > \version "2.19.62" > \include "oll-core/package.ily" > \relative c'' {c4 d e f} > > ...and it looks like this: > > C:\Users\karlin\Music\LilyPond\olltest>lilypond -I C:\oll\ olltest.ly > GNU LilyPond 2.19.62 > Processing `olltest.ly' > Parsing... > C:/oll/oll-core/package.ily:57:2: error: GUILE signaled an error for > the express > ion beginning here > # > (if (not (defined? 'openlilylib-root)) > Value out of range 0 to 4294967295: -1 > Interpreting music... > Preprocessing graphical objects... > Finding the ideal number of pages... > Fitting music on 1 page... > Drawing systems... > Layout output to `./tmp-lilypond-eg2Ldd'... > Converting to `olltest.pdf'... > Deleting `./tmp-lilypond-eg2Ldd'... > fatal error: failed files: "olltest.ly" > > I still get a good PDF file from that. This is not surprising. Loading of oll-core fails, but the music you have entered does not in any way depend on that. > But if instead I do... lilypond > -V -I C:\oll\ olltest.ly ...I get the attached log file, and no PDF. 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 > -- > Karlin High > Missouri, USA -- u...@openlilylib.org https://openlilylib.org http://lilypondblog.org _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user