H5Part development and discussion

[John Biddiscombe <biddisco AT cscs.ch>]

> I agree with Achim; configure make is the way to go!
I wouldn't remove any of the autoconf files, just add one CMakeLists.txt 
file per directory. This gives me the ability to run my tests on a 
nightly basis, submit results to the dashboard, and use packaging of 
source/binaries from cmake. Mostly it just integrates the H5Part build 
with all the other modules like paraview etc which use CMake - it also 
makes it possible for other users who use CMake to simply add an 
INCLUDE(Use_H5Part.cmake) to their cmake scripts and away they go. Not 
putting CMake support in will probably force me to maintain my own copy 
locally and is just a pain really.

I don't agree that autoconf XOR cmake is right. They can coexist quite 
happily.

I volunteer to do what is required to maintain the CMake side of things.

JB

--
John Biddiscombe,                            email:biddisco @ cscs.ch
http://www.cscs.ch/about/BJohn.php
CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
Via Cantonale, 6928 Manno, Switzerland      | Fax:  +41 (91) 610.82.82