On Wed, 10 Dec 2014 14:30:41 +1000 Vince Boros <v.bo...@uq.edu.au> wrote:
> On Mon, 8 Dec 2014 17:51:03 +0100 (CET) Jan Engelhardt <jeng...@inai.de>
> wrote:
> > The sensible way is to statically resolve $(top_srcdir) with the real
> > (relative) path of the source file, that is,
> >
> > foo_SOURCES = foo.c lib/bar.c lib/bar.h lib/nothere.c
> >
> > Depending on where your particular Makefile.am is located, it may even
> > be ../lib/nothere.c or ../../lib/nothere.c, and so on.
> >
> >
>
> During out-of-tree builds I have found that replacing $(top_srcdir)/
> with the real path (../ in my case) results in build files being created
> above the build directory rather than below it whenever subdir-objects
> is enabled. In my view Automake ought to place all build files under
> the build directory whenever one builds outside of the source tree.
>
The placement of build files above the top build directory by Automake
1.14 with subdir-objects turned on during out-of-tree builds can be
traced to the source configuration files being placed one directory
below the top source directory. I don't think that Automake can be
expected to track this sort of discrepancy between build-tree and
source-tree structures. One should either invoke 'configure' from one
directory below the top build directory or move the source configuration
files into the top source directory (which will allow Automake to place
build files in the top build directory rather than above it). My
mistake. Jan is correct.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
