[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 2604 in lilypond: LILYPOND_BUILD_DIR
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 2604 in lilypond: LILYPOND_BUILD_DIR |
Date: |
Mon, 18 Jun 2012 08:06:53 +0000 |
Comment #2 on issue 2604 by address@hidden: LILYPOND_BUILD_DIR
http://code.google.com/p/lilypond/issues/detail?id=2604
Slightly long explanation of what's up here.
GUB always does out-of-tree builds. I got fed up with the GUB build
breaking after 1 hour of 100% 4-CPU use due to people editing the makefiles
in a non-out-of-tree-supported manner, so I started "strongly suggesting"
that people use out-of-tree builds.
(NB: as far as I understand it, "out of tree builds" in automake refers to
any situation in which the top source dir is not the top build dir -- so
a "lilypond-git/build/" dir is called an out-of-tree build, even though
it's actually a subdirectory of the top source dir).
LilyDev and the CG are generally set up to use out-of-tree builds by
default. I haven't heard any complaints about this for months, so I assume
that it's functioning well.
I wouldn't say that it is policy that lilypond must be built in a separate
build dir, but it *is* policy that the build system and CG should *allow*
people to use a separate build dir (whether or not it's a subdir of the
source tree itself). See for example
http://lilypond.org/doc/v2.15/Documentation/contributor/compiling-with-lilydev
which we expect people to copy&paste. also maybe
http://lilypond.org/doc/v2.15/Documentation/contributor/lily_002dgit
for some more background about the LILYPOND_GIT directory.
What's wanted in terms of solving the release-critical problem is:
- somewhere in the CG, tell people that they should define
export LILYPOND_BUILD_DIR=$LILYPOND_GIT/build/
(with a note that advanced users can of course change the directory if they
wish)
- change the script in the minor release checklist to use
make -c BUILD=$LILYPOND_BUILD_DIR
or whatever the appropriate syntax is.
So yeah, something like 3-6 lines of texinfo. Oh yeah, the CG has
instructions for building an ubuntu remix; the $LILYPOND_BUILD should be
listed there in right next to where it defines LILYPOND_GIT and
LILYPOND_MEDIA_GIT. So maybe 5-10 lines of texinfo?
A lower-priority, longer-term thing would be to make scripts like
make-lsr.py use $LILYPOND_BUILD on places like line 62.
- [Lilypond-auto] Issue 2604 in lilypond: LILYPOND_BUILD_DIR, lilypond, 2012/06/14
- Re: [Lilypond-auto] Issue 2604 in lilypond: LILYPOND_BUILD_DIR, lilypond, 2012/06/18
- Re: [Lilypond-auto] Issue 2604 in lilypond: LILYPOND_BUILD_DIR,
lilypond <=
- Re: [Lilypond-auto] Issue 2604 in lilypond: LILYPOND_BUILD_DIR, lilypond, 2012/06/18
- Re: [Lilypond-auto] Issue 2604 in lilypond: LILYPOND_BUILD_DIR, lilypond, 2012/06/18
- Re: [Lilypond-auto] Issue 2604 in lilypond: LILYPOND_BUILD_DIR, lilypond, 2012/06/25
- Re: [Lilypond-auto] Issue 2604 in lilypond: LILYPOND_BUILD_DIR, lilypond, 2012/06/26
- Re: [Lilypond-auto] Issue 2604 in lilypond: LILYPOND_BUILD_DIR, lilypond, 2012/06/27
- Re: [Lilypond-auto] Issue 2604 in lilypond: LILYPOND_BUILD_DIR, lilypond, 2012/06/27
- Re: [Lilypond-auto] Issue 2604 in lilypond: LILYPOND_BUILD_DIR, lilypond, 2012/06/28
- Re: [Lilypond-auto] Issue 2604 in lilypond: LILYPOND_BUILD_DIR, lilypond, 2012/06/28
- Re: [Lilypond-auto] Issue 2604 in lilypond: LILYPOND_BUILD_DIR, lilypond, 2012/06/28
- Re: [Lilypond-auto] Issue 2604 in lilypond: LILYPOND_BUILD_DIR, lilypond, 2012/06/28