On Fri, Jan 10, 2020 at 1:03 AM Werner LEMBERG <w...@gnu.org> wrote: > > > There is one lingering problem: when LilyPond calls Guile, Guile is > > not finding the library files specified in load-extension > > expressions, even though they *should* be in the right place. > > Before I go too crazy searching, does anyone know what controls this > > path choice? I'm assuming it may be a compilation option for the > > LilyPond binary, but I really don't know. > > Here's a link to the script MacPorts is using to call lilypond. > > > https://github.com/macports/macports-ports/blob/master/textproc/lilypond-devel/files/lilypond.in > > It seems you have to set LDTL_LIBRARY_PATH.
I saw that, of course, but I’m not sure what that variable even is. In particular, I have no reason to believe that it affects Guile’s load path...but I’ll try it and see. Thanks for the reminder. I *think* that the Guile load path is the last issue standing between me and a self-contained 64-bit Mac .app bundle. Everything else appears to be working. > > > > Werner > -- Marnen Laibow-Koser mar...@marnen.org http://www.marnen.org Sent from Gmail Mobile
