Dear Karin and Om community,
I’m writing about a problem getting Omlily to compile to PDF directly from OpenMusic. I’d be grateful for any guidance on the correct setup.
Environment:
- Mac with Apple Silicon (M chip), macOS 15.7.3
- LilyPond 2.20.0, installed as the standard .app in /Applications
- OpenMusic with Omlily installed and correctly recognized
What works:
- Compiling Omlily-generated .ly files to PDF manually from the Terminal works fine, using a small wrapper script that calls the binary inside the .app bundle.
What fails:
- Evaluating the OM->LILY box does not produce a PDF. The OM Listener shows that version detection returns “no-version”, and the box errors out with: “End of file while reading stream” from the command ‘bash -l -c lilypond -v’. Only the .ly source is generated.
It looks to me like test-lilypond-bin / find-lilypond-version (in unix-utils.lisp) rely on ‘which lilypond’ in OM’s internal login shell, which doesn’t resolve the binary the same way my interactive Terminal does. Because that check fails, “no-version” is written and compilation never runs.
Things I’ve tried without success:
- Setting the LilyPond path explicitly in the External preferences (pointing to a wrapper outside the .app).
- Symlinking into /usr/local/bin: a link to the .app’s wrapper breaks on a relative path (libexec/lilypond-bin: Not a directory), and a link directly to lilypond-bin produces “warning: not relocating, no 2.20.0/ or current/ found under /usr/local/share/lilypond” and then hangs.
Is there a recommended configuration for the LilyPond .app on Apple Silicon, or a known adjustment for the version-detection step? I’d be happy to share more detail or test anything you suggest.
Thank you very much for developing and sharing Omlily.
Best regards,
Alex Buck