If you wanted to avoid having an external server, you could always use Docker. I’ve been running LP in a Docker container on my mac for a couple of months now, and it’s worked flawlessly.
--Steven
From: lilypond-user <lilypond-user-bounces+address@hidden>
On Behalf Of Austin Blaser
Sent: Tuesday, March 5, 2019 7:20 PM
To: Karlin High <address@hidden>
Cc: Mason Hock <address@hidden>; lilypond-user <address@hidden>; Carl Sorensen <address@hidden>
Subject: Re: LilyPond 64-bit version for a Mac
Regarding the iOS App Store: Oh yeah I forgot about the licensing: definitely a potential deal breaker. One other possibility I’ve thought about is building an iOS app that would have all the text editing capability one would need, but
then send the .ly files to a backend server to typeset with LilyPond and return the PDFs, similar to how
Lilybin.com operates. That way the app itself doesn’t have LilyPond in it and gets around the licensing issue. Would that be of interest? I’ve wanted to use an iPad at the piano for a long time.
Thanks for your input…I’ll keep everyone posted!
I’d like to make an attempt at compiling Llilypond on the Mac.
That sounds like an interesting project. If it turns out to not be very hard, it might influence software distribution choices for LilyPond.
I’m an iOS developer, so I’m also interested to see if we can compile it to run natively for iOS as well. Compiling for OSX is a good first step to getting it running on iOS.
I am thinking LilyPond is GNU GPL software, Apple App Store doesn't accept that license, and the App Store is the only good way to get software onto iOS devices. Are there other possibilities I'm missing?
Who would be the best contact to help with any trouble-shooting for this build?
Probably the lilypond-devel list.
|