From: Thomas Schwinge <thomas@schwinge.name>
To: Carl Worth <cworth@cworth.org>, notmuch@notmuchmail.org
Subject: Build system (was: [PATCH] Have to configure and build inside the source directory.)
Date: Sun, 30 Jan 2011 11:12:42 +0100 [thread overview]
Message-ID: <87lj22pun9.fsf@kepler.schwinge.homeip.net> (raw)
In-Reply-To: <87bp30n3sc.fsf@yoom.home.cworth.org>
[-- Attachment #1: Type: text/plain, Size: 1040 bytes --]
Hallo!
On Sat, 29 Jan 2011 06:58:59 +1000, Carl Worth <cworth@cworth.org> wrote:
> Rather than documenting a limitation here, why don't we do what people
> actually want.
Well, not a big deal for me -- I'm just used to building projects
containing a configure file outside of the source tree, and the notmuch
build machinery at first accepted this, but then fell over.
> What do other build systems generally do when running configure from
> some other directory?
What Rob said -- but: why re-invent Autoconf / Automake if it's already
there? I totally admit that the GNU Autotools have their ugly corners
(and indeed a lot of these), but on the other hand they do solve some
issues quite nicely.
You surely had reasons to not use these tools, and that's fine with me.
(And I'm not especially interested in working on build systems -- done
that enough in the past.) Have you looked at other tools before going
for the straight-forward (and that is very fine!) Makefile-based
solution?
Grüße,
Thomas
[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2011-01-30 10:13 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
2011-01-30 10:12 ` Thomas Schwinge [this message]
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=87lj22pun9.fsf@kepler.schwinge.homeip.net \
--to=thomas@schwinge.name \
--cc=cworth@cworth.org \
--cc=notmuch@notmuchmail.org \
/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).