Hi All. My reason for setting H5_BUILT_AS_DYNAMIC_LIB is based on the fact that 1) h5api_adpt.h uses it as a #ifdef switch to define H5_DLLVAR, 2) AND, the #else branch of this (which references the _HDF5USEDLL_ ifdef) is very clearly marked thus in the comments:
/* This is the original HDFGroup defined preprocessor code which should still work * with the VS projects that are maintained by "The HDF Group" * This will be removed after the next release. */ The statement "this will be removed in the next release" led me to assume that this section of the header is deprecated and should not be used in new code, and hence that the best define to use would be H5_BUILT_AS_DYNAMIC_LIB. Is this interpretation incorrect - will this section of the header continue to exist in future? I don't use CMake, and I'm not building HDF5, just using it from my client code. So what, if any, are the functional consequences to VS2005 projects client code defining H5_BUILT_AS_DYNAMIC_LIB and building against the h, lib binary deliverable - bearing in mind that my application is built, tested, and seems to be working fine....? Steve -- View this message in context: http://hdf-forum.184993.n3.nabble.com/VC-project-Build-Errors-with-HDF5-1-8-5-tp1880934p1888067.html Sent from the hdf-forum mailing list archive at Nabble.com. _______________________________________________ Hdf-forum is for HDF software users discussion. [email protected] http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
