Hi,

Having seen that many here are using 2.19, I thought I'd have a go. I use both Mac/OS and Linux, but what I'm describing here is for Mac/OS.

I install lilypond via macports which provides two packages:

   lilypond @2.18.2_5 (textproc)
   lilypond-devel @2.19.80 (textproc)

So, I deactivated lilypond and activated lilypond-devel in order to use 2.19.

My first test did not work:

   bombyx:~/Music/Matt/Song2017-09-28$ make -B
   lilypond -drelative-includes -I/Users/matt/Music/mattlib/ PianoScore.ly
   GNU LilyPond 2.19.80
   Processing `PianoScore.ly'
   Parsing.../opt/local/share/lilypond/2.19.80/scm/lily-library.scm:375:14:
   In procedure ly:add-context-mod in expression (ly:add-context-mod
   mods (list # #)):
   /opt/local/share/lilypond/2.19.80/scm/lily-library.scm:375:14: Wrong
   type argument in position 1 (expecting Context_mod): #f
   make: *** [PianoScore.pdf] Error 1

There are no error messages referring to my own lilypond source files, which makes me wonder what's going on here.

I understand that the lilypond-devel package is not intended to be stable, and so bugs may appear. Is that what's happening here? If not, I'm happy to try to create a small example that exposes this error.

Would I be better advised to stick to the lilypond package and 2.18? Or is there another route to installing a stable 2.19 without too much work (I keep running into comments about how difficult it is build lilypond from source).

When I tried lilypond 2.19 on a different score, I had the above error, but also some relating to my own .ly files. I guess there are changes that I need to make to my source (even though I have `\version "2.18.2"` in the source). Is that right? Is there a guide to these changes?


I think this is my first post here, which seems like an appropriate time to say that lilypond is a phenomenal piece of software - thanks to all involved.

Matt

_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to