Skip to Content.
Sympa Menu

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

h5part AT

Subject: H5Part development and discussion

List archive

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

Chronological Thread 
  • From: Mark Howison <MHowison AT>
  • To: Achim Gsell <achim AT>
  • Cc: h5part AT
  • Subject: [H5part] Re: notes on changes to the H5hut trunk
  • Date: Tue, 20 Jul 2010 11:21:21 -0700
  • List-archive: <>
  • List-id: H5Part development and discussion <>

Hi Achim,

I created the wrapper h5hutcc in trunk/tools by copying the HDF5
wrapper and modifying it. The source is in and the
./configure script makes a bunch of macro substitutions to create the
h5hutcc script. I've named the libraries

libH5hut.a (h5core)
libH5hutC.a (C bindings)
libH5hutF.a (Fortran bindings)


On Thu, Jul 1, 2010 at 12:43 PM, Achim Gsell <achim AT> 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.
> Achim

Archive powered by MHonArc 2.6.19.

Top of Page