Magics is now using ecCodes
From the 2.22.0 version, Magics is using CMake for its compilation and installation. This is a first step towards an homogenisation of the installation procedures for all ECMWF packages.
Before you install from source code you might want to check that already compiled binary versions are available to you. Magics and third-party dependent software packages might be available as binary packages for you platform in form of RPMs or Debian packages. You might find them by going to the software search services, such as for OpenSuSE and SLES at http://software.opensuse.org/search (select "Search options" - "Include users' home projects"). Ubuntu maintains a Magics version in their system default repository.
CMake installation instructions
The CMake build system is used to build ECMWF software. The build process comprises two stages:
- CMake runs some tests on the system and finds out if required software libraries and headers are available. It uses this information to create native build tools (e.g. Makefiles) for the current platform.
- The actual build can take place, for example by typing '
To install any ECMWF software package, CMake needs to be installed on your system. On most systems it will be already installed or this can be done through the standard package manager to install software. For further information to install CMake see
During a build with CMake there are three different directories involved: The source dir, the build dir and the install dir.
|Source||Contains the software's source code. This is where a source tarball should be extracted to.|
|Build||Configuration and compiler outputs are generated here, including libraries and executables.|
|Install||Where the software will actually be used from. Installation to this directory is the final stage.|
Of these, the source and build directories can be anywhere on the system. The installation directory is usually left at its default, which is
/usr/local. Installing software here ensures that it is automatically available to users. It is possible to specify a different installation directory by adding
-DCMAKE_INSTALL_PREFIX=/path/to/install/dir to the CMake command line.
ECMWF software does not support in-source builds. Therefore the build directory cannot be (a subdirectory of) the source directory.
Quick Build Example
Here is an example set of commands to set up and build a software package using default settings. More detail for a customised build is given below.
On a machine with multiple cores, compilation will be faster by specifying the number of cores to be used simultaneously for the build, for example:
make command fails, you can get more output by typing:
The software distribution will include a small set of tests which can help ensure that the build was successful. To start the tests, type:
As before if you have multiple cores, you can run the tests in parallel by:
Some projects might not be set up to run tests in parallel. If you experience test failures, run the tests sequentially.
If the tests are successful, you can install the software:
General CMake options
Various options can be passed to the CMake command. The following table gives an overview of some of the general options that can be used. Options are passed to the
cmake command by prefixing them with -D, for example -DCMAKE_INSTALL_PREFIX=/path/to/dir.
|where to install the software|
to select the type of compilation:
(release with debug info)
|Additional flags to pass to the C++ compiler|
|Additional flags to pass to the C compiler|
|Additional flags to pass to the Fortran compiler|
The C, C++ and Fortran compilers are chosen by CMake. This can be overwritten by setting the environment variables CC, CXX and F77, before the call to
cmake, to set the preferred compiler. Further the variable
CMAKE_CXX_FLAGS can be used to set compiler flags for optimisation or debugging. For example, using
CMAKE_CXX_FLAGS="-O2 -mtune=native" sets options for better optimisation.
Finding support libraries
If any support libraries are installed in non-default locations, CMake can be instructed where to find them by one of the following methods. First, the option CMAKE_PREFIX_PATH can be set to a colon-separated list of base directories where the libraries are installed, for example
-DCMAKE_PREFIX_PATH=/path/where/my/sw/is/installed. CMake will check these directories for any package it requires. This method is therefore useful if many support libraries are installed into the same location.
Debugging configure failures
If CMake fails to configure your project, run with debug logging first:
This will output lots of diagnostic information (in blue) on discovery of dependencies and much more.
Requirements to build Magics
The following table lists the dependency Magics requires to be build from source. Please note, if you install this package from source you also might have to install the respective "-devel" packages of dependencies.
|Fortran||http://gcc.gnu.org/fortran/||If Fortran or BUFR support needed|
|swig||http://www.swig.org/||to generate the python interface|
|Third party libraries|
|proj||http://trac.osgeo.org/proj/||Proj4 to handle projections|
|boost||http://www.boost.org/ (Requires 1.5)||used for coastlines|
if netcdf support needed
|pango||http://www.pango.org/||if png/pdf support needed|
|expat||http://expat.sourceforge.net/||for XML parsing|
|grib-api||GRIB-API Home (Requires 1.9 or above)||please consider using ecCodes!|
|odb-api||ODB-API Home||if ODB support needed|
|emoslib||EMOSLIB||if BUFR support needed|
Magics specific CMake options
After changing into the build Magics directory, the user has to run CMake with his/her own options. The command gives feedback on what requirements are fulfilled and what software is still required. Table below gives an overview of the different options of configure. The default (without any options) will compile a share library only and install it in /usr/local/.
|enable grib support||on|
Use ecCodes for grib support
Setting this variable to OFF will will build Magics with grib_api
|ECCODES_PATH||where to find eccode ( if non-standard installation )|
|ENABLE_NETCDF||enable netcdf support||on|
|NETCDF_PATH||where to find netcdf ( if non-standard installation )|
|ENABLE_ODB||enable odb support||off|
|ODB_API_PATH||where to find odb ( if non-standard installation )|
enable bufr support
The bufr support is done through emoslib .
|EMOS_PATH||Where to find emos lib ( if non-standard installation )|
|ENABLE_PYTHON||enable python interface||auto|
|ENABLE_FORTRAN||enable fortran interface||on|
|ENABLE_METVIEW||enable metview support(and Qt support)||off|
|ENABLE_CAIRO||enable Cairo support||on|
|BOOST_ROOT||where to find boost ( if non-standard installation )|
|PROJ4_PATH||where to find proj4 ( if non-standard installation )|
To make sure that a feature is really enabled, you will have to specify with the option ex: -DENABLE_GRIB=ON. In that case CMake will fail if the GRIB support can not be enabled.
Testing your build
The Magics code contains a directory called test in which, in separate sub-directories, tests for the various interfaces of Magics are provided. Test programs in Fortran, C, Python and MagML are compiled and run if MAGPLUS_HOME=$PWD make check is invoked from the root directory. (Note that the MAGPLUS_HOME needs to be set!)
The output of the tests should verified before the library is installed. This setup does not check if the user setup is correct, but the code in test can be used to do so. More examples of source code can be found on the Magics web gallery .