Hi list,
is it still possible to use GUB to build lilypond stable 2.12.3?
Simply using the release tarball or the stable branch from git does not work
because of autoconf and the spec file.
/mnt/sdb3/workdir/gub-mingw/gub/target/mingw/src/lilypond-git.sv.gnu.org--lilypond.git-stable-2.12/autogen.sh:
line 36: autoconf: unbound variable
Command barfed:
cd
/mnt/sdb3/workdir/gub-mingw/gub/target/mingw/src/lilypond-git.sv.gnu.org--lilypond.git-stable-2.12
&& ./smart-autogen.sh --noconfigure
And just building bin/gub mingw::url-to-stable-tarball does not work, too.
Maybe you can help me?
We @ Denemo can't take the responsibility to release with a unstable 2.13
lilypond win32 binary build from a random and unknown state of Lilyponds git
master branch.
We ran into several problems because of API- and behaviour- changes (for
examples Titles and Author changed from 2.12 -> 2.13 or the placement of
chord-symbols was broken suddenly, spamming all non-chord notes with "NA" above
it and places the chord symbols right into the staff )
Greetings,
Nils
http://www.denemo.org
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
