diff --git a/.DS_Store b/.DS_Store index e4d0f20e..6340455e 100644 Binary files a/.DS_Store and b/.DS_Store differ diff --git a/assets/.DS_Store b/assets/.DS_Store index 9c198d4e..0a1124fd 100644 Binary files a/assets/.DS_Store and b/assets/.DS_Store differ diff --git a/documentation/.DS_Store b/documentation/.DS_Store index e309de71..586b8a35 100644 Binary files a/documentation/.DS_Store and b/documentation/.DS_Store differ diff --git a/documentation/hdf4-docs/building_hdf4_with_cmake.md b/documentation/hdf4-docs/building_hdf4_with_cmake.md deleted file mode 100644 index e9c6ceef..00000000 --- a/documentation/hdf4-docs/building_hdf4_with_cmake.md +++ /dev/null @@ -1,104 +0,0 @@ -# Building HDF4 with CMake - -A CTest script and platform configuration file can be used to simplify building with CMake. The script below will build HDF4 with SZIP, ZLIB, and the JPEG external libraries. - -## Preconditions: - -* [CMake](https://www.cmake.org) **MUST** be installed. The minimum required version is CMake 3.10 and the recommended version is 3.15. CMake 3.15 is *required* for VS 2019. -* Blank spaces **MUST NOT** be used in directory path names as this will cause the build to fail. -* (Windows) [NSIS](http://nsis.sourceforge.net/Main_Page) or [WiX](http://www.wixtoolset.org/) should be installed in order to create an install image with CPack. NSIS will create a .exe installer. WiX will create a .msi installer. - - Visual Studio Express users will not be able to package HDF into an install image executable. Turn off packaging by doing the following: - - * Edit `HDF4options.cmake`. - * Add the line: `set(ADD_BUILD_OPTIONS "${ADD_BUILD_OPTIONS} –DNO_LOCAL_PACKAGE:BOOL=ON")` - * Uncomment the line: `set(ADD_BUILD_OPTIONS "${ADD_BUILD_OPTIONS} -DHDF4_NO_PACKAGES:BOOL=ON")` - * Comment out the line: `set(ADD_BUILD_OPTIONS "${ADD_BUILD_OPTIONS} -DHDF4_PACKAGE_EXTLIBS:BOOL=ON")` - -## Build Instructions - -1. Create a working directory. -2. Uncompress the HDF4 CMake source code file into the working directory. It will contain a `CMake-hdf-N` directory (where N is the release version). -3. From the command line, go into the `CMake-hdf-N` directory, which contains: - - | build*.sh (.bat) | Build Script(s) | - | CTestScript.cmake | ctest Command | - | hdf-N/ | HDF4 Source Code | - | HDF4config.cmake | Configuration file | - | HDF4options.cmake | User modifiable options | - | JPEG8d.tar.gz | External library for JPEG Compression | - | SZip.tar.gz | External library for SZIP Compression | - | ZLib.tar.gz | External library for ZLIB Compression | - -4. By default HDF4 will be built: - * Without Fortran - * With SZIP compression enabled - * With ZLIB compression enabled - * With static libraries enabled - - Users can change the options that HDF4 is built with by adding options to the build command (see the batch files/test script below) or by modifying the `HDF4options.cmake` file. The `HDF4options.cmake` file will override any options set in the configuration file. For more information see the [How to Change HDF4 CMake Build Options](/documentation/hdf4-docs/how_to_change_hdf4_cmake_build_options.html) page. - - REQUIRED: Visual Studio Express users must change the build options to turn off packaging or the build will fail. - -5. Execute the batch file or shell script containing the ctest command for your platform. (See Troubleshooting if you do not see your platform). - Example build files are shown below: - - | Platform | Batch File / Shell Script | ctest command | - | --- | ---- | ----- | - | Windows 64-bit VS 2015 | build-VS2015-64.bat | `ctest -S HDF4config.cmake,BUILD_GENERATOR=VS201564 -C Release -V -O hdf4.log` | - | Windows 32-bit VS 2015 | build-VS2015-32.bat | `ctest -S HDF4config.cmake,BUILD_GENERATOR=VS2015 -C Release -V -O hdf4.log` | - | Unix | build-unix.sh | `ctest -S HDF4config.cmake,BUILD_GENERATOR=Unix -C Release -V -O hdf4.log` | - - Where the ctest command is using these options: - - * The `-S` option uses the script version of ctest. - * The `-C` option specifies the build configuration which matches `CTEST_BUILD_CONFIGURATION` in the configuration file. - * The `-V` option indicates verbose. **`-VV` option indicates more verbose**. - * The `-O` option saves the output to a log file, `hdf4.log`. - -6. Locate the built binary. - - The built binary will be placed in the build directory and will have the format: - `hdf-4.2.N-` - On Windows, a .msi or .exe file will also be created, depending on the installer. On Unix, an additional .sh file will be created. - - If the built binary is not there, then see Troubleshooting for help. - -7. Check what is included with your built binaries - - You will find the `libhdf4.settings` file in the build directory. It contains information on how the binaries were built. - -## Troubleshooting - -### My platform/compiler is not included. Can I still use the configuration files? - - Yes, you can but you will have to edit the `HDF4config.cmake` file and update the variable: - - `CTEST_CMAKE_GENERATOR` - - Other variables may be updated for informational purposes but are not required (for example, `SITE_OS_BITS`). - - The generators for your platform can be seen by typing: - - `cmake --help` - -### What do I do if the build fails? - - If the build works properly, then you will find the built and compressed binary in your `CMake-hdf-4.N directory`. If you do not find it then check the log files. You will find those in the build directory under `CMake-hdf-4.N`. For example, on Unix the log files will be in: - - `CMake-hdf-4.N/build/Testing/Temporary/` - - There are log files for the configure, test, and build. - -### What if the binary does not get packaged properly? - - If the binary did not get packaged properly, look at the cpack.log file in the build directory under `CMake-hdf-4.N`. For example, on Unix look here: - `CMake-hdf-4.N/build/cpack.log` - -### What do I do if I need to rebuild the software? - - If you have to rebuild HDF4, remove the build directory first. - -### The library was built but there are no binaries. What do I do? - - To install or package the binaries, run either make install or cpack in the build/ directory. diff --git a/documentation/hdf4-docs/how_to_change_hdf4_cmake_build_options.md b/documentation/hdf4-docs/how_to_change_hdf4_cmake_build_options.md deleted file mode 100644 index cf7f8bd3..00000000 --- a/documentation/hdf4-docs/how_to_change_hdf4_cmake_build_options.md +++ /dev/null @@ -1,39 +0,0 @@ -# How to Change HDF4 CMake Build Options - -If using the CTest script and configuration method to build HDF4, you can easily change the build options by either specifying the options on the command line or adding them to the options file, HDF4options.cmake. - -## Change options from the command line - -As described on the [Building HDF4 with CMake](/documentation/hdf4-docs/building_hdf4_with_cmake.html) page, batch files for Windows and a shell script for Unix are provided for building HDF4. These files each contain a command that gets executed on the command line to build HDF4. They can be edited to add or change these options to the build command: - -| Option | Purpose | -| --- | ---| -| BUILD_GENERATOR | Which CMake generator to use (required) | -| INSTALLDIR | Root folder where HDF4 is installed | -| CTEST_CONFIGURATION_TYPE | Release, Debug, RelWithDebInfo | -| CTEST_SOURCE_NAME | Name of source folder (eg. hdf-4.2.N) | - -These are described at the top of the `HDF4config.cmake` file. - -## Change options with the options file - -The `HDF4options.cmake` file is provided so that users can change build options without modifying the configuration file. It gets included by the configuration file and it overrides the settings in the configuration file. - -Options can be set by using the following format: - `set(ADD_BUILD_OPTIONS "${ADD_BUILD_OPTIONS} -DXXX:YY=ZZZZ")` - -The `config/cmake/cacheinit.cmake` file has a complete list of the options that can be used to build HDF4. (Section V in the `INSTALL_CMake.txt` file lists the default CMake options used by HDF4.) - -Several options are included in the `HDF4options.cmake` file, such as the options to turn off ZLIB or SZIP. Additional options can be added to this file, as needed. Common configure options that can be turned off or on in the `HDF4options.cmake` file are listed below. - -## Common CMake and configure Options - -There are numerous CMake options available to users, many of which correspond directly to configure options. Below are a few important options and how to change them in the configuration file. The corresponding configure option is also shown: - -| Option | Configure | Cmake | -| --- | --- | --- | -| Build shared libraries | --enable-shared | `set(ADD_BUILD_OPTIONS "${ADD_BUILD_OPTIONS} -DBUILD_SHARED_LIBS:BOOL=ON")` | -| Build HDF4 Fortran library | --enable-fortran | `set(ADD_BUILD_OPTIONS "${ADD_BUILD_OPTIONS} -DHDF4_BUILD_FORTRAN:BOOL=ON")` | -| Disable ZLIB filter | --with-zlib | `set(ADD_BUILD_OPTIONS "${ADD_BUILD_OPTIONS} -DHDF4_ENABLE_Z_LIB_SUPPORT:BOOL=OFF")` | -| Disable SZIP filter | --with-szlib | `set(ADD_BUILD_OPTIONS "${ADD_BUILD_OPTIONS} -DHDF4_ENABLE_SZIP_SUPPORT:BOOL=OFF")`
`set(ADD_BUILD_OPTIONS "${ADD_BUILD_OPTIONS} -DHDF4_ENABLE_SZIP_ENCODING:BOOL=OFF")` | -| Build HDF4 Java library | --enable-java | `set(ADD_BUILD_OPTIONS "${ADD_BUILD_OPTIONS} -DHDF4_BUILD_JAVA:BOOL=ON")`
Also specify the location of Java in the JAVA_HOME environment variable. | diff --git a/downloads/.DS_Store b/downloads/.DS_Store index 86cc6789..266d1f4e 100644 Binary files a/downloads/.DS_Store and b/downloads/.DS_Store differ