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.
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.
Third party packages
(best installed through system package manager)
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)
|curl||Optional for web services support (WMS, Download module)|
|magics||Magics||if 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-api||ODB-API Home||if ODB support needed|
|emoslib||EMOSLIB||optional and deprecated|
CMake options are passed to the
cmake command by prefixing them with -D, for example -DENABLE_UI=OFF.
|ENABLE_UI||enables the Qt-based user interface||ON|
|ENABLE_PLOTTING||enables plotting capabilities using Magics||ON|
|ENABLE_MARS||enables MARS access (not required if using through the Web API)||OFF|
|MARS_LOCAL_HOME||sets the path to where local MARS is installed|
|ENABLE_ODB||enables processing and plotting of ODB data||OFF|
|ENABLE_MARS_ODB||enables ODB capabilities in MARS client||OFF|
|ENABLE_USAGE_LOG||enables logging of Metview startup calls||OFF|
|LOG_DIR||path to where to log the Metview startup calls|
|METVIEW_SCRIPT||name of the generated Metview startup script||metview|
|EXTRA_CONFIG_PATH||path to optional directory containing metview_local* script files|
|ENABLE_QT_DEBUG||outputs additional log messages from Qt-based modules||OFF|
|EXTRA_TITLE||build-specific title to add to the log entries|
|ENABLE_INPE||enables INPE modules||ON|
|Path options - only required when support libraries are not installed in default locations|
|ECCODES_PATH||path to where ecCodes has been installed|
|MAGICS_PATH||path to where Magics has been installed||Only required if plotting is enabled|
|NETCDF_PATH||path to where netCDF has been installed|
|ODB_API_PATH||path to where ODB_API has been installed||Only required if ODB is enabled|
|ODB_PATH||path to where the original ODB has been installed||Optional if ODB is enabled|
|EMOS_PATH||path to where Emoslib has been installed||Also set EMOS_LIB_NAME|
|FDB_PATH||path to where fdb has been installed||Only required if MARS is enabled|
|FLEXTRA_PATH||path to where the FLEXTRA executable has been installed||See Tutorials for more on FLEXTRA|
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
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.
See also the Installation FAQ.