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! > On Mar 5, 2019, at 7:46 PM, Karlin High <karlinh...@gmail.com> wrote: > > On Tue, Mar 5, 2019, 8:02 PM Austin Blaser <austin.bla...@icloud.com > <mailto:austin.bla...@icloud.com>> wrote: > 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.
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
