On Sat, 2022-05-21 at 11:04 -0700, Kenneth Wolcott wrote:
> Hi Jonas;
>
> As an aside, I tried executing all of the items in the bin directory
> with '--help' to see if they would execute ok.
>
> After getting past all of the mac malware warnings about guile,
> shell, python, etc; I end up wi
Hi Jonas;
As an aside, I tried executing all of the items in the bin directory
with '--help' to see if they would execute ok.
After getting past all of the mac malware warnings about guile,
shell, python, etc; I end up with this:
==
./lilypond-invoke-editor -
Hi Jonas;
The 'gs' executable could not be verified as safe from malware.
I was able to get the mac to accept 'gs' as safe.
It now works.
Thanks,
Ken
On Sat, May 21, 2022 at 10:31 AM Jonas Hahnfeld wrote:
>
> On Sat, 2022-05-21 at 10:29 -0700, Kenneth Wolcott wrote:
> > Hi Jonas;
> >
>
On Sat, 2022-05-21 at 10:29 -0700, Kenneth Wolcott wrote:
> Hi Jonas;
>
> I use lilypond from the command line.
>
> How do I invoke the 2.23.9 lilypond executable from the command
> line instead of using the mouse to context (right-click) from the
> Finder?
You just use the full path to it,
Hi Jonas;
I use lilypond from the command line.
How do I invoke the 2.23.9 lilypond executable from the command
line instead of using the mouse to context (right-click) from the
Finder?
Thanks,
Ken
Ken
On Sat, May 21, 2022 at 10:18 AM Jonas Hahnfeld wrote:
>
> On Sat, 2022-05-21 at 10:15
On Sat, 2022-05-21 at 10:15 -0700, Kenneth Wolcott wrote:
> Hi Jonas;
>
> When trying to execute the lilypond file under bin in the extracted
> tarball, I get the following [see attached screenshot] (looks like
> usage).
Yes, this is what you get when running lilypond without arguments. So
it w
On Sat, 2022-05-21 at 09:03 -0700, Kenneth Wolcott wrote:
> Hi Jonas;
>
> I think that the Rosetta tool only works for x86-64 binaries that
> were built for Micro$oft.
>
> When I try the method as outlined at
> https://www.imore.com/how-identify-intel-based-apps-m1-mac
> I don't see any way
Hi Jonas;
I think that the Rosetta tool only works for x86-64 binaries that
were built for Micro$oft.
When I try the method as outlined at
https://www.imore.com/how-identify-intel-based-apps-m1-mac
I don't see any way to select a different execution method (such as Rosetta).
I, obviously
>> Note that the MacPorts port of LilyPond 2.22.2 already uses Guile
>> 2.2 bytecode and provides a binary for Apple Silicon, too.
>>
>> https://ports.macports.org/port/lilypond/details/
>
> No, the 2.22.2 version uses Guile 1.8 as can be easily seen from the
> dependencies. Even if it used G
On Sat, 2022-05-21 at 11:45 +, Werner LEMBERG wrote:
> > > Currently homebrew provides Lilypond 2.22.2 for Apple Silicon,
> > > that is what I am using.
> >
> > Did you try running the x86_64 binaries via Apple's Rosetta tool?
> > That might be a bit slower than native executables, but given
>> Currently homebrew provides Lilypond 2.22.2 for Apple Silicon,
>> that is what I am using.
>
> Did you try running the x86_64 binaries via Apple's Rosetta tool? That
> might be a bit slower than native executables, but given that Homebrew
> builds 2.22.2 without Guile bytecode, it might actu
Hi Ken,
On Fri, 2022-05-20 at 11:12 -0700, Kenneth Wolcott wrote:
> Hi Jonas;
>
> This is cool.
>
> Question: Will there be support in the future for Apple Silicon?
Possibly. We'd need to ask MacStadium for a second node with Apple
Silicon (they're already sponsoring the node that I use to
Hi Jonas;
This is cool.
Question: Will there be support in the future for Apple Silicon?
Currently homebrew provides Lilypond 2.22.2 for Apple Silicon, that
is what I am using.
Thanks,
Ken Wolcott
On Fri, May 20, 2022 at 10:53 AM Jonas Hahnfeld via LilyPond user
discussion wrote:
>
> We
We are happy to announce the release of LilyPond 2.23.9. This is termed
a development release, but these are usually reliable. However, if you
require stability, we recommend using version 2.22.2, the current
stable release.
As a reminder, the official binaries can be downloaded from GitLab:
https
14 matches
Mail list logo
