lilypond-devel
[Top][All Lists]
Advanced

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

Re: LilyPond 2.23.6 released


From: Thomas Scharkowski
Subject: Re: LilyPond 2.23.6 released
Date: Wed, 16 Feb 2022 15:37:14 +0100

Hi all,

I installed this version today, everything seems to work.
It might be of interest that the MacPorts version of 2.23.6 runs around three 
times faster on my MacBookPro M1, macOs 12.1

Carver Missa compile times are 28,6“ and 10,3“ MacPorts version. 

Thomas



> Am 08.02.2022 um 14:07 schrieb Jonas Hahnfeld via LilyPond user discussion 
> <lilypond-user@gnu.org>:
> 
> We are happy to announce the release of LilyPond 2.23.6. This is termed
> a development release, but these are usually reliable. If you want to
> use the current stable version of LilyPond, we recommend using the
> 2.22.1 version.
> 
> This release also marks a transition towards Guile 2.2: The binaries
> available from http://lilypond.org/development are built using GUB with
> Guile 1.8, while the packages available from
> https://gitlab.com/lilypond/lilypond/-/releases/release%252F2.23.6-1
> were created with the new infrastructure developed over the past
> months, making use of Guile 2.2. We encourage testing with your scores
> to make sure that future releases of LilyPond will continue to work for
> you. If there are problems with the version using Guile 2.2 that cannot
> be reproduced with the binaries using Guile 1.8, we would love to hear
> about them as early as possible.
> 
> The binaries with Guile 2.2 are different in a number of ways, the two
> major changes being:
> 1. All binaries are 64-bit only and available for Linux, Windows (via
> mingw), and macOS. In particular, this finally means official binaries
> that work on macOS >= 10.15, which cannot run 32-bit programs anymore.
> 2. There is no installation, simply extract the downloaded tar or zip
> (for Windows) archive and run it. The binaries don't include a GUI
> anymore, we recommend using third-party editors such as Frescobaldi.




reply via email to

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