Re: LilyPond 2.23.9 released
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 build the
x86_64 binaries). What makes this a bit complicated is that I don't
have a management account to do that. LilyPond's entry in MacStadium's
open source program is managed by a person who isn't actively
contributing to (core) LilyPond (not even reading the mailing list
IIRC), and communication via him was kind of slow / painful in the
past...
> 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 actually be comparable.
Jonas
>
> Thanks,
> Ken Wolcott
>
> On Fri, May 20, 2022 at 10:53 AM Jonas Hahnfeld via LilyPond user
> discussion wrote:
> >
> > 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://gitlab.com/lilypond/lilypond/-/releases/v2.23.9
> > We provide packages for macOS ("darwin"), Linux, and Windows ("mingw")
> > that only need to be extracted (no installation as in older versions).
signature.asc
Description: This is a digitally signed message part
Re: Building lilypond on osx
On Sat, 2022-05-21 at 07:49 +0200, Luca Fascione wrote: > As a side question, may I ask: I thought I saw commits pass in > Colin's emails that were indicating GUB and stepmake were being > removed, did I misunderstand what the plan is? Is there a place I can > get myself up to speed on this? (just curious, don't have much of an > opinion one way or the other atm) Since the past few development releases, LilyPond doesn't rely on GUB anymore. This is tightly coupled with the transition to Guile 2, there are plenty of threads on this topic in the mailing list archives. As for StepMake, its removal as a separate package is ongoing since https://gitlab.com/lilypond/lilypond/-/commit/6c323bc1bb27a79f687f5f3f3ed6b105aad24caa This takes some time because the current build system works, so there isn't much incentive to work on this. For the same reason, the macros in aclocal.m4 are still called STEPMAKE_*. signature.asc Description: This is a digitally signed message part
Re: LilyPond 2.23.9 released
>> 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 actually be comparable. 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/ Werner
Re: LilyPond 2.23.9 released
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 that > > Homebrew builds 2.22.2 without Guile bytecode, it might actually be > > comparable. > > 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 Guile 2.2 as Homebrew does, it cannot use Guile bytecode because that is fundamentally not possible with stable/2.22. Please don't spread wrong information. The lilypond-devel port, currently at version 2.23.7, uses Guile 2.2 with bytecode. That *may* be an alternative. signature.asc Description: This is a digitally signed message part
Re: LilyPond 2.23.9 released
>> 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 Guile 2.2 as Homebrew does, it cannot > use Guile bytecode because that is fundamentally not possible with > stable/2.22. Please don't spread wrong information. Oops, you are right, sorry. I was confused. Werner
Re: LilyPond 2.23.9 released
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, don't know much about this, so it is likely that I am
missing something here.
In general, I think it would be a good idea to support Apple Silicon
directly soon, as there will be more requests for it.
Meanwhile, I'll just continue using the homebrew version of Lilypond
(quite satisfied with it, really).
Thanks,
Ken
On Sat, May 21, 2022 at 2:51 AM Jonas Hahnfeld wrote:
>
> 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 build the
> x86_64 binaries). What makes this a bit complicated is that I don't
> have a management account to do that. LilyPond's entry in MacStadium's
> open source program is managed by a person who isn't actively
> contributing to (core) LilyPond (not even reading the mailing list
> IIRC), and communication via him was kind of slow / painful in the
> past...
>
> > 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 actually be comparable.
>
> Jonas
>
> >
> > Thanks,
> > Ken Wolcott
> >
> > On Fri, May 20, 2022 at 10:53 AM Jonas Hahnfeld via LilyPond user
> > discussion wrote:
> > >
> > > 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://gitlab.com/lilypond/lilypond/-/releases/v2.23.9
> > > We provide packages for macOS ("darwin"), Linux, and Windows ("mingw")
> > > that only need to be extracted (no installation as in older versions).
>
Re: LilyPond 2.23.9 released
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 to select a different execution method (such as > Rosetta). No, as far as I understand Rosetta is automatic: Whenever you try to execute a binary that was built for "Intel" Macs (nothing to do with Microsoft), macOS will do the translation on the fly. Can you just try that, ie download the darwin-x86_64 package, extract it and see how it goes? > I, obviously, don't know much about this, so it is likely that I am > missing something here. > > In general, I think it would be a good idea to support Apple Silicon > directly soon, as there will be more requests for it. I agree. Jonas signature.asc Description: This is a digitally signed message part
Re: LilyPond 2.23.9 released
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 works just fine. How do you use LilyPond, on the command line or from an editor such as Frescobaldi? Jonas signature.asc Description: This is a digitally signed message part
Re: LilyPond 2.23.9 released
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 -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 works just fine. How do you use LilyPond, on the command line or > from an editor such as Frescobaldi? > > Jonas
Re: LilyPond 2.23.9 released
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, as for any command line tool. Assuming you extracted the archive into ~/Downloads/, that would be ~/Downloads/lilypond-2.23.9/bin/lilypond . Jonas signature.asc Description: This is a digitally signed message part
Re: LilyPond 2.23.9 released
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; > > > > 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, as for any command line tool. > Assuming you extracted the archive into ~/Downloads/, that would be > ~/Downloads/lilypond-2.23.9/bin/lilypond . > > Jonas
Re: LilyPond 2.23.9 released
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 --help
lilypond-invoke-editor (GNU LilyPond) 2.23.9
Backtrace:
7 (primitive-load "/Users/kwolcott/Downloads/lilypond-2.2…")
In ice-9/eval.scm:
293:34 6 (_ #(#(#) ("./..…" …)))
619:8 5 (_ #(#(#(#(#) #) #) #))
619:8 4 (_ #(#(#(#(#) #) #) #))
159:9 3 (_ #(#(#) #))
182:19 2 (proc #(#(#) #))
142:16 1 (compile-top-call _ (7 . G_) ((5 . "Usage: lilypond-i…")))
In unknown file:
0 (%resolve-variable (7 . G_) #)
ERROR: In procedure %resolve-variable:
Unbound variable: G_
==
I have never used this app, but just thought you would like to know
about my experience.
Everything else seems to work (well, with '--help', anyway :-)
Thanks,
Ken
On Sat, May 21, 2022 at 10:50 AM Kenneth Wolcott
wrote:
>
> 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;
> > >
> > > 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, as for any command line tool.
> > Assuming you extracted the archive into ~/Downloads/, that would be
> > ~/Downloads/lilypond-2.23.9/bin/lilypond .
> >
> > Jonas
Re: LilyPond 2.23.9 released
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 with this:
>
> ==
> ./lilypond-invoke-editor --help
> lilypond-invoke-editor (GNU LilyPond) 2.23.9
> Backtrace:
>7 (primitive-load "/Users/kwolcott/Downloads/lilypond-2.2…")
> In ice-9/eval.scm:
>293:34 6 (_ #(#(#) ("./..…" …)))
> 619:8 5 (_ #(#(#(#(#) #) #) #))
> 619:8 4 (_ #(#(#(#(#) #) #) #))
> 159:9 3 (_ #(#(#) #))
>182:19 2 (proc #(#(#) #))
>142:16 1 (compile-top-call _ (7 . G_) ((5 . "Usage: lilypond-i…")))
> In unknown file:
>0 (%resolve-variable (7 . G_) #)
>
> ERROR: In procedure %resolve-variable:
> Unbound variable: G_
> ==
>
> I have never used this app, but just thought you would like to know
> about my experience.
Thanks for reporting, I actually noticed this problem earlier today
when working on this script. It's been broken with
https://gitlab.com/lilypond/lilypond/-/merge_requests/1229 in 2.23.7.
Cheers
Jonas
signature.asc
Description: This is a digitally signed message part
Point an Click & emacs
Today I found out it's quite easy to get point and click working with emacs as pdf viewer when using the pdf-tools package. 1. Install pdf-tools: https://github.com/politza/pdf-tools It's available as a package in emacs. 2. put this in your .emacs config >>> (defconst lilypond-filename-rx (rx (seq string-start (group (1+ print)) ":" (group (1+ digit)) ":" (group (1+ digit)) ":" (group (1+ digit)) string-end))) (defun lilypond-pdf-links-browse-uri-function (uri) "Check if the link starts with texedit and just reroute to emacs. Otherwise call pdf-links-browse-uri-default." (cl-check-type uri string) (let* ((obj (url-generic-parse-url uri)) (match (string-match lilypond-filename-rx (url-filename obj (unless match (message "Could not match %s" (url-filename obj))) (let* ((filename (match-string 1 (url-filename obj))) (line (string-to-number (match-string 2 (url-filename obj (pos (string-to-number (match-string 3 (url-filename obj (buf (or (find-buffer-visiting filename) (find-file-noselect filename (pop-to-buffer buf) (goto-char (point-min)) (forward-line (1- line)) (forward-char pos (setq pdf-links-browse-uri-function 'lilypond-pdf-links-browse-uri-function) >>> 3. Open a lilypond generated pdf with \PointAndClickOn and click away. The code might need some refining but it does work here quite well. Immanuel -- -- A man must either resolve to point out nothing new or to become a slave to defend it. -- Sir Isaac Newton
Re: Point an Click & emacs
Le 21/05/2022 à 20:56, Immanuel Litzroth a écrit : Today I found out it's quite easy to get point and click working with emacs as pdf viewer when using the pdf-tools package. 1. Install pdf-tools: https://github.com/politza/pdf-tools It's available as a package in emacs. 2. put this in your .emacs config (defconst lilypond-filename-rx (rx (seq string-start (group (1+ print)) ":" (group (1+ digit)) ":" (group (1+ digit)) ":" (group (1+ digit)) string-end))) (defun lilypond-pdf-links-browse-uri-function (uri) "Check if the link starts with texedit and just reroute to emacs. Otherwise call pdf-links-browse-uri-default." (cl-check-type uri string) (let* ((obj (url-generic-parse-url uri)) (match (string-match lilypond-filename-rx (url-filename obj (unless match (message "Could not match %s" (url-filename obj))) (let* ((filename (match-string 1 (url-filename obj))) (line (string-to-number (match-string 2 (url-filename obj (pos (string-to-number (match-string 3 (url-filename obj (buf (or (find-buffer-visiting filename) (find-file-noselect filename (pop-to-buffer buf) (goto-char (point-min)) (forward-line (1- line)) (forward-char pos (setq pdf-links-browse-uri-function 'lilypond-pdf-links-browse-uri-function) 3. Open a lilypond generated pdf with \PointAndClickOn and click away. The code might need some refining but it does work here quite well. Immanuel Hello, What kind of answer to this post do you await? Best, Jean
Re: Point an Click & emacs
Jean, I think this is a BWV1079... L On Sat, May 21, 2022 at 9:28 PM Jean Abou Samra wrote: > > > Le 21/05/2022 à 20:56, Immanuel Litzroth a écrit : > > Today I found out it's quite easy to get point and click working > > with emacs as pdf viewer when using the pdf-tools package. > > 1. Install pdf-tools: https://github.com/politza/pdf-tools > > It's available as a package in emacs. > > > > 2. put this in your .emacs config > > (defconst lilypond-filename-rx > >(rx (seq > > string-start > > (group (1+ print)) > > ":" > > (group (1+ digit)) > > ":" > > (group (1+ digit)) > > ":" > > (group (1+ digit)) > > string-end))) > > > > (defun lilypond-pdf-links-browse-uri-function (uri) > >"Check if the link starts with texedit and just reroute to emacs. > > Otherwise call pdf-links-browse-uri-default." > >(cl-check-type uri string) > >(let* ((obj (url-generic-parse-url uri)) > > (match (string-match lilypond-filename-rx (url-filename obj > > (unless match > >(message "Could not match %s" (url-filename obj))) > > (let* ((filename (match-string 1 (url-filename obj))) > > (line (string-to-number (match-string 2 (url-filename obj > > (pos (string-to-number (match-string 3 (url-filename obj > > (buf (or (find-buffer-visiting filename) > > (find-file-noselect filename > >(pop-to-buffer buf) > >(goto-char (point-min)) > >(forward-line (1- line)) > >(forward-char pos > > > > > > (setq pdf-links-browse-uri-function > 'lilypond-pdf-links-browse-uri-function) > > 3. Open a lilypond generated pdf with \PointAndClickOn and click away. > > > > The code might need some refining but it does work here quite well. > > Immanuel > > > Hello, > > What kind of answer to this post do you await? > > Best, > Jean > > > -- Luca Fascione
