lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Lilypond code/feature freeze for 2.12


From: Josh Parmenter
Subject: Re: Lilypond code/feature freeze for 2.12
Date: Sat, 20 Sep 2008 19:16:28 -0700

On Sep 20, 2008, at 6:49 PM, Graham Percival wrote:

On Sat, 20 Sep 2008 20:48:53 -0300
"Han-Wen Nienhuys" <address@hidden> wrote:

I recently fixed the last bug on my todo list (tied completion heads).
This means that we should start thinking about releasing 2.12.

Forgot something: we should probably add warnings in the docs (or the
download page) about the sorry state of OSX.

10.5: broken GUI.  (IIRC)

Pardon me for asking (as I am sure this has been beaten to death already)... but I am new to LilyPond, and am wondering if I could help out here. What needs to be done to get the GUI working on OSX?

I have been through the steps to build lilypond from source and have it working from the command line rather nicely. Is the code that generates the .app bundle available somewhere (is it an XCode project?). If so, how can I get it and start trying to help fix the problems for 10.5? I'd love to chip in.

Best,

Josh


10.4 and 10.3: broken lilypond-book and convert-ly.  The broken
convert-ly is particularly unfortunate given the syntax changes between
2.10 and 2.12.

Cheers,
- Graham


_______________________________________________
lilypond-devel mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/lilypond-devel

******************************************
/* Joshua D. Parmenter
http://www.realizedsound.net/josh/

“Every composer – at all times and in all cases – gives his own interpretation of how modern society is structured: whether actively or passively, consciously or unconsciously, he makes choices in this regard. He may be conservative or he may subject himself to continual renewal; or he may strive for a revolutionary, historical or social palingenesis." - Luigi Nono
*/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]