[CMake] [netcdfgroup] [Hdf-forum] netCDF 4.3 Release Candidateavailable --- CMake build in Windows

[Michael Jackson]

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" does a try/compile for that #define to determine which libraries should be linked against and possibly included in deployments.

___________________________________________________________
Mike Jackson                    Principal Software Engineer
BlueQuartz Software                            Dayton, Ohio
mike.jackson at bluequartz.net              www.bluequartz.net

On Apr 25, 2013, at 6:54 AM, "Biddiscombe, John A." <biddisco at cscs.ch> wrote:

> 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 problem of detecting debug/release/shared/static and I ended up rewriting the routine inside findhdf5
> Here’s a patch which I think improves the module somewhat. If someone could take a look at the diff and give me some feedback I’d be most grateful
>  
> Thanks
>  
> JB
>  
>  
> <0001-Fix-some-problems-with-FindHDF5-with-windows-shared-.patch>--
> 
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
> 
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake