Edit file

File name : INSTALL_CMake.txt

Content :************************************************************************* * Build and Install HDF4 C, C++, Fortran Libraries and tools with CMake * ************************************************************************* Table of Contents Section I: Preconditions Section II: Quick Step Building HDF4 Libraries with CMake Script Mode Section III: Quick Step Building HDF4 Libraries with CMake Command Mode Section IV: Further considerations Section V: Options for building HDF4 Libraries with CMake command line Section VI: CMake option defaults for HDF4 Section VII: User Defined Options for HDF4 Libraries with CMake ************************************************************************ ======================================================================== I. Preconditions ======================================================================== Obtaining HDF4 source code 1. Create a directory for your development; for example, "myhdfstuff". 2. Obtain compressed (*.tar or *.zip) HDF4 source from https://portal.hdfgroup.org/display/support/Building+HDF4+with+CMake and put it in "myhdfstuff". Uncompress the file. There should be a hdf-4.2."X" folder. CMake version 1. We suggest you obtain the latest CMake from the Kitware web site. The HDF 4.2."X" product requires a minimum CMake version 3.10, where "X" is the current HDF4 release version. Note: To change the install prefix from the platform defaults initialize the CMake variable, CMAKE_INSTALL_PREFIX. Users of build scripts will use the INSTALLDIR option. ======================================================================== II. Quick Step Building HDF4 Libraries with CMake Script Mode ======================================================================== This short set of instructions is written for users who want to quickly build the HDF4 C, C++, and Fortran shared libraries and tools from the HDF4 source code package using the CMake tools. This procedure will use the default settings in the config/cmake/cacheinit.cmake file. HDF Group recommends using the ctest script mode to build HDF4. The following files referenced below are available at the HDF web site: https://portal.hdfgroup.org/display/support/Building+HDF4+with+CMake Single compressed file with all the files needed, including source: CMake-hdf-4.2.X.zip or CMake-hdf-4.2.X.tar.gz CMake build script: CTestScript.cmake External compression szip and zlib libraries: JPEG8b.tar.gz SZip.tar.gz ZLib.tar.gz Examples Source package: HDF4Examples-3.x-Source.tar.gz Configuration files: HDF4config.cmake HDF4options.cmake Build scripts for windows or linux ----------------------------------------------- To build HDF4 with the SZIP, ZLIB and JPEG external libraries you will need to: 1. Change to the development directory "myhdfstuff". 2. Download the CMake-hdf-2.4.X.zip(.tar.gz) file to "myhdfstuff". Uncompress the file. 3. Change to the source directory "hdf-2.4.x". CTestScript.cmake file should not be modified. 4. Edit the platform configuration file, HDF4options.cmake, if you want to change the default build environment. (See https://portal.hdfgroup.org/display/support/How+to+Change+HDF4+CMake+Build+Options) 5. From the "myhdfstuff" directory execute the CTest Script with the following options: On 32-bit Windows with Visual Studio 2017, execute: ctest -S HDF4config.cmake,BUILD_GENERATOR=VS2017 -C Release -VV -O hdf4.log On 64-bit Windows with Visual Studio 2017, execute: ctest -S HDF4config.cmake,BUILD_GENERATOR=VS201764 -C Release -VV -O hdf4.log On 32-bit Windows with Visual Studio 2015, execute: ctest -S HDF4config.cmake,BUILD_GENERATOR=VS2015 -C Release -VV -O hdf4.log On 64-bit Windows with Visual Studio 2015, execute: ctest -S HDF4config.cmake,BUILD_GENERATOR=VS201564 -C Release -VV -O hdf4.log On Linux and Mac, execute: ctest -S HDF4config.cmake,BUILD_GENERATOR=Unix -C Release -VV -O hdf4.log The supplied build scripts are versions of the above. The command above will configure, build, test, and create an install package in the myhdfstuff folder. It will have the format: HDF-4.2.NN-<platform>.<zip or tar.gz> On Unix, <platform> will be "Linux". A similar .sh file will also be created. On Windows, <platform> will be "win64" or "win32". If you have an installer on your system, you will also see a similar file that ends in either .exe (NSIS) or .msi (WiX). Notes on the command line options. The -S option uses the script version of ctest. The value for the -C option (as shown above, "-C Release") must match the setting for CTEST_CONFIGURATION_TYPE in the platform configuration file. The -VV option is for most verbose; use -V for less verbose. The "-O hdf4.log" option saves the output to a log file hdf4.log. 6. To install, "X" is the current release version On Windows, execute: HDF-4.2."X"-win32.exe or HDF-4.2."X"-win64.exe By default this program will install the hdf4 library into the "C:\Program Files" directory and will create the following directory structure: HDF_Group --HDF ----4.2."X" ------bin ------include ------lib ------cmake On Linux, change to the install destination directory (create it if doesn't exist) and execute: <path-to>/myhdfstuff/HDF-4.2."X"-Linux.sh After accepting the license, the script will prompt: By default the HDF4 will be installed in: "<current directory>/HDF-4.2."X"-Linux" Do you want to include the subdirectory HDF-4.2."X"-Linux? Saying no will install in: "<current directory>" [Yn]: Note that the script will create the following directory structure relative to the install point: HDF_Group --HDF ----4.2."X" ------bin ------include ------lib ------share On Mac you will find HDF-4.2."X"-Darwin.dmg in the myhdfstuff folder. Click on the dmg file to proceed with installation. After accepting the license, there will be a folder with the following structure: HDF_Group --HDF ----4.2."X" ------bin ------include ------lib ------share By default the installation will create the bin, include, lib and cmake folders in the <install destination directory>/HDF_Group/HDF/4.2."X" The <install destination directory> depends on the build platform; Windows will set the default to: C:/Program Files/HDF_Group/HDF/4.2."X" Linux will set the default to: "myhdfstuff/HDF_Group/HDF/4.2."X" The default can be changed by adding ",INSTALLDIR=<my new dir>" to the "ctest -S HDF4config.cmake..." command. For example on linux: ctest -S HDF4config.cmake,INSTALLDIR=/usr/local/myhdf4,BUILD_GENERATOR=Unix -C Release -VV -O hdf4.log ======================================================================== III. Quick Step Building HDF4 C Static Libraries and Tools with CMake ======================================================================== Notes: This short set of instructions is written for users who want to quickly build just the HDF4 C static library and tools from the HDF4 source code package using the CMake command line tools. Avoid the use of drive letters in paths on Windows. Go through these steps: 1. Change to the development directory "myhdfstuff". 2. Uncompress the HDF4 source file 3. Create a folder "build" in the "myhdfstuff" directory. 4. Change into the "build" folder. 5. Configure the C library, tools and tests with one of the following commands: On Windows 32 bit cmake -G "Visual Studio 12 2013" -DCMAKE_BUILD_TYPE:STRING=Release -DBUILD_TESTING:BOOL=ON -DHDF4_BUILD_TOOLS:BOOL=ON ..\hdf-4.2."X" On Windows 64 bit cmake -G "Visual Studio 12 2013 Win64" -DCMAKE_BUILD_TYPE:STRING=Release -DBUILD_TESTING:BOOL=ON -DHDF4_BUILD_TOOLS:BOOL=ON ..\hdf-4.2."X" On Linux and Mac cmake -G "Unix Makefiles" -DCMAKE_BUILD_TYPE:STRING=Release -DBUILD_TESTING:BOOL=ON -DHDF4_BUILD_TOOLS:BOOL=ON ../hdf-4.2."X" where "X" is the current release version. 6. Build the C library, tools and tests with this command: cmake --build . --config Release 7. Test the C library and tools with this command: ctest . -C Release 8. Create an install image with this command: cpack -C Release CPackConfig.cmake 9. To install On Windows (with WiX installed), execute: HDF-4.2."X"-win32.msi or HDF-4.2."X"-win64.msi By default this program will install the hdf4 library into the "C:\Program Files" directory and will create the following directory structure: HDF_Group --HDF ----4.2."X" ------bin ------include ------lib ------cmake On Linux, change to the install destination directory (create if doesn't exist) and execute: <path-to>/myhdfstuff/build/HDF-4.2."X"-Linux.sh After accepting the license, the script will prompt: By default the HDF4 will be installed in: "<current directory>/HDF-4.2."X"-Linux" Do you want to include the subdirectory HDF-4.2."X"-Linux? Saying no will install in: "<current directory>" [Yn]: Note that the script will create the following directory structure relative to the install point: HDF_Group --HDF ----4.2."X" ------bin ------include ------lib ------share On Mac you will find HDF-4.2."X"-Darwin.dmg in the build folder. Click on the dmg file to proceed with installation. After accepting the license, there will be a folder with the following structure: HDF_Group --HDF ----4.2."X" ------bin ------include ------lib ------share ======================================================================== IV. Further considerations ======================================================================== 1. We suggest you obtain the latest CMake for windows from the Kitware web site. The HDF 4.2."X" product requires a minimum CMake version 3.10. 2. HDF4 requires Zlib and JPEG. Szip is optional: A. Download the binary packages and install them in a central location. For example on Windows, create a folder extlibs and install the packages there. Add the following CMake options: -DJPEG_LIBRARY:FILEPATH=some_location/lib/jpeg.lib -DJPEG_INCLUDE_DIR:PATH=some_location/include -DZLIB_LIBRARY:FILEPATH=some_location/lib/zlib.lib -DZLIB_INCLUDE_DIR:PATH=some_location/include -DSZIP_LIBRARY:FILEPATH=some_location/lib/szlib.lib -DSZIP_INCLUDE_DIR:PATH=some_location/include where "some_location" is the full path to the extlibs folder. Note that you can use either JPEG 6b or 8b. B. Use source packages from an GIT server by adding the following CMake options: HDF4_ALLOW_EXTERNAL_SUPPORT:STRING="GIT" JPEG_GIT_URL:STRING="https://some_location/jpeg" ZLIB_GIT_URL:STRING="https://some_location/zlib" SZIP_GIT_URL:STRING="https://some_location/szip" where "some_location" is the URL to the GIT repository. Also set CMAKE_BUILD_TYPE to the configuration type. C. Use source packages from a compressed file by adding the following CMake options: HDF4_ALLOW_EXTERNAL_SUPPORT:STRING="TGZ" JPEG_TGZ_NAME:STRING="jpeg_src.ext" ZLIB_TGZ_NAME:STRING="zlib_src.ext" SZIP_TGZ_NAME:STRING="szip_src.ext" TGZPATH:STRING="some_location" where "some_location" is the URL or full path to the compressed file and ext is the type of compression file. Also set CMAKE_BUILD_TYPE to the configuration type during configuration 3. If you are building on Apple Darwin platforms, you should add the following options: Compiler choice - use xcode by setting the ENV variables of CC and CXX Shared fortran is not supported, build static: BUILD_SHARED_LIBS:BOOL=OFF Additional options: CMAKE_ANSI_CFLAGS:STRING=-fPIC CTEST_USE_LAUNCHERS:BOOL=ON CMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=OFF 4. Windows developers should install NSIS or WiX to create an install image with CPack. Visual Studio Express users will not be able to package HDF4 into an install image executable. 5. Developers can copy the config/cmake/cacheinit.cmake file and alter the the settings for the developers' environment. Then the only options needed on the command line are those options that are different. Example using HDF default cache file: cmake -C ../config/cmake/cacheinit.cmake -G "Visual Studio 12 2013" \ -DHDF4_ENABLE_SZIP_SUPPORT:BOOL=OFF -DHDF4_ENABLE_EXAMPLES:BOOL=OFF \ -DCMAKE_BUILD_TYPE:STRING=Release .. Notes: CMake and HDF4 1. Using CMake for building and using HDF4 is under active development. While we have attempted to provide error-free files, please understand that development with CMake has not been extensively tested outside of HDF. The CMake specific files may change before the next release. 2. CMake support for HDF4 development should be usable on any system where CMake is supported. Please send us any comments on how CMake support can be improved on any system. Visit the KitWare site for more information about CMake. 3. Build and test results can be submitted to our CDash server: The CDash server for community submissions of hdf is at https://cdash.hdfgroup.org. Submitters are requested to register their name and contact info and maintain their test sites. After your first submission, login and go to your "My CDash" link and claim your site. We ask that all submissions include the configuration information and contact information in the CTest Notes Files upload step. See the current reports on CDash for examples. Please follow the convention that "NIGHTLY" submissions maintain the same configuration every time. "EXPERIMENTAL" submissions can be expected to be different for each submission. 4. See the appendix at the bottom of this file for examples of using a ctest script for building and testing. Using a ctest script is preferred because of its flexibility. Notes: CMake in General 1. More information about using CMake can be found at the KitWare site at www.cmake.org. 2. CMake uses the command line; however, the visual CMake tool is available for the configuration step. The steps are similar for all the operating systems supported by CMake. ======================================================================== V. Options for Building HDF4 Libraries with the CMake Command Line ======================================================================== To build the HDF4 Libraries with CMake, go through these five steps: 1. Run CMake 2. Configure the cache settings 3. Build HDF4 4. Test HDF4 5. Package HDF4 (create install image) These five steps are described in detail below. ======================================================================== 1. Run CMake The visual CMake executable is named "cmake-gui.exe" on Windows and should be available in your Start menu. For Linux, UNIX, and Mac users the executable is named "cmake-gui" and can be found where CMake was installed. Specify the source and build directories. ***** Make the build and source directories different. ****** For example on Windows, if the source is at c:\MyHDFstuff\hdf4, then use c:\MyHDFstuff\hdf4\build or c:\MyHDFstuff\build\hdf4 as the build directory. RECOMMENDED: Users can perform the configuration step without using the visual cmake-gui program. We use the file cacheinit.cmake in the config/cmake source folder for our testing. This file enables all of the basic options and we turn specific options on or off for testing using the following command line within the build directory: cmake -C <sourcepath>/config/cmake/cacheinit.cmake -G "<generator>" [-D<options>] <sourcepath> Where <generator> is * MinGW Makefiles * NMake Makefiles * Unix Makefiles * Visual Studio 11 2012 * Visual Studio 11 2012 Win64 * Visual Studio 12 2013 * Visual Studio 12 2013 Win64 * Visual Studio 14 2015 * Visual Studio 14 2015 Win64 <options> is: * SZIP_INCLUDE_DIR:PATH=<path to szip includes directory> * SZIP_LIBRARY:FILEPATH=<path to szip/library file> * ZLIB_INCLUDE_DIR:PATH=<path to zlib includes directory> * ZLIB_LIBRARY:FILEPATH=<path to zlib/library file> * JPEG_INCLUDE_DIR:PATH=<path to jpeg includes directory> * JPEG_LIBRARY:FILEPATH=<path to jpeg/library file> * <HDF4OPTION>:BOOL=[ON | OFF] <cacheinit.cmake> is: # This is the CMakeCache file. ######################## # EXTERNAL cache entries ######################## set (BUILD_SHARED_LIBS ON CACHE BOOL "Build Shared Libraries" FORCE) set (BUILD_TESTING ON CACHE BOOL "Build HDF4 Unit Testing" FORCE) set (HDF4_BUILD_EXAMPLES ON CACHE BOOL "Build HDF4 Library Examples" FORCE) set (HDF4_BUILD_FORTRAN ON CACHE BOOL "Build FORTRAN support" FORCE) set (HDF4_BUILD_TOOLS ON CACHE BOOL "Build HDF4 Tools" FORCE) set (HDF4_BUILD_UTILS ON CACHE BOOL "Build HDF4 Library Utilities" FORCE) set (HDF4_ENABLE_NETCDF ON CACHE BOOL "Build HDF4 versions of NetCDF-3 APIS" FORCE) set (HDF4_BUILD_XDR_LIB OFF CACHE BOOL "Build HDF4 XDR Library" FORCE) set (HDF4_ENABLE_JPEG_LIB_SUPPORT ON CACHE BOOL "Enable Jpeg library" FORCE) set (HDF4_ENABLE_Z_LIB_SUPPORT ON CACHE BOOL "Enable Zlib Filters" FORCE) set (HDF4_ENABLE_SZIP_SUPPORT ON CACHE BOOL "Use SZip Filter" FORCE) set (HDF4_ENABLE_SZIP_ENCODING ON CACHE BOOL "Use SZip Encoding" FORCE) set (HDF4_ENABLE_COVERAGE OFF CACHE BOOL "Enable code coverage for Libraries and Programs" FORCE) set (HDF4_DISABLE_COMPILER_WARNINGS OFF CACHE BOOL "Disable compiler warnings" FORCE) set (HDF4_PACKAGE_EXTLIBS OFF CACHE BOOL "(WINDOWS)CPACK - include external libraries" FORCE) set (HDF4_NO_PACKAGES OFF CACHE BOOL "CPACK - Disable packaging" FORCE) set (HDF4_ALLOW_EXTERNAL_SUPPORT "NO" CACHE STRING "Allow External Library Building (NO GIT TGZ)" FORCE) set_property (CACHE HDF4_ALLOW_EXTERNAL_SUPPORT PROPERTY STRINGS NO GIT TGZ) set (ZLIB_TGZ_NAME "ZLib.tar.gz" CACHE STRING "Use ZLib from compressed file" FORCE) set (SZIP_TGZ_NAME "SZip.tar.gz" CACHE STRING "Use SZip from compressed file" FORCE) set (JPEG_TGZ_NAME "JPEG8b.tar.gz" CACHE STRING "Use JPEG from compressed file" FORCE) set (ZLIB_PACKAGE_NAME "zlib" CACHE STRING "Name of ZLIB package" FORCE) set (SZIP_PACKAGE_NAME "szip" CACHE STRING "Name of SZIP package" FORCE) set (JPEG_PACKAGE_NAME "jpeg" CACHE STRING "Name of JPEG package" FORCE) 2. Configure the cache settings 2.1 Visual CMake users, click the Configure button. If this is the first time you are running cmake-gui in this directory, you will be prompted for the generator you wish to use (for example on Windows, Visual Studio 12). CMake will read in the CMakeLists.txt files from the source directory and display options for the HDF4 project. After the first configure you can adjust the cache settings and/or specify the locations of other programs. Any conflicts or new values will be highlighted by the configure process in red. Once you are happy with all the settings and there are no more values in red, click the Generate button to produce the appropriate build files. On Windows, if you are using a Visual Studio generator, the solution and project files will be created in the build folder. On linux, if you are using the Unix Makefiles generator, the Makefiles will be created in the build folder. 2.2 Preferred command line example on Windows in c:\MyHDFstuff\hdf4\build directory: cmake -C ../config/cmake/cacheinit.cmake -G "Visual Studio 12 2013" \ -DHDF4_ENABLE_SZIP_SUPPORT:BOOL=OFF -DHDF4_ENABLE_Z_LIB_SUPPORT:BOOL=OFF \ -DCMAKE_BUILD_TYPE:STRING=Release .. 2.3 On Windows, if you are using a Visual Studio Express version you must be sure that the following two options are correctly set/unset: HDF4_NO_PACKAGES:BOOL=ON HDF4_USE_FOLDERS:BOOL=OFF 3. Build HDF4 On Windows, you can build HDF4 using either the Visual Studio Environment or the command line. The command line can be used on all platforms; Windows, linux, Unix, and Mac. To build from the command line, navigate to your build directory and execute the following: cmake --build . --config {Debug | Release} NOTE: "--config {Debug | Release}" may be optional on your platform. We recommend choosing either Debug or Release on Windows. 3.1 If you wish to use the Visual Studio environment, open the solution file in your build directory. Be sure to select either Debug or Release and build the solution. 3.2.1 The external libraries (zlib, szip, and jpeg) can be configured to allow building the libraries by downloading from an SVN repository. The option is 'HDF4_ALLOW_EXTERNAL_SUPPORT'; by adding the following configuration option: -DHDF4_ALLOW_EXTERNAL_SUPPORT:STRING="GIT" The options to control the GIT URL (config/cmake/cacheinit.cmake file) are: JPEG_GIT_URL:STRING="https://${git_url}/jpeg8b" ZLIB_GIT_URL:STRING="https://${git_url}/zlib" SZIP_GIT_URL:STRING="https://${git_url}/szip" ${git_url} should be changed to your location. Also define CMAKE_BUILD_TYPE to be the configuration type. 3.2.2 Or the external libraries (zlib, Szip, and jpeg) can be configured to allow building the libraries by using a compressed file. The option is 'HDF4_ALLOW_EXTERNAL_SUPPORT' and is enabled by adding the following configuration option: -DHDF4_ALLOW_EXTERNAL_SUPPORT:STRING="TGZ" The options to control the SVN URL (config/cmake/cacheinit.cmake file) are: JPEG_TGZ_NAME:STRING="jpeg_src.ext" ZLIB_TGZ_NAME:STRING="zlib_src.ext" SZIP_TGZ_NAME:STRING="szip_src.ext" TGZPATH:STRING="some_location" where "some_location/xxxx_src.ext" is the URL or full path to the compressed file and where ext is the type of the compression file such as .bz2, .tar, .tar.gz, .tgz, or .zip. Also define CMAKE_BUILD_TYPE to be the configuration type. 4. Test HDF4 To test the build, navigate to your build directory and execute: ctest . -C {Debug | Release} NOTE: "-C {Debug | Release}" may be optional on your platform. We recommend choosing either Debug or Release to match the build step on Windows. 5. Packaging HDF4 (create an install image) To package the build into a simple installer using WiX toolset or the NullSoft installer NSIS on Windows, or into compressed files (.tar.gz, .sh, .zip), use the CPack tool. To package the build, navigate to your build directory and execute; cpack -C {Debug | Release} CPackConfig.cmake NOTE: See note 8 of this document for NSIS information. See note 9 of this document for WiX information. Also, if you are using a Visual Studio Express version or want to disable the packaging components, set HDF4_NO_PACKAGES to ON (on the command line add -DHDF4_NO_PACKAGES:BOOL=ON) 6. The files that support building HDF4 with CMake are all the files in the config/cmake folder, the CMakeLists.txt files in each source folder, and CTestConfig.cmake. CTestConfig.cmake is specific to the internal testing performed by The HDF Group. It should be altered for the user's installation and needs. The cacheinit.cmake file settings are used by The HDF Group for daily testing. It should be altered/ignored for the user's installation and needs. 7. More information about using CMake can be found at the KitWare site, www.cmake.org. 8. Nullsoft Scriptable Install System The Nullsoft Scriptable Install System (NSIS) is an open source installation system. It was created by the WinAmp authors to distribute that application, but it is now a general-purpose system which anyone might use. NSIS installers recognize /S for silent installation and /D=dir to specify the "output directory", which is where the program will be installed. These options are case-sensitive, so be sure to type them in upper case. 9. WiX Toolset WiX--the Windows Installer XML toolset--lets developers create installers for Windows Installer, the Windows installation engine. See http://wixtoolset.org. ======================================================================== VI. CMake Option Defaults for HDF4 ======================================================================== In the options listed below, there are three columns of information: Option Name, Option Description, and Option Default. The config/cmake/cacheinit.cmake file can override the following values. ---------------- General Build Options --------------------- BUILD_SHARED_LIBS "Build Shared Libraries" OFF BUILD_TESTING "Build HDF4 Unit Testing" OFF ---------------- HDF4 Build Options --------------------- HDF4_BUILD_EXAMPLES "Build HDF4 Library Examples" OFF HDF4_BUILD_FORTRAN "Build FORTRAN support" ON HDF4_BUILD_TOOLS "Build HDF4 Tools" OFF HDF4_BUILD_UTILS "Build HDF4 Utilities" OFF HDF4_BUILD_XDR_LIB "Build HDF4 XDR Library" OFF HDF4_ENABLE_NETCDF "Build HDF4 versions of NetCDF-3 APIS" ON ---------------- HDF4 Advanced Options --------------------- HDF4_DISABLE_COMPILER_WARNINGS "Disable compiler warnings" OFF HDF4_ENABLE_COVERAGE "Enable code coverage for Libraries and Programs" OFF HDF4_ENABLE_DEPRECATED_SYMBOLS "Enable deprecated public API symbols" ON HDF4_ENABLE_LARGE_FILE "Enable support for large (64-bit) files on Linux." ON HDF4_NO_PACKAGES "Do not include CPack Packaging" OFF HDF4_PACKAGE_EXTLIBS "CPACK - include external libraries" OFF HDF4_USE_FOLDERS "Enable folder grouping of projects in IDEs." OFF if (APPLE) HDF4_BUILD_WITH_INSTALL_NAME "Build with library install_name set to the installation path" OFF if (WIN32) HDF_LEGACY_NAMING "Use Legacy Names for Libraries and Programs" OFF ---------------- External Library Options --------------------- HDF4_ALLOW_EXTERNAL_SUPPORT "Allow External Library Building" "NO" HDF4_ENABLE_JPEG_LIB_SUPPORT "Enable libjpeg" ON HDF4_ENABLE_SZIP_SUPPORT "Use SZip Filter" OFF HDF4_ENABLE_Z_LIB_SUPPORT "Enable Zlib Filters" ON JPEG_USE_EXTERNAL "Use External Library Building for JPEG" 0 SZIP_USE_EXTERNAL "Use External Library Building for SZIP" 0 ZLIB_USE_EXTERNAL "Use External Library Building for ZLIB" 0 if (HDF4_ENABLE_SZIP_SUPPORT) HDF4_ENABLE_SZIP_ENCODING "Use SZip Encoding" OFF ======================================================================== VII. User Defined Options for HDF4 Libraries with CMake ======================================================================== Support for User Defined macros and options has been added. The file UserMacros.cmake has an example of the technique. In the folder, config/cmake/UserMacros, is an implementation for Windows Visual Studio users for linking libraries to the static CRT - Windows_MT.cmake. Copy the contents of the file, both macro and option, into the UserMacros.cmake file. Then enable the option to the CMake configuration, build and test process. ======================================================================== For further assistance, send email to help@hdfgroup.org ========================================================================

Save