pt., 23 lis 2018 o 10:15 Urs Liska <li...@openlilylib.org> napisał(a):
> Am 23.11.18 um 00:08 schrieb Janek Warchoł: > > Whoah, I almost forgot them :p > So, you're still using them? > > Unfortunately not. I really used them because it's so convenient to > maintain multiple builds from different branches or commits. > Why, thanks! > The problem is that on (most modern Linux) systems it is necessary to use > a self-compiled version of Guile (if you're not actively investigating > support for Guile 2), and that of course it's necessary to adjust the > compilation commands. > Ouch. > I think it would be worth updating these scripts, at least the > build-lilypond one (I never used the script to pull in all the dependencies > because I think it makes too many assumptions. Instead it's rather easy to > do that by hand). > True. > For others to comment on the latter suggestion: Janek's build script > provides an interface where you don't build LilyPond from the actual > repository. Instead it makes a lot of sanity checks (providing some > configuration), then clones the development repository to another directory > and starts the build from there. Of course this uses significant disk space > but you have a convenient and clean interface to manage multiple builds in > parallel (you then can register them as independent LilyPond versions in > Frescobaldi, for example). > > I've looked at that script (whoah, I wrote it 5 years ago!) and honestly I think it's overengineered, I would have written it differently now. But perhaps it's better than nothing. _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
