-<h3><a name="check_version_proc"></a>Notes on<font color="#ff0000">
-check products version</font> procedure</h3>
-Unfortunately under Linux platform there is no exact algorithm to
-identify the product's version. The information in this section gives
-an idea how the
-version is checked for the native/preinstalled products (this
-information refers to the base platform <span
- style="color: rgb(0, 0, 153);">Linux Mandrake
-10.1</span>; and the same algorithms are used for other platforms). <br>
-The general rule for all products is that the path to the binaries
-should be set via <span style="font-weight: bold;">PATH</span>
-environment variable, path to the libraries should be set via <span
- style="font-weight: bold;">LD_LIBRARY_PATH</span> variable and the
-python modules should be available via <span style="font-weight: bold;">PYTHONPATH</span>
-variable.<br>
-<span style="font-weight: bold;">Note:</span> the information given in
-this section refers to the prerequisite products for SALOME version
-3.2.0.<br>
-<ul>
- <li>gcc 3.4.1<br>
- </li>
-</ul>
-Version number is checked by <span style="font-weight: bold;">gcc
--dumpversion</span> command. <span style="font-weight: bold;">gcc</span>
-executable should be in the <span style="font-weight: bold;">PATH</span>
-environment variable. Version should
-be equal to the "3.4.1". It is recommended to use native gcc on
-Mandrake 10.1.<br>
-<ul>
- <li>tcl/tk 8.4.5</li>
-</ul>
-Version number for <span style="font-weight: bold;">tcl/tk</span> can
-be found in tclConfig.sh and tkConfig.sh files (<span
- style="font-weight: bold;">TCL_VERSION</span> and <span
- style="font-weight: bold;">TK_VERSION</span> variables
-correspondingly). Version number should be equal to "8.4" (release
-number is not checked). <br>
-Set <span style="font-weight: bold;">TCLHOME</span> environment
-variable to the root directory of tcl/tk installation.<br>
-It is recommended to use native tcl/tk on Mandrake 10.1. <span
- style="font-weight: bold;"></span>
-<ul>
- <li>boost 1.31.0</li>
-</ul>
-Version number is defined by <span style="font-weight: bold;">version.hpp</span>
-file which is part of the boost distribution. This file defines <span
- style="font-weight: bold;">BOOST_VERSION</span> macro which should be
-equal to the "103100". In addition the existence of boost libraries is
-checked. <br>
-Set <span style="font-weight: bold;">BOOSTDIR</span>
-environment variable if you have preinstalled version of
-boost.<br>
-<ul>
- <li>Python 2.3.4</li>
-</ul>
-Version number is checked by <span style="font-weight: bold;">python -V</span>
-command. <span style="font-weight: bold;">python</span> executable
-should be in the <span style="font-weight: bold;">PATH</span>
-environment variable. Version number should be equal to "2.3.4". It is
-recommended to use native Python on
-Mandrake 10.1.<br>
-Set <span style="font-weight: bold;">PYTHONHOME</span> environment
-variable if you have preinstalled version of Python.<br>
-<ul>
- <li>Swig 1.3.24</li>
-</ul>
-Version number is checked by <span style="font-weight: bold;">swig
--version</span> command. <span style="font-weight: bold;">swig</span>
-executable should be in the <span style="font-weight: bold;">PATH</span>
-environment variable. Version number should be equal to "1.3.24".<br>
-<ul>
- <li>Qt 3.3.3</li>
-</ul>
-Version number is defined by <span style="font-weight: bold;">qglobal.h</span>
-file which is part of the Qt distribution. This file defines <span
- style="font-weight: bold;">QT_VERSION_STR</span> macro which should be
-equal to "3.3.3". It is recommended to use native Qt on Mandrake 10.1.<br>
-Set <span style="font-weight: bold;">QTDIR</span> environment
-variable if you
-have preinstalled version of qt.<br>
-<ul>
- <li>msg2qm</li>
-</ul>
-<span style="font-weight: bold;">msg2qm</span> is Qt tool which is used
-to
-convert text *.po files to *.qm resource files. Unfortunately this tool
-is not included to the Linux distribution and provided only in Qt
-sources
-package. This is the reason why this tool is suppplied with the SALOME
-Installation Wizard.<br>
-There is no way to check the version number of msg2qm tool. Just set <span
- style="font-weight: bold;">MSG2QM_ROOT</span> environment
-variable if you have preinstalled
-version of msg2qm tool
-<ul>
- <li>Open CASCADE 6.1.0</li>
-</ul>
-Version number is defined by <span style="font-weight: bold;">Standard_Version.hxx</span>
-file which is part of the Open CASCADE distribution. This file defines <span
- style="font-weight: bold;">OCC_VERSION_MAJOR,</span> <span
- style="font-weight: bold;">OCC_VERSION_MINOR</span> and <span
- style="font-weight: bold;">OCC_VERSION_MAINTENANCE</span> macros which
-should refer to version 6.1.0.<br>
-Set <span style="font-weight: bold;">CASROOT</span> environment
-variable if you have preinstalled version of Open CASCADE.<br>
-<ul>
- <li>qwt 4.2.0/0.4.2</li>
-</ul>
-Version number is defined by <span style="font-weight: bold;">qwt_global.h</span>
-file which is part of the qwt distribution. This file defines <span
- style="font-weight: bold;">QWT_VERSION_STR</span> macro which should
-be
-equal to "4.2.0".<br>
-Set <span style="font-weight: bold;">QWTHOME</span> environment
-variable if you
-have preinstalled version of qwt.<br>
-<ul>
- <li>hdf 5-1.6.3</li>
-</ul>
-Version number is defined by <span style="font-weight: bold;">libhdf5.settings</span>
-file which is part of the <span style="font-weight: bold;">hdf5</span>
-distribution. Version should be equal to 1.6.3.<br>
-Set <span style="font-weight: bold;">HDF5HOME</span> environment
-variable if you
-have preinstalled version of hdf5.<br>
-<ul>
- <li>med 2.2.3</li>
-</ul>
-Unfortunately there is no formal way to check med version
-number. We check existense of libmed.so.1.0.2 library on the computer.
-If you have problem with preinstalled version of med, please, reinstall
-it.<br>
-Set <span style="font-weight: bold;">MED2HOME</span> environment
-variable if you
-have preinstalled version of med.<br>
-<ul>
- <li>Vtk 4.2.6</li>
-</ul>
-Unfortunately there is no formal way to check VTK version
-number. We just check existence of <span style="font-weight: bold;">libvtkCommon.so</span>
-library on the computer and hope that it is of version we need. If you
-have problem with preinstalled version of Vtk, please, reinstall it.<br>
-Set <span style="font-weight: bold;">VTKHOME</span> environment
-variable if you
-have preinstalled version of Vtk.<br>
-<ul>
- <li>OmniORB 4.0.5, OmniORBpy 2.5, OmniNotify 2.1</li>
-</ul>
-We just check existence of some omniORB libraries and executable on the
-computer, like <span style="font-weight: bold;">libomniORB4.so.0.5</span>,
-<span style="font-weight: bold;">_omnipymodule.so.2.4</span>, <span
- style="font-weight: bold;">libCOSNotify4.so.0.1</span> and <span
- style="font-weight: bold;">notifd</span>.<br>
-Set <span style="font-weight: bold;">OMNIORBDIR</span> environment
-variable if
-you have preinstalled version of omniORB products.<br>
-<ul>
- <li>sip 4.1</li>
-</ul>
-Version number is checked by <span style="font-weight: bold;">sip -V</span>
-command. <span style="font-weight: bold;">sip</span> executable should
-be in the <span style="font-weight: bold;">PATH</span>
-environment variable. Version number should be equal to "4.1".<br>
-Set <span style="font-weight: bold;">SIPDIR</span> environment
-variable to the
-directory where you have sip executable preinstalled.<br>
-<ul>
- <li>PyQt 3.13</li>
-</ul>
-Version number is defined by <span style="font-weight: bold;">pyqtconfig.py</span>
-Python module file which is part of the <span
- style="font-weight: bold;">PyQt</span> distribution. Version should be
-equal to "3.13".<br>
-Set <span style="font-weight: bold;">PYQTDIR</span>environment
-variable if you
-have preinstalled version of PyQt.
-<ul>
- <li>netgen 4.5</li>
-</ul>
-Unfortunarely we can't find anything about
-netgen version. We just check if <span style="font-weight: bold;">NETGENROOT</span>
-environment varible is set.<br>
-Set <span style="font-weight: bold;">NETGENROOT</span>
-environment
-variable if you have preinstalled version
-of netgen mesher.<br>
-<ul>
- <li>Numeric 23.7</li>
-</ul>
-Version number is checked by <span style="font-weight: bold;">python
--c
-'import Numeric; print Numeric.__version__'</span> command. <span
- style="font-weight: bold;">python</span> executable should be in the <span
- style="font-weight: bold;">PATH</span>
-environment variable and <span style="font-weight: bold;">Numeric</span>
-module should be avaible for the Python (for example it should be in
-the <span style="font-weight: bold;">PYTHONPATH</span> environment
-variable). Version number should be equal to "23.7". If you have
-problem with preinstalled version of Numeric 23.7, please,
-reinstall it.<br>
-Add the directory where <span style="font-weight: bold;"></span>you
-have preinstalled version of Numeric
-package to the <span style="font-weight: bold;">PYTHONHOME </span>environment
-variable.<br>
-<ul>
- <li>graphviz 2.2.1</li>
-</ul>
-Version number is checked by <span style="font-weight: bold;">dot -V</span>
-command. <span style="font-weight: bold;">dot</span> executable should
-be in the <span style="font-weight: bold;">PATH</span>
-environment variable. Version number should be equal to "2.2.1".<br>
-Add <span style="font-weight: bold;">graphviz</span> bin directory to
-the <span style="font-weight: bold;">PATH</span> environment variable.<br>
-<ul>
- <li>doxygen 1.4.6</li>
-</ul>
-Version number is checked by <span style="font-weight: bold;">doxygen
---version</span> command. <span style="font-weight: bold;">doxygen</span>executable
-should be in the <span style="font-weight: bold;">PATH</span>
-environment variable. Version number should be equal to "1.4.6".<br>
-<ul>
- <li><span style="font-weight: bold; color: rgb(0, 0, 153);">SALOME </span>module
- <span style="font-weight: bold;"></span><span
- style="font-weight: bold; color: rgb(0, 0, 153);">sources</span>
-(3.2.0).</li>
-</ul>
-For each SALOME module sources package (KERNEL, GUI, GEOM, etc...) <span
- style="font-weight: bold;">bin</span> directory contains file <span
- style="font-weight: bold;">VERSION</span> which defines version
-information.<br>
-Set <span style="font-weight: bold;"><MODULE>_SRC_DIR</span>
-environment variable for each SALOME <span style="font-weight: bold;">MODULE</span>
-sources package installed (where <span style="font-weight: bold;">MODULE</span>
-is KERNEL, GUI, GEOM, ...).<br>
-<ul>
- <li><span style="font-weight: bold; color: rgb(0, 0, 153);">SALOME </span>module
- <span style="font-weight: bold;"></span><span
- style="font-weight: bold; color: rgb(0, 0, 153);">binaries </span>(3.2.0)</li>
-</ul>
-For each SALOME module binaries package (KERNEL, GUI, GEOM, etc...) <span
- style="font-weight: bold;">bin/salome</span> directory contains file <span
- style="font-weight: bold;">VERSION</span> which defines version
-information.<br>
-Set <span style="font-weight: bold;"><MODULE>_ROOT_DIR</span>
-environment variable for each SALOME <span style="font-weight: bold;">MODULE</span>
-binaries package installed (where <span style="font-weight: bold;">MODULE</span>
-is KERNEL, GUI, GEOM, ...).<br>
-<p><b></b>If you have native products installed to different from
-default
-directories (not <b>/usr/bin</b>, <b>/usr/lib</b>...), it is
-recommended to follow above mentioned instructions. Or you should
-properly set <span style="font-weight: bold;">PATH</span> and <span
- style="font-weight: bold;">LD_LIBRARY_PATH</span> variables <b><font
- color="#ff0000">before</font></b>
-starting the Installation Wizard. Otherwise
-the installation script will fail to find preinstalled/native products.
-</p>
-<p><b>Note:</b> For some native products (e.g. gcc, Python) the rules
-of version
-checking are not so strict as described in the table. Only major and
-minor numbers of version
-should coincide with prerequisite. Newer version of the product can be
-used also. If some native product has version number larger than that
-required by
-the
-installation procedure, user will be prompted by the warning message
-like this: <i>"You have
-newer version of gcc installed
-on your computer than that is required (3.4.1). Continue?"</i>. You can
-press <i>"Yes"</i> button
-to proceed with the installation but in this case you should be aware
-of what you are doing.
-SALOME binaries (including other products) are compiled with the
-predefined prerequisites
-and most likely can not be run successfully if these products are not
-found.
-This can be helpful only if you plan to build all products from
-sources. <br>
-</p>
-<h3>
-<hr></h3>