The time to initialize LilyPond is roughly 0.1s, so 40s of the
5 minutes time are spent just initializing LilyPond 400 times.
Consider passing all the files to 'lilypond' in a single
invocation,
which should be faster.
Yes, I considered doing that. It would
Le 26/11/2022 à 22:36, Eric Benson a écrit :
In anticipation of the impending release of 2.24, I recently ported my
Lilypond files from 2.22 to 2.23.81. I have about 100 lead sheets with
lyrics, parameterized so that I can easily create them in different keys
and in treble clef or bass clef.
On Nov 26, 2022, at 17:43, Eric Benson wrote:
>
> ton of warnings, mostly of the form "implicit conversion changes
> signedness". These seem like the sort of thing that might not be too hard
> to fix.
https://gitlab.com/lilypond/lilypond/-/merge_requests/1744 fixes warnings other
than
I compiled it myself, using Xcode's cc (Apple clang version 14.0.0). Got a
ton of warnings, mostly of the form "implicit conversion changes
signedness". These seem like the sort of thing that might not be too hard
to fix. It's a worthwhile goal to eliminate compiler warnings from as many
of the
On Sat, 2022-11-26 at 13:36 -0800, Eric Benson wrote:
> In anticipation of the impending release of 2.24, I recently ported my
> Lilypond files from 2.22 to 2.23.81. I have about 100 lead sheets with
> lyrics, parameterized so that I can easily create them in different keys
> and in treble clef or
In anticipation of the impending release of 2.24, I recently ported my
Lilypond files from 2.22 to 2.23.81. I have about 100 lead sheets with
lyrics, parameterized so that I can easily create them in different keys
and in treble clef or bass clef. There are all in the range of 1 to 2 pages
when
