lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem let Frescobaldi recognize convert-ly in Lilypond 2.24.0 on m


From: Hans Aikema
Subject: Re: Problem let Frescobaldi recognize convert-ly in Lilypond 2.24.0 on macOS
Date: Sat, 17 Dec 2022 13:59:23 +0100



On 17 Dec 2022, at 12:16, TamuraJun <j.tamura@me.com> wrote:

Hello list,

I’ve been running Lilypond 2.22.2 and Frescobaldi 3.2, both installed with MacPorts, on macOS Monterey 12.6.2. I’ve just download “official” lilypond-2.24.0-darwin-x86_64.tar.gz, unzip/untar it in my home directory, and now I have:

~/lilypond-2.24.0/

Then, in Frescobaldi, I opened Frescobaldi -> Preferences…,
selected LilyPond Preferences,
clicked +Add… for the LilyPond version to use,
specified ~/lilypond-2.24.0/bin/lilypond for LilyPond Command,
and clicked Set as Default to make the 2.24.0 as the default.

By choosing LilyPond -> Engrave, Frescobaldi runs LilyPond 2.24.0, not the older MacPort-installed 2.22.2., and I got anticipated syntax errors as my LilyPond code is written for 2.22.

Then I choose Tools -> Update with convert-ly… but I cannot find LilyPond 2.24.0 in the pull down menu where you expect to choose the desired LilyPond version. I found only "LilyPond 2.22.2 (/opt/local/bin/lilypond)” in the pull down menu.

My understanding is that Frescobaldi would automatically look for convert-ly in the same directory as the LilyPond executable is located (that is ~/lilypond-2.24.0/bin/lilypond) and there certainly exists ~/lilypond-2.24.0/bin/convert-ly.


Am I missing something?

Thanks in advance for your help.




I did a bit of experimentation on my system (after installing the MacPorts edition of Frescobaldi, as I normally code my lilypond sources directly in the editor of a Java IDE)… the crucial part appears to be that for 2.24.0 the “Force use of the tools’ #1 lines” option needs to be checked on the Tool Commands window. After that convert-ly for 2.24.0 started appearing in the dialog for me and could run successfully.
Before that I already manually started each of the tools from Finder to be able to unlock the tools from Mac OS’s Security & Privacy settings, so if just ticking the box doesn’t make It work for you start each of the tools directly from finder, followed by unblocking its execution in the Security & Privacy settings and after that try again.


HTH

Kind regards,
Hans Aikema

reply via email to

[Prev in Thread] Current Thread [Next in Thread]