Dear William and Saul,
thanks for your helpfull posts! I managed to compile the scheme file
by using the GUILE_AUTO_COMPILE=1 environment setting.
I tried it before but failed because I did not know how to set it
successfull with the fish shell I use. Now I know :)
The compiled file will be writt
If you look at LilyPond's code for initializing Guile in main.cc, you'll
see that LilyPond by default turns off automatic compilation of Guile code,
I'm guessing for empirical performance reasons. If you set the environment
variable GUILE_AUTO_COMPILE=1, I wonder if the warning will go away because
Dear Robert,
It sounds like you will have to compile Lilypond from source. I can not
help you with that, sorry, hopefully someone else can. However, in the
meantime, have you considered whether you could achieve what you were
hoping for by re-setting scheme variables using "set!" or similar sc
I want to extend lilypond functionality by altering an provided scheme
file
(in particular fret-diagrams.scm, adding bass fret as label).
I did the changes to the file but if I start lilypond it complains with:
;;; note: .../fret-diagrams.scm
;;; newer than compiled .../ccache/lily/fret-diagrams.
