On Tue, Jan 7, 2020 at 5:15 PM Hans Åberg <[email protected]> wrote:
> > > On 7 Jan 2020, at 22:20, Marnen Laibow-Koser <[email protected]> wrote: > > > > On Tue, Jan 7, 2020 at 4:16 PM Hans Åberg <[email protected]> wrote: > > [...] > > > > FYI, it is possible to build apps using MacPorts, for example, there is > emacs-app that installs Emacs.app in /Applications/MacPorts/, and it seems > working if copied out of that directory. > > > > Thanks, I looked for something like that but didn’t see a general > method. Do you have any idea how this is done? > > No. Yeah, neither do I. Time to look at build scripts. > > > Also, of course, the point is to do this in a way that doesn’t require > the end users to have MacPorts. > > The Emacs.app seemed to be working when put in /Applications/ so it might > be distributed independently. Right, unless it contains absolute paths to MacPorts-installed libraries outside the bundle (which would be horrible practice but I think is allowed). > > But Frescobaldi seems a good choice. It needs a lilypond binary. By > suggestions of the FHS standard I and Werner Lemberg decided to put in > /opt/lilypond/bin/lilypond. I plan to use LilyPad like the current Mac distributions do. I agree that Frescobaldi might be a better choice in the long run. Best, -- Marnen Laibow-Koser [email protected] http://www.marnen.org Sent from Gmail Mobile
