Closed GoogleCodeExporter closed 9 years ago
I then generate a ruby file from the xml produced above using the
ffi-swig-generator
project.
In the produced ruby I get signatures like:
attach_function :H5Sget_simple_extent_dims, [ :int, a().hsize_t, a().hsize_t ],
:int
attach_function :H5Screate_simple, [ :int, a().q(const).hsize_t,
a().q(const).hsize_t
], :int
I am a little lost for an explanation for the methods:
a().q(const).hsize_t
a().hsize_t
Is the source of these methods the permafrost project?
Original comment by hedgehog...@gmail.com
on 22 Jun 2009 at 9:49
It seems the issue is with the ruby-ffi library. This addresses comment #1.
The patch is still required.
Original comment by hedgehog...@gmail.com
on 22 Jun 2009 at 9:36
A number of custom Swig typemaps are needed to move data in and out of the
libjhdf
native code. Currently the typemap code only supports Java as a target
language.
Supporting multiple languages is a goal for the future. However, generating a
complete mapping of the C HDF API is not a small task: there are literally
several
hundred functions and scores of data types. All of these must be mapped,
documented
and tested. I simply do not have the resources to do two language mappings at
once.
If you are interested in starting work on a branch for another language, please
contact me through gmail.
Original comment by solomon....@gmail.com
on 17 Jul 2009 at 11:54
Sorry about the noise - after bumping around I worked out I could get quite far
by
swig + ruby's ff-swig-generator project by haveing swig produc xmloutput from
the raw
hdf headers.
Ironically less was more in this case - really just piggy backing off Ruby's
swig
generator project.
Best wishes
HH
Original comment by hedgehog...@gmail.com
on 17 Jul 2009 at 1:51
Original issue reported on code.google.com by
hedgehog...@gmail.com
on 22 Jun 2009 at 9:41Attachments: