From: James Amundson <amundson@fnal.gov>
To: Brian Gough <bjg@gnu.org>
Cc: gsl-discuss mailing list <gsl-discuss@sourceware.org>
Subject: Re: Feedback from GSL folks on libflame 4.0
Date: Tue, 23 Feb 2010 17:39:00 -0000 [thread overview]
Message-ID: <4B8412BE.10708@fnal.gov> (raw)
In-Reply-To: <87aav0kit7.wl%bjg@network-theory.co.uk>
On 02/22/2010 04:27 PM, Brian Gough wrote:
> 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.
>
I'm entirely sympathetic with the argument that existing standards are
very valuable and may trump technical advantages in the end. I don't
think the case for autotools being "standard" and cmake being
"non-standard" are so clear, however. Let's look at the other
mathematical libraries I deal with on a regular basis:
1) FFTW
2) LAPACK
3) PETSc ( http://www.mcs.anl.gov/petsc/ )
4) Triinos ( http://trilinos.sandia.gov/ )
What do they use for build systems?
1) autotools
2) Custom makefiles
3) Custom complex build system
4) cmake
No clear winner there. Let's look at some major components of my linux
installation:
1) Linux kernel
2) GNU utilities
3) Gnome
4) KDE
What doe they use for build systems?
1) Custom makefiles
2) autotools
3) autotools
4) cmake
Of course, this isn't a detailed survey. I assume autotools would have
the numerical advantage over all other options if a detailed analysis
was made. The point is, however, that many projects don't use autotools
and that a signficant number use cmake. I don't think the "standard"
argument is strong enough to simply trump any technical argument. Of
course, the technical argument still needs to be made.
If you were to argue that the current level of predominance of autotools
means that autotools is the only acceptable build system for GSL, I
think I could make a similar argument that the current level of
predominance of Fortran in scientific computing means that Fortran is
the only acceptable implementation language for GSL.
--Jim Amundson
next prev parent reply other threads:[~2010-02-23 17:39 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
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 [this message]
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=4B8412BE.10708@fnal.gov \
--to=amundson@fnal.gov \
--cc=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).