It is in the lilpondcairo.py. I fixed this. Do you want me to create new binaries? Also, when we use git as source it has version 0.0.0-0 should we use tarballs with versions set to 1.0.1.year.month.day so that we have version 1.0.1.2013.04.03. This way we dont get confused by users running 0.0.0-0 from two years ago or something. I could do this by creating tarballs or hacking gub.
I have also added support for .xz files and gtk3 (and friends) in gub.
On Apr 1, 2013 5:15 AM, "Richard Shann" <
address@hidden> wrote:
We are shipping an old version of LilyPond with the binaries.
I didn't manage to figure out how to move this on in GUB.
Any ideas?
As it is some newer commands don't work with the shipped version - I
have found that windows users can install the latest LilyPond and point
Denemo to it (via Edit->Change Preferences->Externals lilypond path
field becomes
c:\program files\lilypond\usr\bin\...
instead of
c:\program files\Denemo\usr\bin\...
) and this works ok. But, that is just a workaround...
Richard
_______________________________________________
Denemo-devel mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/denemo-devel