mirror of
https://github.com/HDFGroup/hdf5.git
synced 2025-02-23 16:20:57 +08:00
5b7be284bc
* Do not enable szip for sanitizer runs (#4057) * Add note to H5Tset_fields about needing to set datatype precision first (#4059) * Offset of a floating-point type also needs to be accounted for * Clarify ordering of H5Tset_precision and H5Tset_fields * Fix issue where H5Tset_fields does not account for datatype offsets (#4061) H5Tset_fields did not account for any offset in a floating-point datatype, causing it to fail when a datatype's precision is correctly set such that it doesn't include the offset bits. * Ignore UserPresets and Use only C compiler for sanitizers (#4066) * Remove user presets file * Only use C compiler for sanitzers * Rename incorrectly named option (#4067) * Rename incorrectly named option * Restore the correct uses of USING_MEMCHECKER * Update release note * Fix a memory leak in the cmpd_dset test (#4071) This was due to not freeing a test buffer. It was not a core library memory leak. * Fix uninitialized bytes in cmpd_dset test (#4072) Compound fill values were set to the integer -1, causing valgrind to flag 'uninitialized bytes' errors. This is just a problem with the cmpd_dset test and not a core library problem. * Update INSTALL files (#4052) * Add NEWSLETTER and merge abi reports and add sha256sums (#4055) * Fix uninitialized bytes in selection I/O test (#4073) This was due to a complex type fill value being set to -1 instead of a proper complex value. This was a test problem and not a core library issue. * fix path for S3 build path in CI (#4076) * Correct paths for 1.14 and add lines missing from release_docs/INSTALL_CMake.txt. --------- Co-authored-by: Allen Byrne <50328838+byrnHDF@users.noreply.github.com> Co-authored-by: jhendersonHDF <jhenderson@hdfgroup.org> Co-authored-by: Dana Robinson <43805+derobins@users.noreply.github.com>
100 lines
4.2 KiB
Plaintext
100 lines
4.2 KiB
Plaintext
|
|
***********************************************************************
|
|
* HDF5 Build and Install Suggestions for Windows and Visual Studio *
|
|
* (Full Version) *
|
|
***********************************************************************
|
|
|
|
These suggestions are for Visual Studio users.
|
|
|
|
Instructions for building and testing HDF5 applications using CMake can
|
|
be found in the USING_HDF5_CMake.txt file found in this folder.
|
|
|
|
NOTE: Building applications with the dynamic/shared hdf5 libraries requires
|
|
that the "H5_BUILT_AS_DYNAMIC_LIB" compile definition be used.
|
|
Go to "Project" and select "Properties", find "Configuration Properties",
|
|
and then "C/C++"and then "Preprocessor".
|
|
Add H5_BUILT_AS_DYNAMIC_LIB to Preprocessor definitions.
|
|
|
|
The following two sections are helpful if you do not use CMake to build
|
|
your applications.
|
|
|
|
==============================================================================================
|
|
Using Visual Studio 2010 and above with HDF5 Libraries built with Visual Studio 2010 and above
|
|
==============================================================================================
|
|
|
|
1. Set up path for external libraries and headers
|
|
|
|
The path settings will need to be in the project property sheets per project.
|
|
Go to "Project" and select "Properties", find "Configuration Properties",
|
|
and then "VC++ Directories".
|
|
|
|
1.1 If you are building on 64-bit Windows, find the "Platform" dropdown
|
|
and select "x64".
|
|
|
|
1.2 Add the header path to the "Include Directories" setting.
|
|
|
|
1.3 Add the library path to the "Library Directories" setting.
|
|
|
|
1.4 Select Linker->Input and beginning with the
|
|
"Additional Dependencies" line, enter the library names. The
|
|
external libraries should be listed first, followed by the HDF5
|
|
library, and then optionally the HDF5 High Level, Fortran or C++
|
|
libraries. For example, to compile a C++ application, enter:
|
|
|
|
hdf5.lib hdf5_cpp.lib
|
|
|
|
For static linking:
|
|
HDF5 libraries: libhdf5.lib libhdf5_cpp.lib
|
|
Compression libraries: libszaec.lib libaec.lib libzlib.lib
|
|
System libraries: shlwapi.lib
|
|
|
|
|
|
==========================================================================
|
|
Using Visual Studio 2008 with HDF5 Libraries built with Visual Studio 2008
|
|
==========================================================================
|
|
|
|
2. Set up the path for external libraries and headers
|
|
|
|
Invoke Microsoft Visual Studio and go to "Tools" and select "Options",
|
|
find "Projects", and then "VC++ Directories".
|
|
|
|
2.1 If you are building on 64-bit Windows, find the "Platform" dropdown
|
|
and select "x64".
|
|
|
|
2.2 Find the box "Show directories for", choose "Include files", add the
|
|
header path (i.e. c:\Program Files\HDF_Group\HDF5\1.14.x\include)
|
|
to the included directories.
|
|
|
|
2.3 Find the box "Show directories for", choose "Library files", add the
|
|
library path (i.e. c:\Program Files\HDF_Group\HDF5\1.14.x\lib)
|
|
to the library directories.
|
|
|
|
2.4 If using Fortran libraries, you will also need to setup the path
|
|
for the Intel Fortran compiler.
|
|
|
|
2.5 Select Project->Properties->Linker->Input and beginning with the
|
|
"Additional Dependencies" line, enter the library names. The
|
|
external libraries should be listed first, followed by the HDF5
|
|
library, and then optionally the HDF5 High Level, Fortran or C++
|
|
libraries. For example, to compile a C++ application, enter:
|
|
|
|
hdf5.lib hdf5_cpp.lib
|
|
|
|
For static linking:
|
|
HDF5 libraries: libhdf5.lib libhdf5_cpp.lib
|
|
Compression libraries: libszaec.lib libaec.lib libzlib.lib
|
|
System libraries: shlwapi.lib
|
|
|
|
========================================================================
|
|
3. Helpful Pointers
|
|
========================================================================
|
|
|
|
3.1 FAQ
|
|
|
|
Community support forum available, please see:
|
|
|
|
https://forum.hdfgroup.org/c/hdf5/8
|
|
|
|
************************************************************************
|
|
Please send email to help@hdfgroup.org for further assistance.
|