On Sun, 22 Nov 2009 22:36:30 -0600, Jeffrey Ollie wrote:
> Well, to me, part of the appeal of SCons is that it doesn't generate
> Makefiles.This article is a little old, but the first three
> sections are a pretty good rundown on the limitations of Make.
>
>
On Sun, 22 Nov 2009 07:47:10 -0600, "Jeffrey C. Ollie"
wrote:
> The SCons build files included here *should* do everything that the
> current Makefiles do, plus a little bit of configuration checking. To
> build/install:
Hi Jeffrey,
Thanks for your effort to code all this up.
But I'm afraid
On Sun, Nov 22, 2009 at 9:11 PM, Carl Worth wrote:
>
> But I'm afraid I really don't want to switch away from just using (GNU)
> make for the actual compilation.
>
> I don't know anything about scons, but if you can use it to write a
> python script that just does the configuration step,
Personally I'd say we have better things to work on than maintaining
multiple buildsystems for notmuch. Or than resolving possible packaging
bugs originating in the use of different buildsystems.
GNU has a very wide install bas, it's has a low footprint, and it
happened to be the choice of the
On Sun, 22 Nov 2009 10:00:26 -0600, Jeffrey Ollie 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
My bad. I totally misread your introduction.
* Jeffrey Ollie [091122 11:46]:
> The SCons build files are not meant to require emacs. If I've messed
> something up and emacs is somehow required I would consider that a bug
> and would try to fix it.
>
> As far as availability, I'm sure that
The SCons build files are not meant to require emacs. If I've messed
something up and emacs is somehow required I would consider that a bug
and would try to fix it.
As far as availability, I'm sure that SCons is one yum or apt-get or
away. The only
people that would face more than a minor
* Jeffrey C. Ollie [091122 08:47]:
> The SCons build files included here *should* do everything that the
> current Makefiles do, plus a little bit of configuration checking. To
> build/install:
Wouldn't that have the unfortunate side effect of making notmuch
unusable w/o emacs and scons
The SCons build files included here *should* do everything that the
current Makefiles do, plus a little bit of configuration checking. To
build/install:
scons all emacs
sudo scons install
sudo scons install-emacs
sudo scons install-desktop
Various installation directories can be customized:
