MED Module Documentation

-User's Guide +User's Guide

MEDCoupling: User's Guide

diff --git a/dev/cmake/source/config.rst b/dev/cmake/source/config.rst index bcadedc..d63f832 100644 --- a/dev/cmake/source/config.rst +++ b/dev/cmake/source/config.rst @@ -25,7 +25,7 @@ The last point was however never tested in the SALOME context, and probably need In the SALOME context this logic offers the advantage to have a minimal specification on the prerequisites. Technically one just needs to set the _ROOT_DIR variables for the packages that were never found before, and to get "for free" what was already found in a dependent module (for example Qt4 in GUI, but not OmniORB as it was already used by KERNEL). This works thanks to the exposition of all the ROOT_DIR used by one module into its configuration file. This can then be automatically reused by a dependent module. Inspired from the CMake tutorial (http://www.cmake.org/Wiki/CMake/Tutorials/How_to_create_a_ProjectConfig.cmake_file) some -important module use this scheme and install the \*Config.cmake files facilitating the configuration of other dependent modules. Most important SALOME modules (KERNEL, GUI, MED) expose their configuration in such a way. +important module use this scheme and install the \*Config.cmake files facilitating the configuration of other dependent modules. Most important SALOME modules (KERNEL, GUI, FIELDS) expose their configuration in such a way. Guidelines diff --git a/dev/cmake/source/intro.rst b/dev/cmake/source/intro.rst index 66b822a..ea993ff 100644 --- a/dev/cmake/source/intro.rst +++ b/dev/cmake/source/intro.rst @@ -89,14 +89,14 @@ GUI module - on top of some of the KERNEL prerequisites, the following variables * QWT_ROOT_DIR: Qwt package * OPENGL_ROOT_DIR: OpenGL package -MED module - on top of some of the KERNEL and GUI prerequisites, the following variables are used: +FIELDS module - on top of some of the KERNEL and GUI prerequisites, the following variables are used: * MEDFILE_ROOT_DIR: MEDFile package * METIS_ROOT_DIR (optional): Metis package * PARMETIS_ROOT_DIR (optional): ParMetis package * SCOTCH_ROOT_DIR (optional): Scotch package -PARAVIS module - on top of some of the KERNEL, GUI and MED prerequisites, the following variables are used: +PARAVIS module - on top of some of the KERNEL, GUI and FIELDS prerequisites, the following variables are used: * PARAVIEW_ROOT_DIR: ParaView package * at present for a proper build of PARAVIS, the env variables LD_LIBRARY_PATH and PYTHONPATH should be set to contain the HDF5 and ParaView libraries. This is required since the configuration process itself uses a Python script in which the environment is not overriden:: diff --git a/dev/cmake/source/skeleton.rst b/dev/cmake/source/skeleton.rst index dc4cf6a..79d4b06 100644 --- a/dev/cmake/source/skeleton.rst +++ b/dev/cmake/source/skeleton.rst @@ -16,7 +16,7 @@ The root CMakeLists.txt should contain the following elements: * SALOME_BUILD_TESTS: wether the unit tests should be built * SALOME_BUILD_DOC: wether the documentation for the current module should be generated and installed - Other flags specific to the module might be added, and should then start with *SALOME_XYZ_* where is the module's name (MED for example). + Other flags specific to the module might be added, and should then start with *SALOME_XYZ_* where is the module's name (FIELDS for example). * Detection of the required prerequisites for the module. All prerequisites in SALOME are detected through a call to FIND_PACKAGE(SalomeXYZ ...). See section :ref:`package`:: diff --git a/index.html b/index.html index 3f3a6e3..5461f15 100644 --- a/index.html +++ b/index.html @@ -127,7 +127,7 @@

MED Module Documentation

FIELDS Module Documentation