Skip to Content.
Sympa Menu

h5part - Re: [H5part] Re: notes on changes to the H5hut trunk

h5part AT

Subject: H5Part development and discussion

List archive

Re: [H5part] Re: notes on changes to the H5hut trunk

Chronological Thread 
  • From: Andreas Adelmann <andreas.adelmann AT>
  • To: h5part AT
  • Subject: Re: [H5part] Re: notes on changes to the H5hut trunk
  • Date: Fri, 02 Jul 2010 10:58:23 +0200
  • List-archive: <>
  • List-id: H5Part development and discussion <>

On 01.07.10 21:43, Achim Gsell wrote:
Hi Mark,

On Jul 1, 2010, at 7:40 PM, Mark Howison wrote:

Ok, I understand the issue better now, and it seems to be one of
convention. The three examples you give that I am familiar with (hdf5,
mpich, openmpi) all feature compiler wrappers as part of the library
(h5cc, mpicc, etc.) and these reduce the complexity of compilation and
linking for the user. Since ease-of-use is one of the primary design
considerations for H5hut, I would argue that we either need to use a
single library with all language bindings, or we can use separate
libraries only if we also provide a set of compiler wrappers. This is
the type of linker call I want to avoid:

mpicc -L(paths...) -lH5hutC -lH5hutcore -lhdf5 -lz -lm -o ...

and replace with a wrapper as simple as:

h5hcc -o ...

or with a single library:

h5cc -L(paths...) -lH5hut -o ...

Actually, the wrapper is looking like a good option now (and also
agrees with the conventions for the hdf5/mpi libraries that we are
building on top of).
The wrapper is a good idea! The wrapper is pretty simple and we don't have to
rewrite/change and the's.

H5Part mailing list
H5Part AT
ok that sounds good to me too :-)

Dr. sc. math. Andreas (Andy) Adelmann
Staff Scientist
Paul Scherrer Institut WBGB/132 CH-5232 Villigen PSI
Phone Office: xx41 56 310 42 33 Fax: xx41 56 310 50 90
Phone Home: xx41 62 891 91 44
Wednesday: ETH CAB H ??.? xx41 44 632 ?? ??
The more exotic, the more abstract the knowledge,
the more profound will be its consequences."
Leon Lederman

Archive powered by MHonArc 2.6.19.

Top of Page