Hi Michael,
I'm not too familiar with git, last time I tried to install it under msys it
turned out to become messy, so I'm somewhat reluctant to go through this again.
Would you be able to test the SVN patch that I just sent to the list?
Werner
On Wed, 10 Mar 2010 15:00:42 -0500, Michael Jackson
<[email protected]> wrote:
Not sure what you have as far as hardware for testing goes, but if you
use the Git repository at www.gitorious.com/hdf5 then I can test any
changes on OS X intel and Windows 7 x64. Just FYI.
Basically sign up for an account and clone the repository. We can then
pull from your clone to test out changes.
___________________________________________________________
Mike Jackson www.bluequartz.net
Principal Software Engineer [email protected]
BlueQuartz Software Dayton, Ohio
On Mar 10, 2010, at 2:54 PM, Peter Cao wrote:
Werner,
You made a very good suggestion. It is actual in our long-term plan
to make
a set of public tools functions and also to make our current tools
more modular.
Because of other priority, we do not have much resource to commit to
the work.
However, we are working toward to this goal.
As for making some of the current function to be public and build as
dll, you
are welcome to try. If there is no other issue (technical and non-
technical),
we will be happy to include your contribution.
Thanks
--pc
Werner Benger wrote:
This might be a bit too internal for the forum, but maybe still of
interest
for more:
The HDF5 tools (h5dump, h5ls, ...) share common code via the tools
library.
This is currently built as a static library and linked into the
main executables.
It appears it would not be a big effort to modify it to be shared
library/DLL
instead. There are two symbols that from the library are references
as "external"
and are supposed to be defined in the main application. These would
need to go
into the library itself instead to be able to build it as shared
library. Not
a big deal.
If we can have the tools library available through header files and
DLL for
user code as well, it has two advantages: once the executables are
a bit
smaller (which is not really important these days), but secondly
one could
also easier write user-modified versions of h5ls/h5dump etc., for
instance
versions that use another VFD, or output data differently on dump
etc.
As a DLL under windows, only addition required in the code were some
symbol export definitions. I'd be volunteering to contribute such.
Is there interest in such a patch?
Werner
_______________________________________________
Hdf-forum is for HDF software users discussion.
[email protected]
http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
_______________________________________________
Hdf-forum is for HDF software users discussion.
[email protected]
http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
--
___________________________________________________________________________
Dr. Werner Benger Visualization Research
Laboratory for Creative Arts and Technology (LCAT)
Center for Computation & Technology at Louisiana State University (CCT/LSU)
211 Johnston Hall, Baton Rouge, Louisiana 70803
Tel.: +1 225 578 4809 Fax.: +1 225 578-5362
_______________________________________________
Hdf-forum is for HDF software users discussion.
[email protected]
http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
