mirror/hdf5
2
0
Fork 0
mirror of https://github.com/HDFGroup/hdf5.git synced 2025-03-31 17:10:47 +08:00
Code Issues Packages Projects Releases Wiki Activity

HDFFV-10508 clarify library differences

Browse Source
This commit is contained in:
Allen Byrne 2018-07-31 09:41:11 -05:00
parent b8945eac22
commit 2822921c23
1 changed files with 8 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
release_docs/RELEASE.txt
View File

@ -522,7 +522,9 @@ COPYING and RELEASE.txt file in the root folder, CMake places them in
the share folder.
The bin folder contains the tools and the build scripts. Additionally, CMake
creates dynamic versions of the tools with the suffix "-shared".
creates dynamic versions of the tools with the suffix "-shared". Autotools
installs one set of tools depending on the "--enable-shared" configuration
option.
build scripts
-------------
Autotools: h5c++, h5cc, h5fc
@ -531,15 +533,15 @@ creates dynamic versions of the tools with the suffix "-shared".
The include folder holds the header files and the fortran mod files. CMake
places the fortran mod files into separate shared and static subfolders,
while Autotools places one set of mod files into the include folder. Because
Cmake produces a tools library, the header files for tools will appear in
CMake produces a tools library, the header files for tools will appear in
the include folder.
The lib folder contains the library files, and CMake adds the pkgconfig
subfolder with the hdf5*.pc files used by the bin/build scripts created by
the CMake build. In addition, because CMake creates the tools
library and the C-stub libraries for the Fortran libraries, these libraries
are present only for CMake builds. The names of the szip libraries are different
between the build systems.
the CMake build. CMake separates the C interface code from the fortran code by
creating C-stub libraries for each Fortran library. In addition, only CMake
creates the tools library and are present only for CMake builds. The names
of the szip libraries are different between the build systems.
The share folder will have the most differences because CMake builds include
a number of CMake specific files for support of CMake's find_package and support