Overview

Metview uses CMake for its compilation and installation, in line with all other ECMWF packages. Note that there are other ways to install Metview from pre-built binary packages, or from a source bundle that includes many dependencies. See Releases.

Requirements to build Metview

The following table lists the dependencies Metview requires to be built from source. Please note, if you install these package from source you also might have to install the respective "-devel" packages.

Compilers
C++http://gcc.gnu.org/
Fortranhttp://gcc.gnu.org/fortran/
Utilities

make

http://www.gnu.org/software/make/

Third party packages

(best installed through system package manager)

Qt 5http://www.qt.io/

if Metview's user interface is required.

Note that on some systems it is also necessary to install the libQtWebKit-devel development package (it may have different names on different systems)

gdbmhttp://www.gnu.org.ua/software/gdbm/
bashhttps://www.gnu.org/software/bash/
netcdf 4http://www.unidata.ucar.edu/software/netcdf/

Please note: You also will need to install HDF5 and the legacy C++ interface if you wish to run the Single Column Model from Metview (ECMWF only)

curl
Optional for web services support (WMS, Download module)
bison

flex

ECMWF libraries
ecCodesecCodes Home
magicsMagicsif plotting support is needed. Note that Magics should be configured with the -DENABLE_METVIEW=ON option.

For a 'pure batch' installation of Metview with no user interface, it is possible to supply Magics with the option -DENABLE_METVIEW_NO_QT=ON


odb-apiODB-API Homeif ODB support needed
emoslibEMOSLIBoptional and deprecated

CMake options used in Metview

CMake options are passed to the cmake command by prefixing them with -D, for example -DENABLE_UI=OFF.

CMake option
Description
Default
ENABLE_UIenables the Qt-based user interfaceON
ENABLE_PLOTTINGenables plotting capabilities using MagicsON
ENABLE_MARSenables MARS access (not required if using through the Web API)OFF
MARS_LOCAL_HOMEsets the path to where local MARS is installed
ENABLE_ODBenables processing and plotting of ODB dataOFF
ENABLE_MARS_ODBenables ODB capabilities in MARS clientOFF
ENABLE_USAGE_LOGenables logging of Metview startup callsOFF
LOG_DIRpath to where to log the Metview startup calls
METVIEW_SCRIPTname of the generated Metview startup scriptmetview
EXTRA_CONFIG_PATHpath to optional directory containing metview_local* script files
ENABLE_QT_DEBUGoutputs additional log messages from Qt-based modulesOFF
EXTRA_TITLEbuild-specific title to add to the log entries
ENABLE_INPEenables INPE modulesON
Path options - only required when support libraries are not installed in default locations
CMake OptionDescriptionNotes
ECCODES_PATHpath to where ecCodes has been installed
MAGICS_PATHpath to where Magics has been installedOnly required if plotting is enabled
NETCDF_PATHpath to where netCDF has been installed
ODB_API_PATHpath to where ODB_API has been installedOnly required if ODB is enabled
ODB_PATHpath to where the original ODB has been installedOptional if ODB is enabled
EMOS_PATHpath to where Emoslib has been installedAlso set EMOS_LIB_NAME
FDB_PATHpath to where fdb has been installedOnly required if MARS is enabled
FLEXTRA_PATHpath to where the FLEXTRA executable has been installedSee Tutorials for more on FLEXTRA

Notes for installers of Metview 3

If you have installed Metview 3 before, then here are some things to note. Metview 5 does not use directly OpenGL for its on-screen graphics; therefore, it is not necessary to build your own Mesa library anymore.

Metview 5 can be installed side-by-side with an existing Metview 3 installation. However, note that the default startup script will be

/usr/local/bin/metview

so make sure this will not clash with an existing installation. See the table of CMake options for the flag which will allow you to change this.

FAQ

See also the Installation FAQ.