[Top][All Lists]

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

Re: What's with the build directories?

From: David Kastrup
Subject: Re: What's with the build directories?
Date: Mon, 19 Mar 2012 20:25:17 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.94 (gnu/linux)

David Kastrup <address@hidden> writes:

> Julien Rioux <address@hidden> writes:
>> Graham Percival <graham <at>> writes:
>>> On Mon, Mar 19, 2012 at 01:24:54PM +0100, David Kastrup wrote:
>>> > I find that in my patchy runs, I get directories
>>> > /tmp/lilypond-autobuild (my configured build directory)
>>> > and a hierarchy of "build" directories under it, possibly one per tested
>>> > patch (?).
>>> nope, nothing to do with Patchy.
>>> > ls /tmp/lilypond-autobuild/build/build/build/build/
>>> > GNUmakefile  local.make
>>> That's normal.  People were asking why we have nested build dirs
>>> at least two years ago.  *shrug*  Patches appreciated?  I'm not
>>> eager to poke the build system with a sharp stick.
>> So I did a quick search but I'm probably not touching it either.
>> Lines 421, 422 of stepmake/aclocal.m4:
>> for mf in `cd $srcdir ; find . -maxdepth $d -mindepth $d -name
>> GNUmakefile`; do
>>     mkdir -p $(dirname $mf)
>> recursively search for files named GNUmakefile and create a
>> corresponding directory in the build dir. The build dir itself
>> contains a GNUmakefile. This happens at each configure run (which
>> Patchy happens to do at every patch).
> I'll take a look whether I can have it avoid doing that.  Should not be
> too hard.


David Kastrup

reply via email to

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