Comment #3 on issue 2418 by gra...@percival-music.ca: Patch: Don't copy
GNUmakefile and *.make from within builddir to builddir
http://code.google.com/p/lilypond/issues/detail?id=2418
Right. I'm stupid because I like to have
~/src/lilypond/
with everything belonging to lilypond in that directory. I have a mental
disability in which I like to sort things in hierarchical order. Why
bother with a ~/src/lilypond/build/ then? so that I can delete it and know
that I'm in a safe, known space. Our build system does *not* guarantee
that with any combination of make clean reallyclean doc-clean dist-clean
oh-god-i-beg-you-clean.
Why do I want everybody else to use a build/ dir (whether it's a
subdirectory of lilypond/ or not) ? because I'm sick of GUB dying due to
an out-of-tree build error (GUB only does out-of-tree builds) due to a
developer only testing their makefile change with in-tree building. GUB
does out-of-tree builds (and in that case, really out-of-tree). The
easiest way to get everybody to build+test their code, while still
supporting my mental deficiency of hierarchical directories, is to have a
build/ dir within the source dir.
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
