-<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 table below gives an idea how the
-version is checked for the preinstalled products for the Linux Mandrake
-10.1 platform. <br>
-
-<table nosave="" border="1" width="100%">
- <tbody>
- <tr nosave="">
- <th nosave="">
- <center><font size="+1">Product</font></center>
- </th>
- <th nosave="">
- <center><font size="+1">Algorithm of checking</font></center>
- </th>
- <th nosave="">
- <center><font size="+1">Preliminary steps before launching</font>
- <br>
- <font size="+1">of installation procedure</font></center>
- </th>
- <th nosave="">
- <center><font size="+1">Notes</font></center>
- </th>
- </tr>
- <tr>
- <td>gcc 3.4.1</td>
- <td><span style="font-weight: bold;">ver</span>=`gcc -dumpversion`</td>
- <td>
- <center>-</center>
- </td>
- <td><span style="font-weight: bold;">ver</span> should be 3.4.1.<br>
-It is recommended to use native gcc on Mandrake 10.1.<br>
- </td>
- </tr>
- <tr nosave="">
- <td>tcl 8.4.5</td>
- <td nosave=""><span style="font-weight: bold;">1)</span> check if
- <span style="font-weight: bold;">TCLHOME</span> variable is set<br>
- <span style="font-weight: bold;">2)</span> existence of tclsh8.4<br>
- <span style="font-weight: bold;">3)</span> existence of wish8.4 <br>
- <span style="font-weight: bold;">4)</span> existence of
-libtcl8.4.so <br>
- <span style="font-weight: bold;">5)</span> existence of
-libtk8.4.so<br>
- </td>
- <td>set <span style="font-weight: bold;">TCLHOME</span> if you
-have preinstalled version of tcl. <br>
-add a directory where libraries can be found to the <span
- style="font-weight: bold;">LD_LIBRARY_PATH</span><br>
- </td>
- <td>Unfortunately there is no more strict way to check the tcl
-version number.<br>
-It is recommended to use native tcl/tk on Mandrake 10.1.</td>
- </tr>
- <tr>
- <td valign="top">boost 1.31.0<br>
- </td>
- <td valign="top"><span style="font-weight: bold;">1)</span> check
-if <span style="font-weight: bold;">BOOSTDIR</span> variable is set.<br>
- <span style="font-weight: bold;">2)</span> <span
- style="font-weight: bold;">ver</span>=`egrep 'BOOST_VERSION [0-9]+'
-${BOOSTDIR}/boost/version.hpp | sed 's/.*BOOST_VERSION
-\([0-9]\+\)/\1/g'`<br>
- </td>
- <td valign="top">set <span style="font-weight: bold;">BOOSTDIR</span>
-if you have preinstalled version of
-boost<br>
- </td>
- <td valign="top">we use version.hpp file in the boost
-distribution to get the version information.<br>
- <span style="font-weight: bold;">ver</span> should be equal to
-103100.<br>
- </td>
- </tr>
- <tr>
- <td>Open CASCADE 5.2.3<br>
- </td>
- <td><span style="font-weight: bold;">1)</span> check if <span
- style="font-weight: bold;">CASROOT</span> variable is set<br>
- <span style="font-weight: bold;">2)</span> ver_major=`grep
-"!define OCC_VERSION_MAJOR"
-${CASROOT}/inc/Standard_Version.hxx | awk '{print $3}'`<br>
- <span style="font-weight: bold;">3)</span> ver_minor=`grep
-"!define OCC_VERSION_MINOR"
-${CASROOT}/inc/Standard_Version.hxx | awk '{print $3}'`<br>
- <span style="font-weight: bold;">4)</span> <span
- style="font-weight: bold;">ver</span>="$ver_major.$ver_minor"<br>
- <span style="font-weight: bold;">5)</span> Check existence of
-libStdPlugin.so in OpenCASCADE distribution,<br>
- </td>
- <td>set <span style="font-weight: bold;">CASROOT</span> if you
-have preinstalled version of Open CASCADE</td>
- <td>CASCADE's Standard_Version.hxx file provides version
-information.<br>
- <span style="font-weight: bold;">ver</span> should be equal to
-5.2.<br>
- <br>
-Unfortunately there is impossible to define release version number.
-Instead we check if libStdPlugin.so library exists: it is introduced in
-OpenCASCADE from version 5.2.2.<br>
- </td>
- </tr>
- <tr>
- <td>Python 2.3.4</td>
- <td><span style="font-weight: bold;">1)</span> <span
- style="font-weight: bold;">PYTHONHOME</span> variable should be set<br>
- <span style="font-weight: bold;">2)</span> isPython=`which
-python` <br>
- <span style="font-weight: bold;">3)</span> <span
- style="font-weight: bold;">ver</span>=`python -V`</td>
- <td>set <span style="font-weight: bold;">PYTHONHOME</span> to
-root Python distribution folder;<br>
-add the directory where python can be found to the <span
- style="font-weight: bold;">PATH</span> variable<br>
- </td>
- <td>Python should exist and <span style="font-weight: bold;">ver</span>
-should be equal to 2.3.4 <br>
-It is recommended to use native Python on Mandrake 10.1.</td>
- </tr>
- <tr>
- <td>Swig 1.3.24</td>
- <td><span style="font-weight: bold;">ver</span>=`swig -version
-2>&1 | grep -i version | awk '{ print $3 }' | sed -e
-'s/^\([0-9.]*\)\(.*\)/\1/'`</td>
- <td>add the directory where swig binary can be found to the <span
- style="font-weight: bold;">PATH</span> variable</td>
- <td>Swig should exist and <span style="font-weight: bold;">ver</span>
-should be equal to 1.3.24.</td>
- </tr>
- <tr>
- <td>Qt 3.3.3</td>
- <td><span style="font-weight: bold;">1) QTDIR</span> variable
-should be set.<br>
- <span style="font-weight: bold;">2) ver</span>=`grep
-"QT_VERSION_STR" ${QTDIR}/include/qglobal.h | sed -e
-'s%^#define QT_VERSION_STR\([[:space:]]*\)%%g' -e 's%\"%%g'`</td>
- <td>set <span style="font-weight: bold;">QTDIR</span> if you
-have preinstalled version of qt</td>
- <td>Qt's qglobal.h file provides version information: <span
- style="font-weight: bold;">ver</span> should
-be equal to 3.0.5.<br>
-It is recommended to use native Qt on Mandrake 10.1.</td>
- </tr>
- <tr>
- <td style="vertical-align: top;">msg2qm (Qt 3.3.3 compatible)<br>
- </td>
- <td style="vertical-align: top;"><span style="font-weight: bold;">MSG2QM_ROOT</span>
-variable should be set.<br>
- </td>
- <td style="vertical-align: top;">set <span
- style="font-weight: bold;">MSG2QM_ROOT</span> if you have preinstalled
-version of msg2qm tool<br>
- </td>
- <td style="vertical-align: top;">msg2qm is Qt tool used to
-convert text *.po files to *.qm resource files. Unfortunately this tool
-is not included to the Qt distribution and provided only in its sources
-package. We distribute this tool with the Installation Wizard.<br>
-In addition there is no way to check the version number of msg2qm tool.<br>
- </td>
- </tr>
- <tr>
- <td>Qwt 4.2.0/0.4.2</td>
- <td><span style="font-weight: bold;">1)</span> <span
- style="font-weight: bold;">QWTHOME</span> variable should be set.<br>
- <span style="font-weight: bold;">2)</span> check if
-libqwt.so.4.2.0 exists<br>
- </td>
- <td>set <span style="font-weight: bold;">QWTHOME</span> if
-you have preinstalled version of qwt</td>
- <td>Unfortunately there is no strict way to check qwt version
-number.<br>
-We try to find libqwt.so.4.2.0 in the ${<span style="font-weight: bold;">QWTHOME</span>}/lib
-folder. </td>
- </tr>
- <tr>
- <td>Hdf 5-1.6.3</td>
- <td><span style="font-weight: bold;">1) HDF5HOME</span> variable
-should be set.<br>
- <span style="font-weight: bold;">2)</span> existence of
-libhdf5.so.0.0.0 <br>
- <span style="font-weight: bold;">3)</span> existence of
-libhdf5.settings<br>
- <span style="font-weight: bold;">4)</span> <span
- style="font-weight: bold;">ver</span>=`grep "HDF5 Version:"
-${HDF5HOME}/lib/libhdf5.settings | awk
-'{print $3}'`</td>
- <td>set <span style="font-weight: bold;">HDF5HOME</span> if you
-have preinstalled version of hdf</td>
- <td>We try to find libhdf5.so.0.0.0 and libhdf5.settings in
-${<span style="font-weight: bold;">HDF5HOME</span>}/lib folder. <br>
-File libhdf5.settings contains the following version information: <br>
-HDF5 Version: 1.6.3</td>
- </tr>
- <tr>
- <td>Med 2.2.2</td>
- <td><span style="font-weight: bold;">1) MED2HOME</span> variable
-should be set.<br>
- <span style="font-weight: bold;">2)</span> existence of
-libmed.so.1.0.1</td>
- <td>set <span style="font-weight: bold;">MED2HOME</span> if you
-have preinstalled version of med</td>
- <td>Unfortunately there is no strict way to check med version
-number.<br>
-We try to find libmed.so.1.0.1 in ${<span style="font-weight: bold;">MED2HOME</span>}/lib
-folder. <br>
-If you have problem with preinstalled version of med reinstall it.</td>
- </tr>
- <tr>
- <td>Vtk 4.2.6</td>
- <td><span style="font-weight: bold;">1) VTKHOME</span> variable
-should be set.<br>
- <span style="font-weight: bold;">2)</span> existence of
-libvtkCommon.so</td>
- <td>set <span style="font-weight: bold;">VTKHOME</span> if you
-have preinstalled version of vtk</td>
- <td>Unfortunately there is no strict way to check VTK version
-number.<br>
-We try to find libvtkCommon.so in ${<span style="font-weight: bold;">VTKHOME</span>}/lib/vtk
-folder. <br>
-If you have problem with preinstalled version of vtk reinstall it.</td>
- </tr>
- <tr>
- <td valign="top">Netgen 4.3<br>
- </td>
- <td valign="top"><span style="font-weight: bold;">NETGENROOT</span>
-variable should be set. </td>
- <td valign="top">set <span style="font-weight: bold;">NETGENROOT</span>
-if you have preinstalled version
-of Netgen.<br>
- </td>
- <td valign="top">Unfortunarely we can't find anything about
-netgen version.<br>
-We just check if <span style="font-weight: bold;">NETGENROOT</span>
-environment varible is set.<br>
- </td>
- </tr>
- <tr>
- <td>OmniORB 4.0.5, <br>
-OmniORBpy 2.5, <br>
-OmniNotify 2.1</td>
- <td><span style="font-weight: bold;">1) OMNIORBDIR</span>
-variable should be set.<br>
- <span style="font-weight: bold;">2)</span> existence of
-libomniORB4.so.0.5 <br>
- <span style="font-weight: bold;">3)</span> existence of
-_omnipymodule.so.2.4 <br>
- <span style="font-weight: bold;">4)</span> existence of
-libCOSNotify4.so.0.1 <br>
- <span style="font-weight: bold;">5)</span> existence of notifd<br>
- </td>
- <td>set <span style="font-weight: bold;">OMNIORBDIR</span> if
-you have preinstalled version of omni</td>
- <td>We try to find several omni libraries and binaries in the ${<span
- style="font-weight: bold;">OMNIORBDIR</span>}/lib and ${<span
- style="font-weight: bold;">OMNIORBDIR</span>}/bin directories.<br>
- <br>
- </td>
- </tr>
- <tr>
- <td>Numeric 23.7</td>
- <td><span style="font-weight: bold;">ver</span>=`python -c
-'import Numeric; print Numeric.__version__'
-2>/dev/null`</td>
- <td>add the directory where <span style="font-weight: bold;"></span>you
-have preinstalled version of Numeric
-package to your <span style="font-weight: bold;">PYTHONHOME </span>variable<span
- style="font-weight: bold;"><br>
- </span></td>
- <td>If you have problem with preinstalled version of Numeric 23.7
-reinstall it.</td>
- </tr>
- <tr>
- <td>Sip 4.1<br>
- </td>
- <td><span style="font-weight: bold;">1) SIPDIR</span> variable
-should be set.<br>
- <span style="font-weight: bold;">2) ver</span>=`${SIPDIR}/sip -V
-| awk '{print $1}'`</td>
- <td>set <span style="font-weight: bold;">SIPDIR</span> to
-directory where you have sip preinstalled</td>
- <td><span style="font-weight: bold;">ver</span> should be equal
-to 4.1. <br>
- <br>
- </td>
- </tr>
- <tr>
- <td>PyQt 3.13</td>
- <td><span style="font-weight: bold;">1) PYQTDIR</span> variable
-should be set.<br>
- <span style="font-weight: bold;">2)</span> existence of qt.so
-library<br>
- </td>
- <td>set <span style="font-weight: bold;">PYQTDIR</span> to
-directory where you have PyQt preinstalled</td>
- <td>Unfortunately we can't check exact PyQt version number. <br>
-We just try to find qt.so in ${<span style="font-weight: bold;">PYQTDIR</span>}.
- <br>
- </td>
- </tr>
- <tr>
- <td>HappyDoc 2.1</td>
- <td><span style="font-weight: bold;">1)</span> existence of
-happydoc <br>
- <span style="font-weight: bold;">2)</span> <span
- style="font-weight: bold;">ver</span>=`happydoc | grep "HappyDoc
-version 2.1"`</td>
- <td>add the directory where you have HappyDoc
-installed to your <span style="font-weight: bold;">PATH</span>
-variable.<br>
- </td>
- <td>We try to find happydoc in ${<span style="font-weight: bold;">PATH</span>}.
- <br>
- <span style="font-weight: bold;">ver</span> should not be empty. <br>
- <br>
- <span style="font-weight: bold;">Note:</span> this product is not
-obligatory for SALOME compilation.<br>
- </td>
- </tr>
- <tr>
- <td>Doxygen 1.3.7</td>
- <td><span style="font-weight: bold;">1)</span> existence of
-doxygen <br>
- <span style="font-weight: bold;">2)</span> existence of doxytag <br>
- <span style="font-weight: bold;">3)</span> existence of doxywizard<br>
- <span style="font-weight: bold;">4)</span> <span
- style="font-weight: bold;">ver</span>=`doxygen --version`</td>
- <td>add the directory where you have doxygen binaries
-preinstalled to the <span style="font-weight: bold;">PATH</span>
-variable.</td>
- <td>doxygen, doxytag, doxywizard binaries should
-exist; <span style="font-weight: bold;">ver</span> should be equal to
-1.3.7.<br>
- <br>
-If you have problem with preinstalled version of doxygen
-reinstall it. <br>
- <br>
-It is recommended to use native doxygen on Mandrake 10.1.<br>
- </td>
- </tr>
- <tr>
- <td>Graphviz 2.2.1<br>
- </td>
- <td><span style="font-weight: bold;">1)</span> existence of dot
-binary.<br>
- <span style="font-weight: bold;">2)</span> <span
- style="font-weight: bold;">ver</span>=`dot -V 2>&1 | awk
-'{print $3}'`</td>
- <td>add graphviz bin directory to the <span
- style="font-weight: bold;">PATH</span> environment variable</td>
- <td>We try to find dot program in the ${<span
- style="font-weight: bold;">PATH</span>}.<br>
- <span style="font-weight: bold;">ver</span> should be equal to
-2.2.1.<br>
- </td>
- </tr>
- <tr>
- <td><span style="font-weight: bold;">MODULE</span> binaries<br>
-(where <span style="font-weight: bold;">MODULE</span> = KERNEL, GUI,
-GEOM, ...)<br>
- </td>
- <td><span style="font-weight: bold;">1) MODULE_ROOT_DIR</span>
-variable should be set<br>
- <span style="font-weight: bold;">2)</span> existence of VERSION
-file <br>
- <span style="font-weight: bold;">3) ver</span>=`cat ${<span
- style="font-weight: bold;">MODULE_ROOT_DIR</span>}/bin/salome/VERSION
-| awk -F: '{print $NF}' |
-tr -d '[:space:]'`</td>
- <td>set <span style="font-weight: bold;">MODULE_ROOT_DIR</span>
-if you have preinstalled binaries of <span style="font-weight: bold;">MODULE</span>
-version 3.0.0.</td>
- <td><span style="font-weight: bold;">MODULE</span> binaries
-should exist and <span style="font-weight: bold;">ver</span> should be
-equal to 3.0.0.<br>
- </td>
- </tr>
- <tr>
- <td><span style="font-weight: bold;">MODULE</span> sources<br>
-(where <span style="font-weight: bold;">MODULE</span> = KERNEL, GUI,
-GEOM, ...)<br>
- </td>
- <td><span style="font-weight: bold;">1)</span> existence of <span
- style="font-weight: bold;">MODULE_SRC_DIR</span> <br>
- <span style="font-weight: bold;">2)</span> existence of VERSION
-file <br>
- <span style="font-weight: bold;">3) ver</span>=`cat ${<span
- style="font-weight: bold;">MODULE_SRC_DIR</span>}/bin/VERSION | awk
--F: '{print $NF}' | tr -d
-'[:space:]'`</td>
- <td>set <span style="font-weight: bold;">MODULE_SRC_DIR</span>
-if you have preinstalled sources of <span style="font-weight: bold;">MODULE</span>
-version 3.0.0.<br>
- </td>
- <td><span style="font-weight: bold;">MODULE</span> sources should
-exist and ver should be equal to 3.0.0.</td>
- </tr>
- </tbody>
-</table>
-<p><b>Note:</b> For native products installation procedure sets proper
-environment variables itself, and you do not need to set such variables
-like, e.g. <b>TCLHOME</b> or <b>PYTHONHOME</b>. <br>
-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 description. Or you should set properly <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 Installation Wizard. Otherwise
-installation script will fail to find preinstalled 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. Release number can be larger. It is
-done for making a possibility
-to use native products for newer versions of Linux.
-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 procede with the installation but in this case you should be aware
-of what you are doing.
-SALOME binaries (inluding 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 only helpful if you intend to build all products from
-sources.</p>
-<h3>
-<hr></h3>
