...
CMAKE_INSTALL_PREFIX | where you want to install your ecCodes | /usr/local |
CMAKE_BUILD_TYPE | to select the type of compilation:
| RelWithDebInfo |
BUILD_SHARED_LIBS | Select the type of library built:
| ON |
CMAKE_C_COMPILER | C Compiler | |
CMAKE_C_FLAGS | Flags for the C Compiler | |
CMAKE_Fortran_COMPILER | Fortran Compiler | |
CMAKE_Fortran_FLAGS | Flags for the Fortran Compiler | |
ENABLE_NETCDF | For the grib_to_netcdf convert tool | AUTO |
ENABLE_JPG | Enable JPEG2000 support. This option should look for Jasper or OpenJPG | AUTO |
ENABLE_PNG | Enable PNG support for decoding/encoding | OFF |
ENABLE_PYTHON | Offers the Python interface to the package | AUTO |
ENABLE_FORTRAN | Offers the Fortran interface to the package | AUTO |
ENABLE_ECCODES_THREADS | Enable POSIX threads | OFF |
cmake options | doc | default |
---|
Note: The compilers can also be overridden by setting the environment variables CC and FC.
Note: To see the full output from the compilation, you can use:
make VERBOSE=1
Quick installation guide
Here is an example of a list of commands you could use to install ecCodes. It is assumed “>” is the shell prompt.
Code Block |
---|
> tar -xzf eccodes-x.y.z-Source.tar.gz > mkdir build ; cd build > cmake –DCMAKE_INSTALL_PREFIX=/path/to/where/you/install/eccodes ../eccodes-x.y.z-Source ... > make > make checkctest > make install |
Note that for the testing step ("make check"running the ctest command) you need to be connected to the internet (and set the relevant "http_proxy" environment variable if you must use a proxy) so data files can be downloaded for the tests. You can however download all the data files in one go (See the data tarball link at the top of the Releases page)
...