Am Montag, dem 19.04.2021 um 10:39 +0200 schrieb Thomas Morley: > Am Mo., 19. Apr. 2021 um 08:42 Uhr schrieb Jonas Hahnfeld <hah...@hahnjo.de>: > > > > (2) > > > If I switch to a different branch, with changed .scm-files, do some > > > work there and then switch back (NB in this branch the scm-files are > > > _not_ changed inbetween) I need to recompile guile, a real nuisance. > > > Could this be improved? > > > > I'm not sure I understand this: Do you mean the .scm files from Guile > > itself, or the .scm files from LilyPond? If the latter, do you mean > > "recompile" with GUILE_AUTO_COMPILE=1? > > I noticed it while testing compiled guile-code. In a break I manually > bisected the cause for #6120 > For this task I switched to my build-directors with guile-1. > Afterwards back to the guile-2 build-directory. > > Maybe a minimal example demonstrates it better than any explanation: > In lilypond master: > $ /home/hermann/lilypond-git/build-guile-2-2-6/out/bin/lilypond scheme-sandbox > $ git checkout release/2.22.0-1 > $ /home/hermann/lilypond-git/build/out/bin/lilypond scheme-sandbox > (Some error occurs, ignore) > $ git checkout master > $ /home/hermann/lilypond-git/build-guile-2-2-6/out/bin/lilypond scheme-sandbox > -> > GNU LilyPond 2.23.3 > ;;; note: source file > /home/hermann/lilypond-git/build-guile-2-2-6/out/share/lilypond/current/scm/lily/lily.scm > ;;; newer than compiled > /home/hermann/lilypond-git/build-guile-2-2-6/out/share/lilypond/current/guile/ccache/2.2-LE-8-3.A/home/hermann/lilypond-git/scm/lily.scm.go > ... > ... > > Obviously, it's not seen that unchanged master is indeed unchanged.
To know that, it would need to compute a hash or something of the file, but AFAICT Guile only looks at file modification dates (like most other software, including 'make'). And those did change when you switched between branches. Jonas > Thus a new round of GUILE_AUTO_COMPILE=1 is needed. > > Cheers, > Harm
signature.asc
Description: This is a digitally signed message part
