Re: [PoC] EXPERIMENTAL binaries of LilyPond 2.22.1

[Jean Abou Samra]

Le 15/05/2021 à 16:24, Jean Abou Samra a écrit :
> Le 13/05/2021 à 22:46, Jonas Hahnfeld via Discussions on LilyPond 
> development a écrit :
>
> > Feel free to give them a try, but please keep in mind the 
> > limitations: Guile 2.2 and no compiled bytecode [1] means startup 
> > will take around 3 seconds.
>
> Having `export GUILE_AUTO_COMPILE=1` in my ~/.bash_profile (for
> development), I got many warnings, mostly about "possibly unbound
> variables", during the first run.  That's nothing different from
> current master.
>
> There is, however, one error that appears on every compilation.
> I don't have it with my local build.
>
> ;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
>
> ;;; or pass the --no-auto-compile argument to disable.
>
> ;;; compiling 
> /home/jean/lilypond-new-binaries/share/lilypond/2.22.1/scm/ly-syntax-constructors.scm
>
> ;;; WARNING: compilation of 
> /home/jean/lilypond-new-binaries/share/lilypond/2.22.1/scm/ly-syntax-constructors.scm 
> failed:
>
> ;;; unhandled constant #<fluid 7fcb2efd07f0>
>
>
>
> I don't have a full history of 2.23 development in mind.
> Was this fixed at some point?
>
> I also experienced the same problem as Lukas-Fabian with
> Unicode file names in Frescobaldi with English messages.
>
> Other than that, both the full and non-full versions run fine
> on my scores.

Today I additionally tested building with this system, too (Ubuntu 20.10).
I had to install lzip, needed to unpack the gmp tarball. Other than
that, it worked very nicely; I got the final tar archives within an
hour, without the slightest complication in setup. I didn't attempt
cross-compilation for Windows, understanding from the README.md that
it required some tricks above my pay grade.

Cheers,
Jean