|
From: | Urs Liska |
Subject: | Re: LD_LIBRARY_PATH in different installation contexts |
Date: | Tue, 11 Apr 2017 18:01:20 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 |
Am 11.04.2017 um 17:47 schrieb N.
Andrew Walsh:
This is not odd. At a certain point Lily is released and gets the next version number. This is what you can download as a release or as the source code. The version is increased in the Git repository, and development happens on release+1 until that is released and made public.
Yes, this is still an issue. People have successfully built LilyPond against Guile 2, but that seems to still require patches and doesn't work in a satisfactory way (e.g. *significant* performance issues).
Yes, I think this basically is the issue I'm trying to solve with my Frescobaldi patch. Urs
-- address@hidden https://openlilylib.org http://lilypondblog.org |
[Prev in Thread] | Current Thread | [Next in Thread] |