NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Hi Allen, Ward I have a request regarding your new CMake Windows build system, could you add an option to make the build static regarding the Microsoft libraries (MSVCR100D.dll) ? Starting with version 4.3.1, NCO http://nco.sourceforge.net/ uses the HDF5 and netCDF Windows libraries made with your CMake system, and this is causing problems for NCO users, as explained here https://sourceforge.net/projects/nco/forums/forum/9830/topic/8345151 and here https://sourceforge.net/projects/nco/forums/forum/9829/topic/8417103 This is just a matter of changing the compiler flag to /MT(d) http://msdn.microsoft.com/en-us/library/2kzt1wy3.aspx Using a dynamic build is just a bad idea, because of these DLL issues. I have some Windows executables from code I did in the early 90's , that unfortunately I cannot run today, just because I linked them with DLLs, with the DLLs from the Visual Studio from that time, that do not exist anymore (it seems every new version they change the Visual Studio Dlls). Because of this I do not use Dlls, I know that eventually something will go wrong :-) Pedro ------ Pedro Vicente, Earth System Science University of California, Irvine http://www.ess.uci.edu/
netcdfgroup
archives: