<!DOCTYPE doctype PUBLIC "-//w3c//dtd html 4.0 transitional//en"><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
- <meta name="GENERATOR" content="Mozilla/4.73 [en] (WinNT; I) [Netscape]"><title>MED Module Documentation</title></head>
+ <meta name="GENERATOR" content="Mozilla/4.73 [en] (WinNT; I) [Netscape]"><title>FIELDS Module Documentation</title></head>
<body bgcolor="#ffffff" text="#000000" link="#0000ee" alink="#0000ee" vlink="#551a8b">
<div style="text-align: left; background-color: #175783; border: 1px solid; height: 80px; background-repeat: no-repeat; margin-bottom: 10px;">
</div>
<div align="center">
-<h1>MED Module Documentation</h1>
+<h1>FIELDS Module Documentation</h1>
</div>
<div align="center">
<p><img src="about.png" alt="about.png"></p>
<br><br>
-<big><a href="dev/MED/index.html">User's Guide</a></big>
+<big><a href="dev/FIELDS/index.html">User's Guide</a></big>
<br><br>
<big><a href="dev/MEDCoupling/index.html">MEDCoupling: User's Guide</a></big>
<br><br>
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
* 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::
* 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 <XYZ> 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 <XYZ> 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`::
<li><a href="GUI_index.html">GUI</a></li>
<li><a href="GEOM_index.html">Geometry</a></li>
<li><a href="SMESH_index.html">Mesh</a></li>
- <li><a href="MED_index.html">Med</a></li>
+ <li><a href="FIELDS_index.html">Fields</a></li>
<li><a href="PARAVIS_index.html">ParaVis</a></li>
<li><a href="YACS_index.html">YACS</a></li>
<li><a href="JOBMANAGER_index.html">JobManager</a></li>
