+1 the bootstrapping issue is 50% of the reason I will never use CMake for any production code.
vygr:~ hjelmn$ type -p cmake
Nada, zilch, nothing on standard OS X install. I do not want to put an extra requirement on my users. Nor do I want something as simple-minded as CMake. autotools works great for me.
From: users [users-bounces_at_[hidden]] on behalf of Ralph Castain [rhc_at_[hidden]]
Sent: Friday, May 16, 2014 2:07 PM
To: Open MPI Users
Subject: Re: [OMPI users] Question about scheduler support
On May 16, 2014, at 1:03 PM, Fabricio Cannini <fcannini_at_[hidden]<mailto:fcannini_at_[hidden]>> wrote:
Em 16-05-2014 10:06, Jeff Squyres (jsquyres) escreveu:
On May 15, 2014, at 8:00 PM, Fabricio Cannini <fcannini_at_[hidden]<mailto:fcannini_at_[hidden]>>
Nobody is disagreeing that one could find a way to make CMake
work - all we are saying is that (a) CMake has issues too, just
like autotools, and (b) we have yet to see a compelling reason to
undertake the transition...which would have to be a *very*
I was simply agreeing with Maxime about why it could work. ;)
But if you and the other devels are fine with it, i'm fine too.
FWIW, simply for my own curiosity's sake, if someone could confirm
deny whether cmake:
1. Supports the following compiler suites: GNU (that's a given, I
assume), Clang, OS X native (which is variants of GNU and Clang),
Absoft, PGI, Intel, Cray, HP-UX, Oracle Solaris (Linux and Solaris),
Tru64, Microsoft Visual, IBM BlueGene (I think that's gcc, but am
not entirely sure). (some of these matter mainly to hwloc, not
Not 100% confirmed, but this is good evidence that cmake does indeed supports all these suites. See the file list:
2. Bootstrap a tarball such that an end user does not need to have
What do you mean by 'bootstrapping a tarball' ?
If someone doesn't have cmake installed and downloads a tarball that was built from a CMake-based project, can they configure/build that tarball? Or do they have to install cmake first?
users mailing list