From: Jed Brown <jed@59A2.org>
To: Jeffrey Ollie <jeff@ocjtech.us>,
Bart Trojanowski <bart@jukie.net>,
Not Much Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH] Add SCons build files.
Date: Sun, 22 Nov 2009 18:21:28 +0100 [thread overview]
Message-ID: <87r5rqmq5j.fsf@kunyang.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <935ead450911220800r47284335n301a2b2432638c72@mail.gmail.com>
On Sun, 22 Nov 2009 10:00:26 -0600, Jeffrey Ollie <jeff@ocjtech.us> wrote:
> Yes, I'm sure that make is widely available, but as notmuch gets used
> on a wider variety of systems some sort of configuration system will
> become necessary. If I can prevent another project from going down
> the autoconf/automake path I'll be happy. I started creating CMake
> build files but I don't know CMake well enough to come up with a
> working build.
I can do a CMake build if that's desirable. While I prefer it to SCons,
particularly when config/build times are an issue and you want to have
several active build trees, it is a significantly heavier dependency.
With SCons, you can dump scons-local (a pure Python script) into the
source tree and then users only need Python. There are lots of other
lightweight build tools.
Jed
next prev parent reply other threads:[~2009-11-22 17:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-22 13:47 [PATCH] Add SCons build files Jeffrey C. Ollie
2009-11-22 14:15 ` Bart Trojanowski
2009-11-22 16:00 ` Jeffrey Ollie
2009-11-22 17:21 ` Jed Brown [this message]
2009-11-22 20:02 ` Jeffrey Ollie
2009-11-22 20:36 ` Bart Trojanowski
2009-11-22 20:43 ` Ingmar Vanhassel
2009-11-23 3:11 ` Carl Worth
2009-11-23 4:36 ` Jeffrey Ollie
2009-11-23 6:20 ` 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=87r5rqmq5j.fsf@kunyang.i-did-not-set--mail-host-address--so-tickle-me \
--to=jed@59a2.org \
--cc=bart@jukie.net \
--cc=jeff@ocjtech.us \
--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).