From: Rob Browning <rlb@defaultvalue.org>
To: Carl Worth <cworth@cworth.org>
Cc: notmuch@notmuchmail.org, Thomas Schwinge <thomas@schwinge.name>
Subject: Re: [PATCH] Have to configure and build inside the source directory.
Date: Fri, 28 Jan 2011 17:18:16 -0600 [thread overview]
Message-ID: <87ei7wty6f.fsf@raven.defaultvalue.org> (raw)
In-Reply-To: <87bp30n3sc.fsf@yoom.home.cworth.org> (Carl Worth's message of "Sat, 29 Jan 2011 06:58:59 +1000")
Carl Worth <cworth@cworth.org> writes:
> What do other build systems generally do when running configure from
> some other directory? Copy/link the Makefiles and then construct them
> carefully such that they can find all the source files?
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.
FWIW
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
next prev parent reply other threads:[~2011-01-28 23:18 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 [this message]
2011-03-09 23:19 ` Carl Worth
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=87ei7wty6f.fsf@raven.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=cworth@cworth.org \
--cc=notmuch@notmuchmail.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).