Re: LilyPond build for windows?
Am Sonntag, den 21.06.2020, 13:35 +0200 schrieb Han-Wen Nienhuys: > On Sun, Jun 21, 2020 at 12:07 PM Jonas Hahnfeld wrote: > > Am Samstag, den 20.06.2020, 20:25 +0200 schrieb Han-Wen Nienhuys: > > > 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 ? > > > > Starting from 2.21.0, GUB uses the embeddable package for Python: > > https://docs.python.org/3.8/using/windows.html#the-embeddable-package > > > > This is official, so no "limitations" from our side. > > awesome. I assume that subprocess works normally on windows, so we can get rid > of the hack in lilylib.py I have no idea. I was satisfied after testing that it worked equally well as before 😉 (not using Windows in production since I-don't-know) Jonas signature.asc Description: This is a digitally signed message part
Re: LilyPond build for windows?
On Sun, Jun 21, 2020 at 12:07 PM Jonas Hahnfeld wrote: > > Am Samstag, den 20.06.2020, 20:25 +0200 schrieb Han-Wen Nienhuys: > > 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 ? > > Starting from 2.21.0, GUB uses the embeddable package for Python: > https://docs.python.org/3.8/using/windows.html#the-embeddable-package > This is official, so no "limitations" from our side. awesome. I assume that subprocess works normally on windows, so we can get rid of the hack in lilylib.py -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen
Re: LilyPond build for windows?
Am Samstag, den 20.06.2020, 20:25 +0200 schrieb Han-Wen Nienhuys: > 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 ? Starting from 2.21.0, GUB uses the embeddable package for Python: https://docs.python.org/3.8/using/windows.html#the-embeddable-package This is official, so no "limitations" from our side. The most severe limitation for Windows is that it's still 32-bit, so it crashes when compiling really large scores. I tried to get it to 64- bit, but Guile 1.8 simply doesn't work and crashes somewhere in the GC. This is no problem with Guile 2.2, see also my thread a few months back about my approach of native builds using few shell scripts. I've verified that this is able to compile larger scores that our official binaries fail on right now. Jonas signature.asc Description: This is a digitally signed message part
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 - http://www.xs4all.nl/~hanwen
