lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: State of LilyPond with Guile 2.2


From: Thomas Morley
Subject: Re: State of LilyPond with Guile 2.2
Date: Sat, 17 Apr 2021 13:04:16 +0200

Am Sa., 17. Apr. 2021 um 12:02 Uhr schrieb Thomas Morley
<thomasmorley65@gmail.com>:
>
> Am So., 11. Apr. 2021 um 20:04 Uhr schrieb Thomas Morley
> <thomasmorley65@gmail.com>:
> >
> > Am So., 11. Apr. 2021 um 19:37 Uhr schrieb Jonas Hahnfeld via
> > Discussions on LilyPond development <lilypond-devel@gnu.org>:
> > >
> > > Am Sonntag, dem 11.04.2021 um 18:04 +0200 schrieb Han-Wen Nienhuys:
> > > > I wonder if it isn't more practical to fork guile 1.8, and stick it
> > > > into our tree as a submodule, and always build lilypond against the
> > > > in-tree version. We'd be up for the maintenance on the 1.8 branch, but
> > > > it might well be less work than keeping up with the churn that newer
> > > > GUILE versions bring us.
> > > >
> > >
> > > I had already replied that I don't like that option; it was always a
> > > given for me that LilyPond would move on. Guile 2.2 also makes binary
> > > distribution much nicer (because there no more shared srfi libraries,
> > > so lilypond can be linked as one static executable) and makes it
> > > possible to offer 64 bit executables for Windows.
> > >
> > > But given the reactions, I'll reduce activity on my work towards Guile
> > > 2.2...
> >
> > Jonas,
> >
> > once the startup delay and overall lower tempo is reduced to a
> > reasonable amount I'm for moving on to Guile-2, if not then Guile-3
> > (yes, I've read what you wrote about Guile-3).
> > Apart from the already mentioned unicode-thingy (admittedly the
> > strongest argument to move up, imho) there are also bug-fixes and new
> > functionality in newer guile-versions. The possibility to have 64 bit
> > executables for Windows is the overall strongest argument, I'd say.
> > I'd love to do my own tests etc, regrettable my spring-break is over.
> > I'll likely will have no time until next weekend.
>
> As promised I started to do some tests.
> After installing guile-2.2.6. system wide I did in the lilypond-repo:
>
>   git checkout master
>   git fetch
>   git pull -r
>   rm -fr build-guile-2-2-6/
>   sh autogen.sh --noconfigure
>   mkdir -p build-guile-2-2-6
>   cd build-guile-2-2-6/
>   ../configure GUILE_FLAVOR=guile-2.2
>   make -j4 CPU_COUNT=4
>
> Although successfully I get for every file:
> GNU LilyPond 2.23.2
> <unnamed port>: In procedure scm-error in expression (scm-error (quote
> misc-error) #f ...):
> <unnamed port>: no code for module (lily clip-region)
>
> Am I doing something wrong?

Please ignore above, I messed up my setup, sorry for the noise.

> Above was meant to get a default build, i.e. without compiled .go-files.
> Though, it's not entirely clear to me how to enable compiling those files.
> Am I correct that
> GUILE_AUTO_COMPILE=1
> is not an option while running configure, but will happen lateron by
> running some ly-file with
> GUILE_AUTO_COMPILE=1 ./out/bin/lilypond some-file.ly
> ?
>
> Cheers,
>   Harm



reply via email to

[Prev in Thread] Current Thread [Next in Thread]