Hi Andrew, On Windows, we ship a copy of HDF5 along with the h5py installer, > which is built by the h5py team. It's customized to disable the SZIP > writer for licensing issues, and to rename the DLL to avoid a conflict > with PyTables. Right now that version is built with VS2008 (and on a > WinXP build node, for added irony). I build from the included project > file at the moment but I'm fine with switching to CMake.
You'll have to switch to CMake for the next release since we've dropped the VS projects and solutions for the next release. CMake is actually a much, much better build environment for HDF5. The projects and solutions we'd been including with the source distribution had been deprecated for some time. > > I would assume so, but I don't think we've had a lot of problems with > > VS-specific issues in HDF5. Usually Windows bugs apply to all versions > of > > Visual Studio and Windows. > > If this is the case, may I ask what the motivation is to drop VS2008 > support? Is it to reduce the testing burden? I understand the HDF > Group can't support every old compiler forever, but I would certainly > be willing to chip in with testing, etc. because this is such an > important part of our infrastructure. > > It's mainly a test and build issue. It costs time and resources to build and test on a large number of platforms and we try to keep the load due to Windows small since we receive no funding for Windows development. We do have CDash set up to track testing by external parties. I can put you in touch with Allen if you'd like to investigate that. Cheers, Dana
_______________________________________________ Hdf-forum is for HDF software users discussion. [email protected] http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
