Le 15/05/2021 à 16:21, Jonas Hahnfeld via Discussions on LilyPond
development a écrit :
[Lukas]
So I guess Frescobaldi's way of forcing LilyPond to display English
messages (just force LANG and LC_ALL to C) has unintended side-effects
for pathnames that somehow were partly masked before by some
Am Mittwoch, dem 30.06.2021 um 08:18 +0200 schrieb Jonas Hahnfeld via
Discussions on LilyPond development:
> Hi Petr,
>
> Am Mittwoch, dem 30.06.2021 um 05:11 +0200 schrieb Petr Pařízek:
> > Hi Jonas and others,
> > I wanted to try it out on my Windows computer. What I got was
> > (translating fr
Hi Petr,
Am Mittwoch, dem 30.06.2021 um 05:11 +0200 schrieb Petr Pařízek:
> Hi Jonas and others,
> I wanted to try it out on my Windows computer. What I got was
> (translating from Czech):
> Missing libgio-2.0-0.dll, please try reinstalling the program.
Indeed, that library is missing / not pack
Am Donnerstag, dem 20.05.2021 um 08:26 +0200 schrieb Jonas Hahnfeld via
Discussions on LilyPond development:
> Am Mittwoch, dem 19.05.2021 um 22:54 +0200 schrieb Federico Bruni:
> > On Thu, May 13 2021 at 22:46:58 +0200, Jonas Hahnfeld via Discussions
> > on LilyPond development wrote:
> > > Afte
Am Donnerstag, dem 20.05.2021 um 22:46 +0200 schrieb Federico Bruni:
> On Thu, May 20 2021 at 08:26:18 +0200, Jonas Hahnfeld
> wrote:
> > Yes, I *hope* that it would be straight-forward to produce binaries
> > with the same set of scripts, provided dependencies like Guile and
> > friends don't ch
On Thu, May 20 2021 at 08:26:18 +0200, Jonas Hahnfeld
wrote:
Yes, I *hope* that it would be straight-forward to produce binaries
with the same set of scripts, provided dependencies like Guile and
friends don't choke about the architecture. It clearly needs a native
build host, but it's not obvio
Do Debian package LilyPond for aarch64? If they do, their build
scripts are probably available somewhere.
On Thu, 20 May 2021 at 07:26, Jonas Hahnfeld via Discussions on
LilyPond development wrote:
>
> Am Mittwoch, dem 19.05.2021 um 22:54 +0200 schrieb Federico Bruni:
> > On Thu, May 13 2021 at 2
Am Mittwoch, dem 19.05.2021 um 22:54 +0200 schrieb Federico Bruni:
> On Thu, May 13 2021 at 22:46:58 +0200, Jonas Hahnfeld via Discussions
> on LilyPond development wrote:
> > After some work, I built binaries from the released sources of
> > LilyPond 2.22.1 for
> > * Linux (compiled on CentOS
On Thu, May 13 2021 at 22:46:58 +0200, Jonas Hahnfeld via Discussions
on LilyPond development wrote:
After some work, I built binaries from the released sources of
LilyPond
2.22.1 for
* Linux (compiled on CentOS 7; tested on Arch, CentOS 8, Ubuntu
18.04)
Have you thought about adding more a
Am Sonntag, dem 16.05.2021 um 21:22 +0200 schrieb Jean Abou Samra:
> Today I additionally tested building with this system, too (Ubuntu
> 20.10).
> I had to install lzip, needed to unpack the gmp tarball. Other than
> that, it worked very nicely; I got the final tar archives within an
> hour, w
Le 15/05/2021 à 16:24, Jean Abou Samra a écrit :
Le 13/05/2021 à 22:46, Jonas Hahnfeld via Discussions on LilyPond
development a écrit :
Feel free to give them a try, but please keep in mind the
limitations: Guile 2.2 and no compiled bytecode [1] means startup
will take around 3 seconds.
Am Sonntag, dem 16.05.2021 um 16:56 +0200 schrieb Thomas Morley:
> Am So., 16. Mai 2021 um 13:58 Uhr schrieb Thomas Morley
> :
> > I'll continue testing using this binary for every days work
>
> The following:
>
> \void b-\displayMusic -!
> ->
> (make-music
> 'ArticulationEvent
> 'midi-
Am So., 16. Mai 2021 um 13:58 Uhr schrieb Thomas Morley
:
> I'll continue testing using this binary for every days work
The following:
\void b-\displayMusic -!
->
(make-music
'ArticulationEvent
'midi-extra-velocity
6
'midi-length
#
'articulation-type
"staccatissimo")
is not t
Am So., 16. Mai 2021 um 14:40 Uhr schrieb Jonas Hahnfeld :
>
> Am Sonntag, dem 16.05.2021 um 13:58 +0200 schrieb Thomas Morley:
> > Hi Jonas,
> >
> > many thanks for your hard work!
> >
> > I'm testing with Linux 64-bit after having done GUILE_AUTO_COMPILE=1
> > One thing I stumpled across by accid
Am Sonntag, dem 16.05.2021 um 13:58 +0200 schrieb Thomas Morley:
> Hi Jonas,
>
> many thanks for your hard work!
>
> I'm testing with Linux 64-bit after having done GUILE_AUTO_COMPILE=1
> One thing I stumpled across by accident was:
>
> \version "2.22.1"
>
> \relative c'' {
> bes4^"ऌ"
> }
>
Am Do., 13. Mai 2021 um 22:47 Uhr schrieb Jonas Hahnfeld via
Discussions on LilyPond development :
>
> Before starting: These builds are not official, highly experimental,
> and not meant for "production" installations. They use Guile 2.2 and
> are slower, might not compile all scores or break some
Jonas,
Thanks for these builds.
I have tested the MacOS x86_64 version and have no problems running it on
Catalina from Frescobaldii.
It has worked well with every score I've tried. Of course, my scores are
pretty vanilla, but I do use partcombine a lot.
My system is too old to run Big Sur,
Le 15/05/2021 à 20:11, Jonas Hahnfeld a écrit :
Am Samstag, dem 15.05.2021 um 17:30 +0200 schrieb Jean Abou Samra:
Le 15/05/2021 à 17:02, Jonas Hahnfeld a écrit :
Yes, all 64-bit. For macOS, it's x86_64 only and not arm64 (Apple M1).
I'm optimistic that it should work with the same approach,
Am Samstag, dem 15.05.2021 um 17:30 +0200 schrieb Jean Abou Samra:
> Le 15/05/2021 à 17:02, Jonas Hahnfeld a écrit :
> > Yes, all 64-bit. For macOS, it's x86_64 only and not arm64 (Apple M1).
> > I'm optimistic that it should work with the same approach, but I have
> > to use GitHub Actions because
Le 15/05/2021 à 17:02, Jonas Hahnfeld a écrit :
Am Samstag, dem 15.05.2021 um 16:24 +0200 schrieb Jean Abou Samra:
Le 13/05/2021 à 22:46, Jonas Hahnfeld via Discussions on LilyPond
development a écrit :
Before starting: These builds are not official, highly experimental,
and not meant for
Jonas Hahnfeld via Discussions on LilyPond development
writes:
> Am Samstag, dem 15.05.2021 um 16:24 +0200 schrieb Jean Abou Samra:
>> > After some work, I built binaries from the released sources of
>> > LilyPond 2.22.1 for
>> > * Linux (compiled on CentOS 7; tested on Arch, CentOS 8, Ubuntu
>
Am Samstag, dem 15.05.2021 um 16:24 +0200 schrieb Jean Abou Samra:
> Le 13/05/2021 à 22:46, Jonas Hahnfeld via Discussions on LilyPond
> development a écrit :
>
> > Before starting: These builds are not official, highly experimental,
> > and not meant for "production" installations. They use Guil
Le 13/05/2021 à 22:46, Jonas Hahnfeld via Discussions on LilyPond
development a écrit :
Before starting: These builds are not official, highly experimental,
and not meant for "production" installations. They use Guile 2.2 and
are slower, might not compile all scores or break some advanced
fea
Am Samstag, dem 15.05.2021 um 16:05 +0200 schrieb Lukas-Fabian Moser:
> Hi Jonas,
>
> Am 14.05.21 um 21:59 schrieb Jonas Hahnfeld:
> > Am Freitag, dem 14.05.2021 um 20:35 +0200 schrieb Lukas-Fabian Moser:
> > > I just remembered that I have another encoding problem with LilyPond,
> > > namely spec
Hi Jonas,
Am 14.05.21 um 21:59 schrieb Jonas Hahnfeld:
Am Freitag, dem 14.05.2021 um 20:35 +0200 schrieb Lukas-Fabian Moser:
I just remembered that I have another encoding problem with LilyPond,
namely special characters in \bootOutputSuffix lead to replacement
characters __ in the name of the
Am Freitag, dem 14.05.2021 um 20:35 +0200 schrieb Lukas-Fabian Moser:
> I just remembered that I have another encoding problem with LilyPond,
> namely special characters in \bootOutputSuffix lead to replacement
> characters __ in the name of the generated file. Which means I should
> investigate th
but frankly I'm surprised that plain gcc's char type and printf seem
to be able to deal with multi-byte characters. But this probably has
to do with the fact that this was my first #include "stdio.h" since
(I think) 1998, and the world has moved on...
I don't think "char *" and printf care, they
Am Freitag, dem 14.05.2021 um 19:24 +0200 schrieb Lukas-Fabian Moser:
> Looks like Unicode alright,
I agree (can't properly quote the rest because the plain message is
very unreadable, only the HTML part is fine...)
> but frankly I'm surprised that plain gcc's char type and printf seem
> to be ab
Hi Jonas,
Do you have any suggestion which route I could try to find out?
Not really, other than maybe writing a small C program that dumps the
arguments as binary in hex code?
I did:
#include "stdio.h" void dump_char(char c) { printf("%02hhX(%c)", c, c);
} void dump_string(char *c) { print
Am Freitag, dem 14.05.2021 um 16:26 +0200 schrieb Lukas-Fabian Moser:
> Hi Jonas,
>
> > > Obviously some encoding/unicode problem, but I'm not sure if the
> > > culprit is LilyPond or Frescobaldi?
> > >
> > Umm, so if it works from the command line but not from Frescobaldi, it
> > could be that t
Hi Jonas,
Obviously some encoding/unicode problem, but I'm not sure if the
culprit is LilyPond or Frescobaldi?
Umm, so if it works from the command line but not from Frescobaldi, it
could be that the invocation from there doesn't pass the filename as
UTF-8 and Guile 1.8 works by chance due to
Am Donnerstag, dem 13.05.2021 um 23:49 +0200 schrieb Lukas-Fabian
Moser:
> Hi Jonas,
>
> Am 13.05.21 um 22:46 schrieb Jonas Hahnfeld via Discussions on
> LilyPond development:
>
> > Before starting: These builds are not official, highly
> > experimental, and not meant for "production" installati
Hi Jonas,
Am 13.05.21 um 22:46 schrieb Jonas Hahnfeld via Discussions on LilyPond
development:
Before starting: These builds are not official, highly experimental,
and not meant for "production" installations. They use Guile 2.2 and
are slower, might not compile all scores or break some advance
Before starting: These builds are not official, highly experimental,
and not meant for "production" installations. They use Guile 2.2 and
are slower, might not compile all scores or break some advanced feature
that you might use. The binaries might eat your files or do other bad
things to your comp
34 matches
Mail list logo
