From: Brian Gough <bjg@gnu.org>
To: gsl-discuss mailing list <gsl-discuss@sourceware.org>
Subject: Re: Feedback from GSL folks on libflame 4.0
Date: Mon, 22 Feb 2010 23:09:00 -0000 [thread overview]
Message-ID: <87aav0kit7.wl%bjg@network-theory.co.uk> (raw)
In-Reply-To: <1266613086.27033.124.camel@manticore.lanl.gov>
At Fri, 19 Feb 2010 13:58:06 -0700,
Gerard Jungman wrote:
>
> On Fri, 2010-02-19 at 13:41 -0500, Robert G. Brown wrote:
> > On Fri, 19 Feb 2010, Brian Gough wrote:
> > >
> > > Thanks for using autoconf. I think it is a good thing.
> >
> > Yeah, I don't really think of them as optional these days. They are far
> > from perfect and often a PITA, but what they do is necessary.
>
> You guys are missing the point. The question is not
> "autotools or nothing" but "autotools or cmake".
As Robert says, it's a question of standardisation. I have nothing
against cmake, on a purely techical level it may be better but
autotools is the defacto standard and that is worth more in practice.
next prev parent reply other threads:[~2010-02-22 23:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4a00655d1002171047t4e87fb85w88b609245e3f9a8e@mail.gmail.com>
2010-02-19 8:48 ` Field G. Van Zee
2010-02-18 19:51 ` Rhys Ulerich
2010-02-19 0:20 ` Gerard Jungman
2010-02-19 20:22 ` Brian Gough
2010-02-19 0:00 ` Gerard Jungman
2010-02-20 4:30 ` Field G. Van Zee
2010-02-23 13:13 ` Brian Gough
2010-02-24 1:42 ` Gerard Jungman
2010-02-19 18:19 ` Brian Gough
2010-02-19 18:41 ` Robert G. Brown
2010-02-19 20:57 ` Gerard Jungman
2010-02-19 21:46 ` Robert G. Brown
2010-02-19 22:34 ` Gerard Jungman
2010-02-22 23:09 ` Brian Gough [this message]
2010-02-23 10:50 ` Theodore Papadopoulo
2010-02-23 14:55 ` Robert G. Brown
2010-02-24 1:50 ` Gerard Jungman
2010-02-24 11:31 ` Robert G. Brown
2010-02-23 17:39 ` James Amundson
2010-02-19 20:07 ` Brian Gough
2010-02-19 20:54 ` Gerard Jungman
2010-02-20 4:31 ` Field G. Van Zee
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87aav0kit7.wl%bjg@network-theory.co.uk \
--to=bjg@gnu.org \
--cc=gsl-discuss@sourceware.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.
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).