From: Carl Worth <cworth@cworth.org>
To: Rob Browning <rlb@defaultvalue.org>
Cc: notmuch@notmuchmail.org, Thomas Schwinge <thomas@schwinge.name>
Subject: Re: [PATCH] Have to configure and build inside the source directory.
Date: Wed, 09 Mar 2011 15:19:53 -0800 [thread overview]
Message-ID: <87k4g7lw4m.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <87ei7wty6f.fsf@raven.defaultvalue.org>
[-- Attachment #1: Type: text/plain, Size: 1598 bytes --]
On Fri, 28 Jan 2011 17:18:16 -0600, Rob Browning <rlb@defaultvalue.org> wrote:
> 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:
>
> VPATH = ../../wherever/notmuch/thisdir
> ...
>
> 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
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.
-Carl
--
carl.d.worth@intel.com
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2011-03-09 23:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 12:01 [PATCH] Have to configure and build inside the source directory Thomas Schwinge
2011-01-12 17:58 ` Michal Sojka
2011-01-28 20:58 ` Carl Worth
2011-01-28 23:18 ` Rob Browning
2011-03-09 23:19 ` Carl Worth [this message]
2011-01-30 10:12 ` Build system (was: [PATCH] Have to configure and build inside the source directory.) Thomas Schwinge
2011-01-30 10:28 ` Build system Thomas Schwinge
2011-01-30 11:14 ` Carl Worth
2011-02-08 8:55 ` Thomas Schwinge
2011-02-08 21:13 ` Michal Sojka
2011-03-10 19:38 ` Carl Worth
2011-03-10 19:36 ` Carl Worth
2011-03-10 23:42 ` Rob Browning
2011-03-11 4:02 ` Carl Worth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k4g7lw4m.fsf@yoom.home.cworth.org \
--to=cworth@cworth.org \
--cc=notmuch@notmuchmail.org \
--cc=rlb@defaultvalue.org \
--cc=thomas@schwinge.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).