************************************************************************ * Build and Install HDF Java Library with CMake * ************************************************************************ Table of Contents Section I: Preconditions Section II: Quick Step Building HDF Java Libraries with CMake Script Mode Section III: Quick Step Building HDF Java Libraries with CMake Command Mode Section IV: Further considerations Section V: Options for building HDF Java Libraries with CMake command line Section VI: CMake option defaults for HDF Java Section VII: User Defined Options for HDF Java Libraries with CMake Section VIII: Options for platform configuration files ************************************************************************ ======================================================================== I. Preconditions ======================================================================== Obtaining HDF Java source code 1. Create a directory for your development; for example, "myhdfstuff". 2. Obtain compressed (*.tar or *.zip) HDF Java source from https://support.hdfgroup.org/products/java/release/download.html and put it in "myhdfstuff". Do not uncompress. CMake version 1. We suggest you obtain the latest CMake from the Kitware web site. The HDFJava 3."X.Y" product requires a minimum CMake version 3.2, where "X.Y" is the current HDF Java release version. ======================================================================== II. Quick Step Building HDF Java Libraries with CMake Script Mode ======================================================================== This short set of instructions is written for users who want to quickly build the HDF Java Library and HDFView from the HDF Java 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 HDF Java. The following files referenced below are available at the HDF web site: https://support.hdfgroup.org/products/java/release/download.html CMake build script: CTestScript.cmake External compression szip and zlib libraries: SZip.tar.gz ZLib.tar.gz JPEG8d.tar.gz HDF4.tar.gz HDF5.tar.gz Platform configuration files: HDFJavaconfig.cmake To build HDFJava with all the external libraries you will need to: 1. Change to the development directory "myhdfstuff". 2. Download the *.tar.gz files to "myhdfstuff". Do not uncompress the files. 3. Download the CTestScript.cmake file to "myhdfstuff". CTestScript.cmake file should not be modified. 4. Download the platform configuration file to "myhdfstuff". Do not modify the file unless you want to change default build environment. 5. From the "myhdfstuff" directory execute the CTest Script with the following options: ctest -S HDFJavaconfig.cmake -C Release -VV -O hdfjava.log The command above will configure, build, test, and create an install package in the myhdfstuff/HDF Java/build folder. 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_BUILD_CONFIGURATION in the platform configuration file. The -VV option is for verbose; use -V for less verbose. The "-O hdfjava.log" option saves the output to a log file hdfjava.log. 6. To install, "X.Y" is the current release version On Windows, execute: HDFJava-3."X.Y"-win32.exe or HDFJava-3."X.Y"-win64.exe By default this program will install the HDF Java library into the "C:\Program Files" directory and will create the following directory structure: HDF_Group --HDFJava ----3."X.Y" ------cmake ------lib On Linux, change to the install destination directory (create it if doesn't exist) and execute: /myhdfstuff/HDF Java/build/HDFJava-3."X.Y"-Linux.sh After accepting the license, the script will prompt: By default the HDF Java will be installed in: "/HDFJava-3."X.Y"-Linux" Do you want to include the subdirectory HDFJava-3."X.Y"-Linux? Saying no will install in: "" [Yn]: Note that the script will create the following directory structure relative to the install point: HDF_Group --HDFJava ----3."X.Y" ------lib ------share By default the installation will create the folders in the /HDF_Group/HDFJava/3."X.Y" location. On Mac you will find HDFJava-3."X.Y"-Darwin.dmg in the build folder. Click on the dmg file to proceed with installation. After accepting the license, there will be an application packaged named: HDFJava By default this will install the HDF Java library into the "/Applications/HDFJava.app/Contents/" directory and will create the following directory structure: Java MacOS Resources --lib --share ----cmake ======================================================================== III. Quick Step Building HDF Java Static Libraries with CMake ======================================================================== Notes: This short set of instructions is written for users who want to quickly build the just the HDF Java static library from the HDF Java source code package using the CMake command line tools. Go through these steps: 1. Change to the development directory "myhdfstuff". 2. Uncompress the HDF Java source file 3. Create a folder "build" in the "myhdfstuff" directory. 4. Change into the "build" folder. 5. Configure the library and tests with one of the following commands: On Windows 32 bit cmake -G "Visual Studio 11" -DCMAKE_BUILD_TYPE:STRING=Release -DBUILD_TESTING:BOOL=ON ..\HDFJava-3."X.Y" On Windows 64 bit cmake -G "Visual Studio 11 Win64" -DCMAKE_BUILD_TYPE:STRING=Release -DBUILD_TESTING:BOOL=ON ..\HDFJava-3."X.Y" On Linux and Mac cmake -G "Unix Makefiles" -DCMAKE_BUILD_TYPE:STRING=Release -DBUILD_TESTING:BOOL=ON ../HDFJava-3."X.Y" where "X" is the current release version. 6. Build he library and tests with this command: cmake --build . --config Release 7. Test the library with this command: ctest . -C Release 8. Create an install image with this command: cpack -C Release CPackConfig.cmake 9. To install, "X.Y" is the current release version On Windows, execute: HDFJava-3."X.Y"-win32.exe or HDFJava-3."X.Y"-win64.exe By default this program will install the HDF Java library into the "C:\Program Files" directory and will create the following directory structure: HDF_Group --HDFJava ----3."X.Y" ------cmake ------lib On Linux, change to the install destination directory (create it if doesn't exist) and execute: /myhdfstuff/HDFJava/build/HDFJava-3."X.Y"-Linux.sh After accepting the license, the script will prompt: By default the HDF Java will be installed in: "/HDFJava-3."X.Y"-Linux" Do you want to include the subdirectory HDFJava-3."X.Y"-Linux? Saying no will install in: "" [Yn]: Note that the script will create the following directory structure relative to the install point: HDF_Group --HDFJava ----3."X.Y" ------lib ------share By default the installation will create the folders in the /HDF_Group/HDFJava/3."X.Y" location. On Mac you will find HDFJava-3."X.Y"-Darwin.dmg in the build folder. Click on the dmg file to proceed with installation. After accepting the license, there will be an application packaged named: HDFJava By default this will install the HDF Java library into the "/Applications/HDFJava.app/Contents/" directory and will create the following directory structure: Java MacOS Resources --lib --share ----cmake ======================================================================== IV. Further considerations ======================================================================== 1. We suggest you obtain the latest CMake for windows from the Kitware web site. The HDFJava 3.x product requires a minimum CMake version of 3.2.2. 2. HDFJava requires Zlib, Szip, Jpeg, hdf4, hdf5: 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: -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 -DJPEG_LIBRARY:FILEPATH=${some_location}/lib/jpeg.lib -DJPEG_INCLUDE_DIR:PATH=${some_location}/include -DHDF4_LIBRARY:FILEPATH=${some_location}/lib/hdf.lib;some_location/lib/mfhdf.lib -DHDF4_INCLUDE_DIR:PATH=${some_location}/include -DHDF5_LIBRARY:FILEPATH=${some_location}/lib/hdf5.lib -DHDF5_INCLUDE_DIR:PATH=${some_location}/include where "${some_location}" is the full path to the extlibs folder. B. Use source packages from an GIT server by adding the following CMake options: HDF_ALLOW_EXTERNAL_SUPPORT:STRING="GIT" HDF4_GIT_URL:STRING="http://${some_location}/hdf4/" HDF5_GIT_URL:STRING="http://${some_location}/hdf5/" JPEG_GIT_URL:STRING="http://${some_location}/jpeg/" ZLIB_GIT_URL:STRING="http://${some_location}/zlib/" SZIP_GIT_URL:STRING="http://${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: HDF_ALLOW_EXTERNAL_SUPPORT:STRING="TGZ" HDF4_TGZ_NAME:STRING="hdf4_src.ext" HDF5_TGZ_NAME:STRING="hdf5_src.ext" 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 Additional options: CMAKE_ANSI_CFLAGS:STRING=-fPIC CTEST_USE_LAUNCHERS:BOOL=ON CMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=OFF 4. Windows developers should install WiX to create an install image with CPack. Visual Studio Express users will not be able to package HDFJava 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 11" \ -DHDF_ENABLE_SZIP_SUPPORT:BOOL=OFF \ -DCMAKE_BUILD_TYPE:STRING=Release .. Notes: CMake and HDF Java 1. Using CMake for building and using HDFJava 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 HDFJava 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 at: cdash.hdfgroup.org. 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 HDFJava Libraries with the CMake Command Line ======================================================================== To build the HDFJava Libraries with CMake, go through these five steps: 1. Run CMake 2. Configure the cache settings 3. Build HDFJava 4. Test HDFJava 5. Package HDFJava (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\HDFJava, then use c:\MyHDFstuff\HDFJava\build or c:\MyHDFstuff\build\HDFJava 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 /config/cmake/cacheinit.cmake -G "" [-D] Where is: * MinGW Makefiles * NMake Makefiles * Unix Makefiles * Visual Studio 12 * Visual Studio 12 Win64 * Visual Studio 11 * Visual Studio 11 Win64 * Visual Studio 10 * Visual Studio 10 Win64 is: * HDF4_INCLUDE_DIR:PATH= * HDF4_LIBRARY:FILEPATH= * HDF5_INCLUDE_DIR:PATH= * HDF5_LIBRARY:FILEPATH= * SZIP_INCLUDE_DIR:PATH= * SZIP_LIBRARY:FILEPATH= * ZLIB_INCLUDE_DIR:PATH= * ZLIB_LIBRARY:FILEPATH= * JPEG_INCLUDE_DIR:PATH= * JPEG_LIBRARY:FILEPATH= * :BOOL=[ON | OFF] is: # This is the CMakeCache file used by HDF Group for daily tests. ######################## # EXTERNAL cache entries ######################## set (BUILD_SHARED_LIBS OFF CACHE BOOL "Build Shared Libraries" FORCE) set (BUILD_TESTING ON CACHE BOOL "Build HDFJava Unit Testing" FORCE) set (HDF_PACKAGE_EXT "" CACHE STRING "Name of HDF package extension" FORCE) set (HDF_ENABLE_JPEG_LIB_SUPPORT ON CACHE BOOL "Use Jpeg library" FORCE) set (HDF_ENABLE_Z_LIB_SUPPORT ON CACHE BOOL "Enable Zlib Filters" FORCE) set (HDF_ENABLE_SZIP_SUPPORT ON CACHE BOOL "Use SZip Filter" FORCE) set (HDF_ENABLE_SZIP_ENCODING ON CACHE BOOL "Use SZip Encoding" FORCE) set (HDF_DISABLE_COMPILER_WARNINGS OFF CACHE BOOL "Disable compiler warnings" FORCE) set (HDF_PACKAGE_EXTLIBS OFF CACHE BOOL "(WINDOWS)CPACK - include external libraries" FORCE) set (HDF_ALLOW_EXTERNAL_SUPPORT "NO" CACHE STRING "Allow External Library Building (NO GIT TGZ)" FORCE) set_property (CACHE HDF_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 "JPEG8d.tar.gz" CACHE STRING "Use JPEG from compressed file" FORCE) set (HDF4_TGZ_NAME "HDF4.tar.gz" CACHE STRING "Use HDF4 from compressed file" FORCE) set (HDF5_TGZ_NAME "HDF5.tar.gz" CACHE STRING "Use HDF5 from compressed file" FORCE) set (HDF4_PACKAGE_NAME "hdf4" CACHE STRING "Name of HDF4 package" FORCE) set (HDF5_PACKAGE_NAME "hdf5" CACHE STRING "Name of HDF5 package" 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 11). CMake will read in the CMakeLists.txt files from the source directory and display options for the HDF Java 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\HDF Java\build directory: cmake -C ../config/cmake/cacheinit.cmake -G "Visual Studio 11" \ -DHDF_ENABLE_SZIP_SUPPORT:BOOL=OFF -DHDF_BUILD_EXAMPLES: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: HDF_NO_PACKAGES:BOOL=ON HDF_USE_FOLDERS:BOOL=OFF 3. Build HDFJava On Windows, you can build HDFJava 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, jpeg, hdf4 and hdf5) can be configured to allow building the libraries by downloading from an GIT repository. The option is 'HDF_ALLOW_EXTERNAL_SUPPORT'; by adding the following configuration option: -DHDF_ALLOW_EXTERNAL_SUPPORT:STRING="GIT" The options to control the GIT URL (config/cmake/cacheinit.cmake file) are: HDF4_GIT_URL:STRING="http://${some_location}/hdf4" HDF5_GIT_URL:STRING="http://${some_location}/hdf5" JPEG_GIT_URL:STRING="http://${some_location}/jpeg" ZLIB_GIT_URL:STRING="http://${some_location}/zlib" SZIP_GIT_URL:STRING="http://${some_location}/szip" ${some_location} should be changed to your git location. Also define CMAKE_BUILD_TYPE to be the configuration type. Also set the GIT branch for each repo. 3.2.2 Or the external libraries (zlib, szip, jpeg, hdf4 and hdf5) can be configured to allow building the libraries by using a compressed file. The option is 'HDF_ALLOW_EXTERNAL_SUPPORT' and is enabled by adding the following configuration option: -DHDF_ALLOW_EXTERNAL_SUPPORT:STRING="TGZ" The options to control the TGZ names (config/cmake/cacheinit.cmake file) are: HDF4_TGZ_NAME:STRING="hdf4_src.ext" HDF5_TGZ_NAME:STRING="hdf5_src.ext" 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 HDFJava 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 HDFJava (create an install image) To package the build into a simple installer using the NullSoft installer NSIS on Windows, or WiX 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. Also, if you are using a Visual Studio Express version or do not want to enable the packaging components, set HDF_NO_PACKAGES to ON (on the command line add -DHDF_NO_PACKAGES:BOOL=ON) 6. The files that support building HDFJava 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. ======================================================================== VI. CMake Option Defaults for HDFJava ======================================================================== In the options listed below, there are three columns of information: Option Name, Option Description, and Option Default. The config/cmake/cacheinit.cmake file overrides the following values. ---------------- General Build Options --------------------- BUILD_SHARED_LIBS "Build Shared Libraries" OFF BUILD_TESTING "Build HDFJava Unit Testing" OFF ---------------- HDFJava Build Options --------------------- HDFJAVA_PACK_EXAMPLES "Package the HDFJava Library Examples Compressed File" OFF ---------------- HDFJava Apple Build Options --------------------- HDF_BUILD_WITH_INSTALL_NAME "Build with library install_name set to the installation path" OFF HDFJAVA_PACK_MACOSX_FRAMEWORK "Create a Mac OSX Framework Bundle" OFF ---------------- HDFJava Native Options --------------------- HDF_DISABLE_COMPILER_WARNINGS "Disable compiler warnings" OFF ---------------- HDFJava Advanced Options --------------------- HDF_NO_PACKAGES "Do not include CPack Packaging" OFF HDF_PACKAGE_EXTLIBS "CPACK - include external libraries" OFF HDF_USE_FOLDERS "Enable folder grouping of projects in IDEs." OFF HDFJAVA_PACK_JRE "Package a JRE installer file" OFF ---------------- External Library Options --------------------- HDF_ALLOW_EXTERNAL_SUPPORT "Allow External Library Building" "NO" HDF4_USE_EXTERNAL "Use External Library Building for HDF4" 0 HDF5_USE_EXTERNAL "Use External Library Building for HDF5" 0 ======================================================================== VII. User Defined Options for HDFJava 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. ======================================================================== VIII. Options for Platform Configuration Files ======================================================================== Below is the HDFJavaconfig.cmake ctest script with extra comments. The example is for a linux machine, but the same scripts can be used on a Windows machine by adjusting the CTEST_CMAKE_GENERATOR option in the platform configuration script. ############################################################################ # Product specific script, HDFJavaconfig.cmake, that uses the # CTestScript.cmake file. Usage: # "ctest -S HDFJavaconfig.cmake -C Release -O hdfjavastatic.log" ############################################################################ cmake_minimum_required(VERSION 3.2.2 FATAL_ERROR) # this is the location of the source hardcoded to HDF Java set(CTEST_SOURCE_NAME HDFJava) # this is the location of the source with ctest parameter hdf5src # "ctest -S HDFJavaconfig.cmake -C Release -O hdfjavastatic.log" set(CTEST_SOURCE_NAME ${CTEST_SCRIPT_ARG}) # this is the location of the build directory set(CTEST_BINARY_NAME ${CTEST_SOURCE_NAME}/build) # this is the directory the script is executed from set(CTEST_DASHBOARD_ROOT "${CTEST_SCRIPT_DIRECTORY}") # this is the full path of the source directory set(CTEST_SOURCE_DIRECTORY "${CTEST_DASHBOARD_ROOT}/${CTEST_SOURCE_NAME}") # this is the full path of the build directory set(CTEST_BINARY_DIRECTORY "${CTEST_DASHBOARD_ROOT}/${CTEST_BINARY_NAME}") ################################################################### ### Following Line is one of [Release, RelWithDebInfo, Debug] ##### set(CTEST_BUILD_CONFIGURATION "Release") ################################################################### ################################################################### ######### Following describes compiler ############ # this is for linux set(CTEST_CMAKE_GENERATOR "Unix Makefiles") # this is for windows 32 bit #set(CTEST_CMAKE_GENERATOR "Visual Studio 11") # this is for windows 64 bit #set(CTEST_CMAKE_GENERATOR "Visual Studio 11 Win64") # Visual Studio 2013 is 12, Visual Studio 2012 is 11, Visual Studio 2010 is 10 ################################################################### ################################################################### ######### Following is for submission to CDash ############ ################################################################### set(MODEL "Experimental") ######### Following describes computer ############ ## Set the following to unique id your computer ## set(CTEST_SITE "LINUX.XXXX") ## following is optional to describe build ## set(SITE_BUILDNAME_SUFFIX "STATIC") ######### Following controls CDash submission ########## #set(LOCAL_SUBMIT "TRUE") ######### Following controls test process ########## #set(LOCAL_SKIP_TEST "TRUE") #set(LOCAL_MEMCHECK_TEST "TRUE") #set(LOCAL_COVERAGE_TEST "TRUE") ######### Following controls cpack command ########## #set(LOCAL_NO_PACKAGE "TRUE") ######### Following controls source update ########## #set(LOCAL_UPDATE "TRUE") ######### Following controls source repository ########## # current HDF Group git url #set(hdfgroup_url "hdfgroup.org") #set(REPOSITORY_URL "http://git.${hdfgroup_url}/hdfview/hdfjava") #set(REPOSITORY_BRANCH hdfjava") #comment to use a uncompressed source folder set(CTEST_USE_TAR_SOURCE "hdf_java_3_3_2") ################################################################### ################################################################### #### Change default configuration of options in config/cmake/cacheinit.cmake file ### #### format: set(ADD_BUILD_OPTIONS "${ADD_BUILD_OPTIONS} -DXXX:YY=ZZZZ") ### uncomment/comment and change the following lines for configuration options ### comment the following line to build shared libraries set(ADD_BUILD_OPTIONS "${ADD_BUILD_OPTIONS} -DBUILD_SHARED_LIBS:BOOL=OFF") #### ext libraries #### ### ext libs from tgz set(ADD_BUILD_OPTIONS "${ADD_BUILD_OPTIONS} -DHDF_ALLOW_EXTERNAL_SUPPORT:STRING=TGZ -DTGZPATH:PATH=${CTEST_SCRIPT_DIRECTORY}") ### ext libs from git #set(ADD_BUILD_OPTIONS "${ADD_BUILD_OPTIONS} -DHDF_ALLOW_EXTERNAL_SUPPORT:STRING=GIT") ### ext libs on system #set(ADD_BUILD_OPTIONS "${ADD_BUILD_OPTIONS} -DZLIB_LIBRARY:FILEPATH=${some_location}/lib/zlib.lib -DZLIB_INCLUDE_DIR:PATH=${some_location}/include") #set(ADD_BUILD_OPTIONS "${ADD_BUILD_OPTIONS} -DSZIP_LIBRARY:FILEPATH=${some_location}/lib/szlib.lib -DSZIP_INCLUDE_DIR:PATH=${some_location}/include") ### Create install package with external libraries (szip, zlib) set(ADD_BUILD_OPTIONS "${ADD_BUILD_OPTIONS} -DHDF_PACKAGE_EXTLIBS:BOOL=ON") ### disable test program builds #set(ADD_BUILD_OPTIONS "${ADD_BUILD_OPTIONS} -DBUILD_TESTING:BOOL=OFF") ### disable packaging #set(ADD_BUILD_OPTIONS "${ADD_BUILD_OPTIONS} -DHDF_NO_PACKAGES:BOOL=ON") ### disable building examples #set(ADD_BUILD_OPTIONS "${ADD_BUILD_OPTIONS} -DHDF_BUILD_EXAMPLES:BOOL=OFF") ### disable building tests #set(ADD_BUILD_OPTIONS "${ADD_BUILD_OPTIONS} -DBUILD_TESTING:BOOL=OFF") ### change install prefix #set(ADD_BUILD_OPTIONS "${ADD_BUILD_OPTIONS} -DCMAKE_INSTALL_PREFIX:PATH=install") ################################################################### include(${CTEST_SCRIPT_DIRECTORY}/CTestScript.cmake) ======================================================================== For further assistance, send email to help@hdfgroup.org ========================================================================