You tell the difference between debug & release by the naming of the library
itself. All the debug libraries have a "_D" in them or some such thing like
that.
For the Static/Dynamic there is a #define in one of the HDF5 headers (if built
with CMake) that says how it was built. My own "FindHDF5"
Just to follow up my earlier mail,
>
HDF5_C_LIBRARY C:/Program Files/HDF5/bin/hdf5_D.dll
Instead of
HDF5_C_LIBRARY C:/Program Files/HDF5/bin/hdf5_D.lib
<
Should have read
HDF5_C_LIBRARY C:/Program Files/HDF5/lib/hdf5_D.lib
To fix the problem a bit more obustly.
Trying to fix that left me with a pr
Ward
<
Currently, using find_package(HDF5 NO_MODULE) results in Visual Studio
attempting to link against the shared libraries (.dll) themselves, instead of
the associated import libraries (.lib). I'm still trying to figure out why
this is, exactly, but in the mean time I am using the work-arou
