Page History

Overview

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. 

Binary versions

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 for Linux. Ubuntu maintains a Magics version in their system default repository. 

Installing Magics through conda and pip

If you want to use Magics only through Python you have now choices to install Magics with your favourite Python package manager. With the release of Magics 4.

...

0.0 (Feb 2019), the Python interface is separated from the library. This allowed the packaging through pip and conda.

Using pip

When using pip it is required to have the Magics library installed on the system!

pip install Magics

Ref: https://pypi.org/project/Magics/

Using conda

Conda will install the Magics library and all its dependencies for you. Please make sure to  activate you conda environment  before running your python program.

conda install -c conda-forge Magics
conda activate
python my-magics-script.py

Building Magics from source yourself

Requirements

...

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. 

if BUFR support needed

Compilers
C++	http://gcc.gnu.org/	The compiler must support C++ 17. GCC supports it from version 7
Fortran	http://gcc.gnu.org/fortran/	If Fortran or BUFR support neededOnly needed to run Fortran tests
Utilities
make	http://www.gnu.org/software/make/
cmake	https://cmake.org	version > v2.8.4
Python Support
swig	http://www.swig.org/	to generate the python interface
python	http://www.python.org/
python-numpy	http://www.numpy.org/
3.12
Third party libraries
proj	httphttps://trac.osgeoproj.org/proj/	Proj4 to handle projections
boost	http://www.boost.org/ (Requires 1.5)	used for coastlines
netcdf	http://www.unidata.ucar.edu/software/netcdf/	if for netcdf support needed Please note: You also need to install the legacy C++ interface and HDF5
cairo + pango	https://www.cairographics.org http://www.pango.org/	if for png/pdf support needed
expat	http://expat.sourceforge.net/	for XML parsing
ECMWF libraries
ecCodes	ECC
grib-api	GRIB-API Home (Requires 1.9 or above)	please consider using ecCodes!
Enables GRIB and BUFR support
odc	odc on GitHub	odb-api	ODB-API Home	if ODB support needed		emoslib	EMOS

Include Page
SUP:General CMake installation instructions SUP:General CMake installation instructions

Magics specific CMake options

After changing into the build Magics directory, the user  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/.

To make sure that a feature is really enabled, you will have to specify with the option ex: -DENABLE_GRIBNETCDF=ON. In that case CMake will fail if the GRIB NetCDF support can not cannot 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 , and 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!)

...