Version: 8.3.0
 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Friends Macros Pages
Configuring and Installing MED from sources

The install procedure of MEDCoupling can handle a variety of configurations to suit the needs of its user. Instructions for configuring and installing the module can be found here. Partitioning and parallel functionalities are optional.

Assume that the library sources are located in MEDCOUPLING_SRC directory. Build and install directories are MEDCOUPLING_BUILD and MEDCOUPLING_INSTALL, respectively. The first step consists in preparing the CMake build precedure :

mkdir <MEDCOUPLING_BUILD>
cd <MEDCOUPLING_BUILD>
cmake -DCMAKE_BUILD_TYPE=<Mode> -DCMAKE_INSTALL_PREFIX=<MEDCOUPLING_INSTALL> <MEDCOUPLING_SRC>

, where <Mode> is build mode (Release or Debug).

This will configure the library without splitting functionalities. The parallel functionalities will be compiled if an MPI version has been found.

The following options can be useful to configure MEDCoupling :

  • -DMEDCOUPLING_PARTITIONER_METIS=ON enables metis graph library in MEDPartitioner,
  • -DMEDCOUPLING_PARTITIONER_PARMETIS=ON enables parmetis graph library in MEDPartitioner,
  • -DMEDCOUPLING_PARTITIONER_SCOTCH=ON enables scotch graph library in MEDPartitioner,
  • -DMEDCOUPLING_MICROMED=ON build MED with MED file dependancy,
  • -DMEDCOUPLING_ENABLE_PYTHON=ON builds PYTHON bindings,
  • -DMEDCOUPLING_ENABLE_PARTITIONER builds MEDPartitioner,
  • -DMEDCOUPLING_ENABLE_RENUMBER builds Renumber,
  • -DMEDCOUPLING_USE_MPI=ON uses MPI containers.

According to set options and compilation environment, user may need to define some <prerequisite>_ROOT_DIR variables. For example if in SALOME environment:

export MEDFILE_ROOT_DIR=${MED3HOME}
export METIS_ROOT_DIR=$METISDIR
export SCOTCH_ROOT_DIR=$SCOTCHDIR
export BOOST_ROOT_DIR=$BOOST_ROOT
export GRAPHVIZ_ROOT_DIR=$GRAPHVIZHOME
export CPPUNIT_ROOT_DIR=$CPPUNIT_ROOT

If using MPI, the PARMETIS_ROOT_DIR variable should be set.