Hello Werner, A happy new year 2019, and thumbs up, thanks!
JM > Le 7 janv. 2019 à 08:10, Werner LEMBERG <[email protected]> a écrit : > > > Folks, > > > using gub pull requests > > https://github.com/gperciva/gub/pull/53 > https://github.com/gperciva/gub/pull/54 > > together with > > https://sourceforge.net/p/testlilyissues/issues/5456/ > > allows me to successfully run gub's `make lilypond' on my machine, > including regression tests and documentation! This means that > a lilypond build is no longer bound to a certain architecture, user, > or top-level directory. As soon as issue #5456 is in git master you > can test this :-) > > > Werner > > > PS: If you want to test this immediately, do the following. > > . Apply the patches from the above two pull requests to gub's git > repository. > . Apply https://codereview.appspot.com/349090043 to lilypond's git. > . Move the modified file `output-distance.py' to from lilypond's git > to $HOME. > . Do `git reset --hard' in lilypond's git. > . Apply the attached patch to gub's `lilypond.make': > diff --git a/lilypond.make b/lilypond.make > index 7a3d6333..7f318a36 100644 > --- a/lilypond.make > +++ b/lilypond.make > @@ -290,7 +290,7 @@ unlocked-test-export: > $(SET_TOOLS_PATH) \ > $(PYTHON) test-lily/rsync-test.py \ > --version-file=$(NATIVE_LILY_BUILD)/out/VERSION \ > - > --output-distance=$(NATIVE_LILY_SRC)/$(BUILDSCRIPTS)/output-distance.py \ > + --output-distance=$(HOME)/output-distance.py \ > --test-dir=uploads/webtest \ > --gub-target-dir=$(NATIVE_TARGET_DIR) > > _______________________________________________ > lilypond-devel mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/lilypond-devel _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
