From: Carl Worth <cworth@cworth.org>
To: Rob Browning <rlb@defaultvalue.org>
Subject: Re: [PATCH] Have to configure and build inside the source directory.
In-Reply-To: <87ei7wty6f.fsf@raven.defaultvalue.org>
References: <1294747284-18791-1-git-send-email-thomas@schwinge.name>
	<87bp30n3sc.fsf@yoom.home.cworth.org>
	<87ei7wty6f.fsf@raven.defaultvalue.org>
User-Agent: Notmuch/0.5 (http://notmuchmail.org) Emacs/23.2.1
	(i486-pc-linux-gnu)
Date: Wed, 09 Mar 2011 15:19:53 -0800
Message-ID: <87k4g7lw4m.fsf@yoom.home.cworth.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
Cc: notmuch@notmuchmail.org, Thomas Schwinge <thomas@schwinge.name>
Precedence: list

--=-=-=
Content-Transfer-Encoding: quoted-printable

On Fri, 28 Jan 2011 17:18:16 -0600, Rob Browning <rlb@defaultvalue.org> wro=
te:
> I think the use of GNU make VPATH is fairly common.  For example, I
> believe the autotools build a tree that matches the srcdir structure and
> add Makefiles that contain something like this:
>=20
>   VPATH =3D ../../wherever/notmuch/thisdir
>   ...
>=20
> Of course, given that, the build tree doesn't include any source
> files.

Thanks for the pointer to VPATH. I had some code half-written to use
this sitting around since we last talked about it, and I've just cleaned
it up and pushed it out now.

It turns out that VPATH itself isn't very useful, (since it matches on
targets as well as prerequisites), but the similar "vpath" directive
matches only on prerequisites so it does what we want here.

So non-source-directory builds of notmuch should work now. Along the
lines of:

	git clone git.notmuchmail.org:/git/notmuch
        cd notmuch=20=20=20=20=20=20
	mkdir build
        cd build
        ../configure
        make

Everyone, please feel free to test this and report back if you see any
problems.

We should also fix the "make release" target to exercise this code. Does
anyone know what else a GNU configure script typically does in "make
distcheck". I recall that it untars the built tar file and does a
non-srcdir build of it, (and runs the test suite). Then I think it also
does an install and perhaps checks that no extra files are leftover
after "make clean"? Something like that anyway---and we should probably
do something similar.

=2DCarl

=2D-=20
carl.d.worth@intel.com

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQFNeAsZ6JDdNq8qSWgRAqH1AJ0ZVP3XNgG2x2H8yZxpdHiTCsc2JACgqBDq
auoKMaL0MGBPJV443tjVfuw=
=T8RI
-----END PGP SIGNATURE-----
--=-=-=--