Le lundi 22 janvier 2024 à 18:00 -0700, Carl Sorensen a écrit : > So I ran the file in this log message: > > > carl@carls-mbp-2 build % out/bin/lilypond out/share/lilypond/current/ly/ > init.ly > > GNU LilyPond 2.25.13 (running Guile 3.0) > > Processing `out/share/lilypond/current/ly/init.ly' > > Parsing... > > out/share/lilypond/current/ly/init.ly:47:1: error: \maininput not allowed > outside init files > > > \maininput > > out/share/lilypond/current/ly/init.ly:1: warning: no \version statement > found, please add > > > \version "2.25.13" > > > for future compatibility > > out/share/lilypond/current/ly/init.ly:1: warning: no \version statement > found, please add > > > \version "2.25.13" > > > for future compatibility > > fatal error: failed files: "out/share/lilypond/current/ly/init.ly" > > > Now I have found an error in the file -- it appears ist is due to > \maininput not being allowed.
This isn't the problem. init.ly is a special file that LilyPond always loads before starting to compile any file and is not meant to be compiled standalone like this. The reason the error message mentions init.ly is that init.ly contains some Scheme code that is used to trigger the compilation. (This could be improved.) The problem really is the font issue in the error message.
signature.asc
Description: This is a digitally signed message part
