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 LilyPond will recompile the changed Scheme file.
On Tue, Feb 11, 2025 at 8:39 AM William Rehwinkel via LilyPond user discussion <lilypond-user@gnu.org> wrote: > 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 scheme > procedures? A little bit like this: > https://lists.gnu.org/archive/html/lilypond-user/2015-03/msg00201.html > > -William > > On 2/10/25 18:04, robert--- via LilyPond user discussion wrote: > > 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.go > > > > Is there a way to achieve the compilation with lilypond. Or do I have to > > use guile for this? > > > > > > > > -- > William Rehwinkel (any pronouns) > Juilliard School '26 - Oberlin Conservatory '24 > will...@williamrehwinkel.net - https://williamrehwinkel.net > PGP Public Key: https://ftp.williamrehwinkel.net/pubkey.txt >
