Op 14 augustus 2018 23:06:54 schreef "Phil Holmes" <address@hidden>:
Please look at:
http://lilypond.org/doc/v2.19/Documentation/contributor/minor-release-checklist
which I follow for "standard" development builds.
I also aim to follow "Subsequent builds" in
http://lilypond.org/doc/v2.19/Documentation/contributor/notes-on-builds-with-gub
Please let me know if this doesn't help.
--
Phil Holmes
That seems pretty complicated. Also, I'm not building 'official' releases,
just a windows-version of Lilypond for my own use. Ideally that build is
based on the most recent master branch. So I guess my question is: does
GUB's command "make lilypond" automatically perform a 'pull' of origin
master? Or do I have to perform that step manually myself before issuing
'make lilypond'?
Auke
----- Original Message -----
From: "Partitura Organum" <address@hidden>
To: "lilypond-user" <address@hidden>
Sent: Tuesday, August 14, 2018 5:07 PM
Subject: Question about GUB and source code update
Hello,
About a month ago I succeeded in getting GUB running and compiling in
VirtualBox on my Windows 10 machine. So I have now a working Windows
version of Lilypond 2.21 from the source code as it was a month ago. What
I'd like to know is: what happens if I run GUB again? Do I then build the
same Lilypond version again? Or does GUB automatically refresh the source
code and is the result a 'newer' Lilypond? I did run it again, but the
version is number is the same, so that's a bit inconclusive.
Regards,
Auke
_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user