lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: PATCHES: Brain surgery on the build system, first stage


From: Phil Holmes
Subject: Re: PATCHES: Brain surgery on the build system, first stage
Date: Sat, 4 Aug 2012 16:44:47 +0100

----- Original Message ----- From: "John Mandereau" <address@hidden>
To: "Phil Holmes" <address@hidden>
Cc: "Lily devel" <address@hidden>
Sent: Saturday, August 04, 2012 2:55 PM
Subject: Re: PATCHES: Brain surgery on the build system, first stage


Hi Phil,
Le samedi 04 août 2012 à 14:02 +0100, Phil Holmes a écrit :
Hi John - is this patch designed to fix problems like:

http://lists.gnu.org/archive/html/lilypond-devel/2011-11/msg00360.html

Yes, exactly; the commit that adresses this issue is among the four top
commits in dev/jmandereau commit
8a0905f1409f3d01bf902312cb53cb8f1127e760
Make distributed tarball from Git file list

You can also test this commit separately (or together with the parent
commit that changes mass-link.py) with the test procedure I gave in my
earlier message, except that you won't have "make vc-clean" available,
but it can be replaced by
make distclean && rm -f configure aclocal.m4


I'd be happy to test once I know what it does a bit better.

Basically, that commit changes how dist target finds files to put in the
tarball, and removes all GNUmakefiles that are made unnecesszary by this
change (i.e. GNUmakefiles that were present only for distributing source
files in the tarball).

Best,
John



The step after I checkout your branch failed with this as the last few lines:

touch ./out/share/lilypond/current/lilypond-force
make --no-builtin-rules out=www clean
make[1]: Entering directory `/media/IntelSSD/lilypond/lilypond-git'
make[1]: *** No rule to make target `clean'.  Stop.
make[1]: Leaving directory `/media/IntelSSD/lilypond/lilypond-git'
make: *** [doc-clean] Error 2


FWIW it also failed on the lines

$LILYPOND_GIT/configure

for reasons I don't understand, but must be something to do with bash. Replacing the variable with the actual path worked.

Let me know if I can give you further information to help you find out what's happening.

--
Phil Holmes



reply via email to

[Prev in Thread] Current Thread [Next in Thread]