LilyPond build for windows?

What is the status of our lilypond binary on windows? The GUB based binary used to include a hacked-together Python interpreter, which -due to being cross-compiled- had some serious limitations. Is this still the binary we recommend to use ? -- Han-Wen Nienhuys - hanw...@gmail.com -

Re: releasing 2.21.2

On Sat, Jun 20, 2020 at 3:01 PM Jonas Hahnfeld wrote: > > Am Samstag, den 20.06.2020, 13:55 +0100 schrieb Phil Holmes: > > OK. First question. Should I switch completely to GitLab for doing all the > > updating of news, VERSION, etc? That is - pretty much stop using Savannah > > for anything

Re: releasing 2.21.2

OK. First question. Should I switch completely to GitLab for doing all the updating of news, VERSION, etc? That is - pretty much stop using Savannah for anything except GUB builds using my GUB user. -- Phil Holmes - Original Message - From: "Jonas Hahnfeld" To: "lilypond-devel"

Re: releasing 2.21.2

Am Samstag, den 20.06.2020, 13:55 +0100 schrieb Phil Holmes: > OK. First question. Should I switch completely to GitLab for doing all the > updating of news, VERSION, etc? That is - pretty much stop using Savannah > for anything except GUB builds using my GUB user. Yes, that would be best.

Re: Parsing JSON in C++

>> 1. LilyPond already seems to use some parts of the BOOST library (which >> is kind of the extended C++ STL). > > Not that I know of. > You're right. I just quickly skimmed through a grep and found this: https://github.com/lilypond/lilypond/blob/master/flower/include/yaffut.hh#L2 or a

Re: Parsing JSON in C++

Noeck writes: >> in C++ I worked with property_trees from BOOST (under the BOOST license): >> >> https://www.boost.org/doc/libs/1_73_0/doc/html/property_tree.html > > Two more remarks: > > 1. LilyPond already seems to use some parts of the BOOST library (which > is kind of the extended C++ STL).

Re: Parsing JSON in C++

> in C++ I worked with property_trees from BOOST (under the BOOST license): > > https://www.boost.org/doc/libs/1_73_0/doc/html/property_tree.html Two more remarks: 1. LilyPond already seems to use some parts of the BOOST library (which is kind of the extended C++ STL). There should be no license

Fwd: Fine tuning of MetronomeMark's expression

Hello, Please have a look at this thread. It shows that the \tempo markup can't be properly overridden. And it shows an ambiguity of the API. Can the discussed feature be added to Lilypond? IMHO it is an important feature. Thanks, Best P -- Forwarded message - From: Paolo

Re: Parsing JSON in C++

On Sat, Jun 20, 2020 at 11:00 AM Jonas Hahnfeld wrote: > > Am Samstag, den 20.06.2020, 10:52 +0200 schrieb Han-Wen Nienhuys: > > On Sat, Jun 20, 2020 at 1:30 AM Owen Lamb wrote: > > > Hi all, > > > > > > I need to be able to expose the contents of a SMuFL font's JSON metadata > > > file to

Re: Parsing JSON in C++

Am Samstag, den 20.06.2020, 10:52 +0200 schrieb Han-Wen Nienhuys: > On Sat, Jun 20, 2020 at 1:30 AM Owen Lamb wrote: > > Hi all, > > > > I need to be able to expose the contents of a SMuFL font's JSON metadata > > file to LilyPond. From what I can tell, LilyPond currently doesn't have any > >

Re: Parsing JSON in C++

On Sat, Jun 20, 2020 at 1:30 AM Owen Lamb wrote: > > Hi all, > > I need to be able to expose the contents of a SMuFL font's JSON metadata > file to LilyPond. From what I can tell, LilyPond currently doesn't have any > sort of JSON-parsing library in its dependencies, either in Scheme or in > C++.

PATCHES - Countdown for June 20th

Hello, Here is the current patch countdown list. The next countdown will be on June 22nd. A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: !172 MacPorts fixes - Werner Lemberg

Re: Parsing JSON in C++

On 20.06.2020 01:30, Owen Lamb wrote: Hi all, I need to be able to expose the contents of a SMuFL font's JSON metadata file to LilyPond. From what I can tell, LilyPond currently doesn't have any sort of JSON-parsing library in its dependencies, either in Scheme or in C++. An internet search

Re: xdvipdfmx fails with some regtests (“Invalid object”)

Am 19.06.2020 um 18:48 schrieb Jonas Hahnfeld via Discussions on LilyPond development: Am Freitag, den 19.06.2020, 16:31 +0200 schrieb Han-Wen Nienhuys: Thanks; yours is much nicer. Meanwhile, mine is failing for unknown reasons. How does this thing work? make doc => # Making

GSoC 2020 update, June 19

Hi all! Here with another weekly update. This week, I corresponded with Daniel Spreadbury on the W3C Music Notation Community Group public email list and Behdad Esfahbod on the HarfBuzz mailing list, and received some clarifications on how to continue. It looks like we won't need to add OpenType