Re: Installing Lilypond 2.23.10

[David Sumbler]

On Wed, 2022-07-13 at 23:00 +0200, Jean Abou Samra wrote:

Le 13/07/2022 à 20:26, David Sumbler a écrit :

Thank you for that.  Yes, I should have noticed that the contents of

the tar file were not source code.  As it is, though, I'm not entirely

sure what to do with it - I guess that I put it all in a folder

somewhere and then make a link to bin/lilypond.

You just extract it somewhere and it becomes usable as

/.../lilypond-2.23.10/bin/lilypond file.ly

If you want to invoke it as "lilypond file.ly" without typing

the full path, you have to add the /.../lilypond-2.23.10/bin

directory to your PATH. One way to do so is to add this line

to your shell startup file (probably ~/.bashrc):

export PATH=/.../lilypond-2.23.10/bin:$PATH

That said, if you're using Frescobaldi, this is not needed.

Go to Edit > Preferences > LilyPond Preferences and add the

new version, providing  /.../lilypond-2.23.10/bin/lilypond as

the executable.

I don't use Frescobaldi; I normally edit Lilypond files in Emacs.

I moved the 2.23.10 folder to my home folder.  I tried making soft and hard links in my $HOME/bin folder to

 $HOME/lilypond-2.23.10/bin/lilypond, but for some reason I couldn't get it to run, even though $HOME/bin is the first item in my PATH.  I haven't yet fathomed out why this was, but I worked around it by adding a direct reference to the folder as you suggested.

A more serious problem (for me) is that Emacs could no longer find Lilypond mode.  So I moved the new Lilypond to /usr/local/lilypond/usr/.  Emacs can now uses Lilypond mode, but can't compile a file - it produces reams of messages (after much processing time), mostly of the

;;; note: source file /usr/local/lilypond/usr/share/lilypond/2.23.10/scm/lily/display-lily.scm

;;; newer than compiled /usr/local/lilypond/usr/lib/lilypond/2.23.10/ccache/lily/display-lily.go

kind, and then exits with

ERROR: In procedure apply-smob/1:

Wrong number of arguments to #<boot-closure 7fa410c90dc0 (_ . _)>

Compilation exited abnormally with code 1 at Thu Jul 14 17:21:52

I have spent some hours experimenting, but so far I haven't managed to get things working.

David