[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Building Mac OS LilyPond versions automatically (Was : another 'wrong ty
From: |
Jacques Menu |
Subject: |
Building Mac OS LilyPond versions automatically (Was : another 'wrong type argument' error ) |
Date: |
Fri, 14 Oct 2022 08:29:22 +0200 |
Hello folks,
I’m a regular user of Mac OS, which I use for development, and will help with
the creation of LilyPond versions with pleasure.
My last try at building LilyPond from the source code on my Mac Mini M1 failed
due to a library not being ported yet to this architecture, but Jonas told me
that this should come with the current efforts by the developers team.
Hope that helps!
JM
> Le 14 oct. 2022 à 06:30, Werner LEMBERG <wl@gnu.org> a écrit :
>
>
>>> So you checked all of LilyPond's dependencies and can guarantee
>>> that it will stay like this forever?
>>
>> I am on Big Sur (11.6) and I can still choose 10.9 as a deployment
>> target. [...]
>
>>> I'm not going to work on anything. I have been alone trying to get
>>> a build for macOS even though I don't even use Apple hardware and
>>> other core developers do. It will take somebody willing to work on
>>> this effort *and commit to maintaining it* because I don't think
>>> it's a good idea to release something half-working.
>>
>> In the spirit of my first comments in this email I’ll directly ask
>> if the project needs help testing or working on the Mac build system
>> at all?
>
> Yes, we need help – namely for taking *permanent* care of the MacOS
> releases in
>
> https://gitlab.com/lilypond/lilypond/-/releases
>
> that have been built with the scripts in
>
> https://gitlab.com/lilypond/lilypond/-/tree/master/release
>
> With 'permanent' I mean that the automatically created and released
> binaries should be regularly tested on actual Mac hardware to check
> whether they work as expected. Jonas's fear is too real that some day
> deployment support for older OS versions will break out of the blue,
> unfortunately.
>
> As Jonas writes: He isn't a MacOS users, and none of us main
> developers is either. It was a heroic effort of him to set up the
> scripts, but details like handling deployment targets to make this
> work on older MacOS versions needs a dedicated specialist.
>
>
> Werner
- Re: another 'wrong type argument' error, (continued)
- Re: another 'wrong type argument' error, David Wright, 2022/10/13
- Re: another 'wrong type argument' error, David Kastrup, 2022/10/13
- Re: another 'wrong type argument' error, Werner LEMBERG, 2022/10/10
- Re: another 'wrong type argument' error, Jonas Hahnfeld, 2022/10/10
- Re: another 'wrong type argument' error, Werner LEMBERG, 2022/10/10
- Re: another 'wrong type argument' error, Alex Harker, 2022/10/13
- Re: another 'wrong type argument' error, Werner LEMBERG, 2022/10/14
- Building Mac OS LilyPond versions automatically (Was : another 'wrong type argument' error ),
Jacques Menu <=
- Re: Building Mac OS LilyPond versions automatically (Was : another 'wrong type argument' error ), Jonas Hahnfeld, 2022/10/14
- Re: Building Mac OS LilyPond versions automatically (Was : another 'wrong type argument' error ), Jacques Menu, 2022/10/15
- Re: Building Mac OS LilyPond versions automatically (Was : another 'wrong type argument' error ), Jonas Hahnfeld, 2022/10/15
- Re: Building Mac OS LilyPond versions automatically (Was : another 'wrong type argument' error ), Jacques Menu, 2022/10/16
- Re: Building Mac OS LilyPond versions automatically (Was : another 'wrong type argument' error ), Jonas Hahnfeld, 2022/10/16
- Re: another 'wrong type argument' error, Jonas Hahnfeld, 2022/10/14
- Re: another 'wrong type argument' error, Alex Harker, 2022/10/17
- Re: another 'wrong type argument' error, Jean Abou Samra, 2022/10/17
- Re: another 'wrong type argument' error, Jonas Hahnfeld, 2022/10/17
- Re: another 'wrong type argument' error, Karlin High, 2022/10/17