-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
+<!DOCTYPE html 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.8 [en] (X11; U; Linux 2.4.18-14 i686) [Netscape]">
- <meta name="Author" content="Vadim SANDLER (v-sandler@opencascade.com)">
- <title>SALOME Professional v1.2 Installation Wizard Help</title>
+ <meta http-equiv="Content-Type"
+ content="text/html; charset=iso-8859-1">
+ <meta name="GENERATOR"
+ content="Mozilla/4.8 [en] (X11; U; Linux 2.4.18-14 i686) [Netscape]">
+ <meta name="Author"
+ content="Vadim SANDLER (v-sandler@opencascade.com)">
+ <title>SALOME 3 Installation Wizard Help</title>
+ <meta content="Vadim SANDLER" name="author">
</head>
-<body text="#000000" bgcolor="#FFFFE5" link="#0000EE" vlink="#551A8B" alink="#FF0000">
+<body style="color: rgb(0, 0, 0); background-color: rgb(255, 255, 229);"
+ alink="#ff0000" link="#0000ee" vlink="#551a8b">
-<center><table WIDTH="100%" NOSAVE >
-<tr NOSAVE>
-<td NOSAVE>
-<h1>
-<a href="http://www.opencascade.com"><img SRC="logocorp.png" BORDER=0 height=47 width=139></a></h1>
-</td>
-
-<td>
<center>
-<h1>
-<font size=+4><font color="#000099">SALOME Professional Installation Wizard
-Help</font> </font></h1></center>
-</td>
-
-<td>
-<div align=right><a href="http://www.opencascade.org/SALOME/"><img SRC="application.png" BORDER=0 height=45 width=104></a></div>
-</td>
-</tr>
-</table></center>
-
-<div align=right><b><font color="#000099">updated for the version 1.2d</font></b></div>
-
+<table nosave="" width="100%">
+ <tbody>
+ <tr nosave="">
+ <td nosave="">
+ <h1><a href="http://www.opencascade.com"><img src="logocorp.png"
+ border="0" height="47" width="139"> </a></h1>
+ </td>
+ <td>
+ <center>
+ <h1><font size="+4"><font color="#000099">SALOME Installation
+Wizard Help</font> </font></h1>
+ </center>
+ </td>
+ <td>
+ <div align="right"><a href="http://www.opencascade.org/SALOME/"><img
+ src="application.png" border="0" height="47" width="109"> </a></div>
+ </td>
+ </tr>
+ </tbody>
+</table>
+</center>
+<div align="right"><b><font color="#000099">updated for the version </font><font
+ color="#ff0000">3.0.0</font></b></div>
<hr>
<ul>
-<li>
-<a href="#install_from_wizard">Installing products with the Installation
-Wizard</a></li>
-
-<li>
-<a href="#check_version_proc">Notes on check products version procedure</a></li>
-
-<li>
-<a href="#pick_up_env">Pick up the environment</a></li>
-
-<li>
-<a href="#xml_files">Modifying XML configuration file</a></li>
-
-<li>
-<a href="#new_products">Implementing installation scripts for the new products</a></li>
+ <li> <a href="#install_from_wizard">Installing products with the
+Installation Wizard</a></li>
+ <li> <a href="#check_version_proc">Notes on check products version
+procedure</a></li>
+ <li> <a href="#pick_up_env">Pick up the environment</a></li>
+ <li> <a href="#xml_files">Modifying XML configuration file</a></li>
+ <li> <a href="#new_products">Implementing installation scripts for
+the new products</a></li>
</ul>
-
<h3>
-
<hr></h3>
-
-<h3>
-<a NAME="install_from_wizard"></a>Installing products with the <font color="#FF0000">Installation
-Wizard</font></h3>
-You can run the Installation Wizard in two modes. It's root directory contains
-python script runInstall.py:
-<p><b>[ python ] runInstall [ -g | b ] [ -f <xml-file> ] [ -t <target-dir>
-] [ -tmp <tmp-dir> ]</b>
-<p><b>-g </b>
-Runs the Installation Wizard in the GUI mode. In this case only <xml-file>
-key is taken into account. This option is used by default.
-<br><b>-b </b>
-Runs the Installation Wizard in the batch mode.
-<br><b>-f <xml-file> </b> The configuration
-file to be used by the Installation Wizard. If this parameter is
-missed then the script tries to define the <i>Red Hat </i>version and use
-corresponding xml file. For examle, for the <i>Red Hat 8.0</i> <b>config_RedHat8_0.xml</b>
-file is supposed to be used by default. If the appropriate file is not
-found, <b>config.xml</b> is used by default.
-<br><b>-t <target-dir></b> The target directory, SALOME products
-to be installed to. If used, overloads target directory, described in the
-configuration file.
-<br><b>-tmp <tmp-dir></b> The directory, which is used to contain
-temporary files. If used, overloads temporary directory, described
-in the configuration file.
-<p>So, to run the Installation Wizard in the GUI mode, just type <b>runInstall</b>.
-<p>The installation procedure can support some different Linux platforms
-(currently it provides configuration scripts for <i>RedHat-7.1</i> and
-<i>RedHat-8.0</i>)
-and various number of products.
-<br>The using of configuration xml files gives flexible way to modify the
-list of products to be installed by the Installation Wizard without changing
-program's source code. Just create your own configuration file and implement
-installation scripts for products you want to be provided by Wizard. See
-<a href="#xml_files">modifying
-XML configuration file</a> and <a href="#new_products">implementing installation
-scripts for the new products</a> for more information.
-<p>The <font color="#FF0000">Installation Wizard</font> was built with
-using of the <b><i>Qt </i></b>library. The program contains several
-pages. To navigate between pages use <i>"Next"</i> and <i>"Back"</i> buttons
-in the lower part of the wizard window. <i>"Cancel"</i> button closes dialog
-window and quits the installation procedure. To invoke this help information
+<h3> <a name="install_from_wizard"></a>Installing products with the <font
+ color="#ff0000">Installation Wizard</font></h3>
+The Installation Wizard can be launched in two modes: gui and batch. <br>
+The root directory of the Installation Wizard
+contains python script <span style="font-weight: bold;">runInstall</span>.
+To run the Installation Wizard just type <b>runInstall</b> in terminal
+window:<br>
+<p><b>[ python ] runInstall [ -g | -b ] [ -f <xml-file> ] [ -t
+<target-dir> ] [ -tmp <tmp-dir> ]</b> </p>
+<p><b>-g</b><br>
+ Runs the Installation Wizard in the
+GUI
+mode (default option). In this case only<span style="font-weight: bold;">
+<xml-file></span> key is taken into account.
+Other parameters are ignored. <br>
+<b>-b</b><br>
+ Runs the Installation Wizard in
+command-line mode. <br>
+<b>-f <xml-file></b><br>
+ The configuration file to be used by
+the
+Installation Wizard. If this parameter is missed then the script
+tries
+to define the <i>Linux </i>version and uses corresponding xml file.
+For
+examle, for the <i>Linux Mandrake 10.1</i> <b>config_Mandrake10_1.xml</b>
+file
+is supposed to be used by default. If the appropriate file is not
+found, <b>config.xml</b>
+is used by default. This file refers to the basic target platform
+which is Mandrake 10.1 for SALOME 3.0 and higher. If config.xml file is
+also not found the warning message box is shown and Installation Wizard
+quits.<br>
+<b>-t <target-dir></b><br>
+ The target directory, SALOME platform
+to
+be installed to. If used, overloads default target directory, given in
+the
+configuration
+xml file (usually <span style="font-weight: bold;">/salome</span>, see
+<a href="#xml_files">here</a>). <br>
+<b>-tmp <tmp-dir></b><br>
+ The directory, which is used to
+contain temporary files. If used, overloads default temporary
+directory,
+given in the
+configuration xml file (usually <span style="font-weight: bold;">/tmp</span><span
+ style="font-weight: bold;"></span>, see <a
+ href="readme.html#xml_files">here</a>).<br>
+<b>-h</b><br>
+ Prints help information. <br>
+</p>
+<p>The installation procedure can support some different Linux
+platforms
+and various number of products. As it was mentioned above the basic
+target platform for SALOME 3.0.0 and higher is <i>Linux Mandrake 10.1</i>.<br>
+The using of configuration xml files gives flexible way to modify the
+list of products to be installed by the Installation Wizard without
+changing program's source code. Just create your own configuration file
+and implement installation scripts for products you want to be provided
+by Wizard. See <a href="#xml_files">modifying XML configuration file</a>
+and <a href="#new_products">implementing installation scripts for the
+new products</a> for more information. </p>
+<p>The <font color="#ff0000">Installation Wizard</font> was built with
+using of the <span style="font-style: italic;">Trolltech's</span> <b><i>Qt
+3.0.5 </i></b>library. The program contains
+several pages. To navigate between pages use <i>"Next"</i> and <i>"Back"</i>
+buttons in the
+lower part of the wizard window. <i>"Cancel"</i> button closes dialog
+window
+and quits the installation procedure. To invoke this help information
click
-<i>"Help"</i> button.
+<i>"Help"</i> button. </p>
<p>Skip the first <i>"Introduction"</i> page by pressing <i>"Next"</i>
-button.
-<p>In the second page you are proposed to enter the target directory where
-all selected products will be installed to. You can also press <i>"Browse..."</i>
-button and choose the folder for installation using standard <b><i>Qt</i></b>
-browse directory dialog box.
-<br>If the directory you want to install products does not exist you will
+button:
+</p>
+<center><a name="IntroPage"></a><br>
+<img alt="Intro page" src="intropage.png"
+ style="width: 586px; height: 390px;">
+<p><b>Figure 1:</b> "Introduction" page</p>
+</center>
+<p>In the second page you are proposed to enter the target directory
+where all selected products should be installed to. You can also press <i>"Browse..."</i>
+button and choose the folder for installation using standard <b><i>Qt</i></b>'s
+browse directory dialog box. <br>
+If the directory you want to install products does not exist you will
be prompted to confirm directory creation. If you type wrong directory
-path, or if you have no permission for the directory you use, the corresponding
-message box will raise.
-<p>The Installation Wizard has two modes of the installation: basic and
-advanced. In the basic mode it is necessary just to enter target directory.
-If you want to use advanced mode, click <i>"More..."</i> button.
+path, or if you have no permission for the directory you use, the
+corresponding message box will raise. </p>
+<p>The Installation Wizard has two modes of the installation: basic
+(default) and
+advanced. In the basic mode it is necessary just to enter target
+directory. If you want
+to use advanced mode, click <i>"More..."</i> button. </p>
<p>In the advanced mode you have the possibility to select products to
-be installed (see <a href="#ProductPage">Fig.1</a> ). Each product has
-several options of installation: you have a possibility to use native products,
-install already precompiled binaries, build product from the sources or
-not installed at all. Possible options and default choice are provided
-by the configuration file. You can mark the products, you want to install,
-by clicking the corresponding radiobuttons in the list view in the left
-part of the page. Note that some products can be installed only together
-with other products (or these prerequisite products should be already installed
-on your computer). The installation procedure has a special feature to
-automatically mark these products in the list view. For example, in order
-to install <b><i>pyqt</i></b> it's necessary to have
-<b><i>gcc, python</i></b>,<b><i>
-qt</i></b> and
-<b><i>sip</i></b> installed. Therefore all these products
-will be marked when you check on
-<b><i>pyqt</i></b>. This feature can be
-switched off by clicking <i>"Auto set prerequisites products"</i> checkbox.
-<br>Special button in the right part of the page - <i>"Unselect All" </i>-
-allows to reset quickly all products to the <i>"not install"</i> state.
-<br>If you want to use native Linux Red Hat 8.0 products (these are gcc,
-tcl, Python, Qt, Sip and PyQt), select <i>"use native" </i>option.
+be installed (see <a href="#ProductPage">Fig.2</a> ). Each product can
+have several options of installation: you have a possibility to use
+native products, install already precompiled binaries, build product
+from the sources or not install it at all. Possible options and default
+choice are provided by the configuration file. You can mark the
+products you want to install by clicking the corresponding
+radiobuttons in the list view in the left part of the page. Note that
+some products can be installed only together with other products (or
+these prerequisite products should be already installed on your
+computer). The installation procedure
+has a special feature to automatically mark these products in the list
+view.
+For example, in order to install <b><i>PyQt</i></b> it's necessary to
+have
+<b><i>gcc, Python</i></b>,<b><i> Qt</i></b> and <b><i>Sip</i></b>
+installed.
+Therefore all these products will be marked when you check on <b><i>PyQt</i></b>.
+This feature can be switched off by clicking <i>"Auto set
+prerequisites products"</i> checkbox. <br>
+Special button in the right part of the page - <i>"Unselect All" </i>-
+allows to reset quickly all products to the <i>"not install"</i>
+state. <br>
+If you want to use native products (like <span
+ style="font-weight: bold;">gcc</span>, <span
+ style="font-weight: bold;">tcl</span>, etc.), select <i>"use native" </i>option.
+</p>
+<p>There are also two checkboxes on this page: <i>"SALOME sources"</i>
+and <i>"SALOME binaries"</i>.
+These three-state checkboxes allow quick selecting/unselecting SALOME
+itself packages
+for the installation.</p>
<p>The box at the right side of the page displays the information about
-currently highlighted product: name, version, required disk space, temporary
-files disk space and list of prerequisites.
-<center><a NAME="ProductPage"></a>
-<br><img SRC="productpage.png" height=523 width=566>
-<p><b>Figure 1:</b> "Installation settings" page in the advanced mode</center>
-
-<p>The <i>"Total disk space required:"</i> field displays how much disk
-space on the hard drive is required for installation of selected products.
-<br><b>Note: </b>Please, take into account that displayed amount of required
-disk space is approximate and may differ when you install products on your
-hard drive.
-<p>Installation procedure uses a special directory to store temporary files.
-The <i>"Space for temporary files:"</i> field shows the information about
-required disk space on the hard drive for extracting and compiling of the
-selected products. You can change the default directory - just type path
+currently highlighted product: name, version, short description (if
+provided in XML file), required
+disk space, disk space required for temporary files, list of
+prerequisites and current user
+choice.
+</p>
+<center><a name="ProductPage"></a><br>
+<img src="productpage.png" alt="Products page"
+ style="width: 586px; height: 589px;">
+<p><b>Figure 2:</b> "Installation settings" page in the advanced mode</p>
+</center>
+<p>The <i>"Total disk space required:"</i> field displays how much
+disk space on the hard drive is required for installation of selected
+products. <br>
+<b>Note: </b>Please, take into account that displayed amount of
+required disk space is approximate and may differ when you install
+products on your hard drive. </p>
+<p>The installation procedure uses a special directory to store
+temporary files. The <i>"Space for temporary files:"</i> field shows
+the information about required disk space on the hard drive for
+extracting and compiling of the selected products. You can change the
+default directory - just type path
to the folder you want to use or click on the corresponding <i>"Browse..."</i>
-button.
-<p>The installation procedure also checks available disk space on the selected
-directories according to the products selected. If there is no enough disk
-space on your hard drive you will see the corresponding error message box.
-<p><b>Note: </b>Unfortunately, the configure procedure has a very annoying
-bug under Linux platform. The directory should be obligatory entered without
-spaces. For example, the configure procedure for <b><i>gcc</i></b> won't
+button. <br>
+<span style="font-weight: bold;">Note:</span> actually temporary files
+are stored not in the directory entered by user. The Installation
+Wizard creates in this directory an additional one folder named
+something like INSTALLWORK<span style="font-weight: bold;">XXXXX</span>
+where XXXXX is unique number. This allows to launch several
+Installation Wizards simultaneously. This temporary directory is
+removed automaticaly when the installation finishes.<br>
+</p>
+<p>The installation procedure also checks available disk space on the
+selected directories according to the products selected. If there is no
+enough disk space on your hard drive you will see the corresponding
+error message box. </p>
+<p><b>Note: </b>Unfortunately, the configure procedure has a very
+annoying bug under Linux platform. The directory should be obligatory
+entered without spaces. For example, the configure procedure for <b><i>gcc</i></b>
+won't
work if you pass the following parameter: <i>--prefix="/New Folder 1"</i>.
-<b>Therefore
-you are strongly recommended not to use directory names containing spaces.</b>
-<p>To proceed further click <i>"Next"</i> button. At this moment program
+<b>Therefore you are strongly recommended not to use directory names
+containing
+spaces.</b> </p>
+<p>To proceed further click <i>"Next"</i> button. At this moment
+program
will make some tests to check installation settings: if there is enough
-disk space on the hard drive, if native products are preinstalled, dependencies
-(prerequisites) for each product you have selected to be installed.
-If any test fails you will see corresponding warning message box. Otherwise
-wizard will follow to the next page:
+disk
+space on the hard drive, if native products are preinstalled,
+dependencies
+(prerequisites) for each product you have selected to be
+installed.
+If any test fails you will see the corresponding warning message box.
+Otherwise
+wizard will follow to the next page: </p>
<center>
-<p><a NAME="ChoicePage"></a>
-<br><img SRC="choicepage.png" height=523 width=566><b></b>
-<p><b>Figure 2:</b> "Check your choice" page</center>
-
-<p>This page summarizes the installation settings you've made on the previous
-pages. You can check again your choice to change it if necessary.
-<br>When you are sure that everything is OK, press <i>"Next"</i> button
-to follow to the <a href="#ProgressPage">next page</a>.
-<center><a NAME="ProgressPage"></a>
-<br><img SRC="progresspage.png" height=523 width=566><b></b>
-<p><b>Figure 3:</b> "Installation progress" page</center>
-
+<p><a name="ChoicePage"></a><br>
+<img src="choicepage.png" alt="Choice page"
+ style="width: 586px; height: 589px;"> </p>
+<p><b>Figure 3:</b> "Check your choice" page</p>
+</center>
+<p>This page summarizes the installation settings you've made on the
+previous pages. You can check again your choice to change it if
+necessary. <br>
+When you are sure that everything is OK, press <i>"Next"</i> button to
+follow to the <a href="#ProgressPage">next page</a>. </p>
+<center><a name="ProgressPage"></a><br>
+<img src="progresspage.png" alt="Progress page"
+ style="width: 586px; height: 589px;">
+<p><b>Figure 4:</b> "Installation progress" page</p>
+</center>
<p>To start installation of the selected products click <i>"Start"</i>
button. It launches the shell installation script and you will be able
to see the output of the script in the topmost dialog's frame. In case
-of any installation problems (for example, you have accidentally removed
-the temporary directory) the script will ask you:
-<i>"Would you like to
-continue : (Y,N) ?"</i>. You can answer this question by typing [Y] or
-[N] in the middle text edit control frame.
-<br><b>Note:</b> press [Enter] when you finish typing data.
-<p>The <i>"Installation Status"</i> frame window shows you the progress
-of installation. It contains a list of all selected products with brief
-descriptions. "<font color="#FF0000">Waiting</font>" description means
-that installation of this product have not started yet. Currently installing
-product is marked as "<font color="#FF9900">Processing</font>". All installed
-products have "<font color="#33FF33">Completed</font>" description.
-<p>You can abort installation and close the installation procedure using
-<i>"Cancel"</i>
-button. It sends the signal "SIGTERM" to the shell script. The script has
-a signal handler and will try to clear all temporary files. The process
-of removing temporary files can take some time, so the installation wizard
-will wait 3 seconds before closing.
-<p>At the end of installation (all selected products have been installed
-successfully) you can go back to the previous pages to start a new installation
-or click <i>"Next"</i> button to go the Readme page:
+of any installation problems (for example, you have accidentally
+removed the temporary directory) the script will ask you: <i>"Would
+you like to continue : (Y,N) ?"</i>. You can answer this question by
+typing [Y] or [N] in the middle text edit control frame. <br>
+<b>Note:</b> press [Enter] when you finish typing data. </p>
+<p>The <i>"Installation Status"</i> frame window shows you the
+progress of installation. It contains a list of all selected products
+with brief descriptions. "<font color="#ff0000">Waiting</font>"
+description means that installation of this product have not started
+yet. Currently installing product is marked as "<font color="#ff9900">Processing</font>".
+All installed products have "<font color="#33ff33">Completed</font>"
+description. </p>
+<p>You can abort installation and close the installation procedure
+using
+<i>"Cancel"</i> button. It sends the signal "SIGTERM" to the shell
+script.
+The script has a signal handler and will try to clear all temporary
+files.
+The process of removing temporary files can take some time, so the
+installation
+wizard will wait 3 seconds before closing. </p>
+<p>At the end of installation (all selected products have been
+installed
+successfully) you can go back to the previous pages to start a new
+installation
+or click <i>"Next"</i> button to go the Readme page: </p>
<center>
-<p><a NAME="readmepage"></a>
-<br><img SRC="readmepage.png" height=523 width=566>
-<p><b>Figure 4:</b> "Finish installation" page</center>
-
-<p>In this page you can read important information about the Instalation
-Wizard itself and some hints: how to run and test SALOME or how to build
+<p><a name="readmepage"></a><br>
+<img src="readmepage.png" alt="Readme page"
+ style="width: 586px; height: 589px;"> </p>
+<p><b>Figure 5:</b> "Finish installation" page</p>
+</center>
+<p>In this page you can read important information about the
+Instalation
+Wizard itself and some hints: how to run and test SALOME or how to
+build
SALOME from the sources. This is the contents of the README file which
-you can find in the root directory of the Installation Wizard.
-<br>You can also launch SALOME Desktop from this page by clicking <i>"Launch
-SALOME" </i>button.
-<p>During the process of installation the script creates some environment
-files to simplify procedure of launching SALOME. These shell scripts set
-all necessary environment variables for all products you have installed.
-To learn how installation scripts collects the environment, see <a href="#pick_up_env">
-here</a>. These files are: <b>salome.csh</b> + <b>salome.sh</b> in the
-<b><i>SALOME
-PRO sources</i></b> and <b><i>SALOME PRO binaries</i></b> root directories
-and <b>env_products.csh</b> + <b>env_products.sh
-</b>in the target directory.
-<p>
+you
+can find in the root directory of the Installation Wizard. <br>
+You can also launch SALOME Desktop from this page by clicking <i>"Launch
+SALOME" </i>button. </p>
+<p><a name="env_files"></a>During the process of installation the
+script creates some
+environment files to simplify procedure of launching SALOME. These
+shell scripts set
+all necessary environment variables for all products you have
+installed.
+To learn how installation scripts collects the environment, see <a
+ href="#pick_up_env"> here</a>. These files are: <b>salome.csh</b> + <b>salome.sh</b>
+in the <span style="font-style: italic;"><span
+ style="font-weight: bold;">KERNEL module</span></span><b><i> sources</i></b>
+and <span style="font-style: italic;"><span style="font-weight: bold;">KERNEL
+module</span></span><b><i> binaries</i></b> root directories and <b>env_products.csh</b>
++ <b>env_products.sh </b>in the target directory.<br>
+</p>
+<span style="font-weight: bold;">Note:</span> <b>salome.(c)sh</b> and <b>env_products.(c)sh
+files</b> are slightly different: env_products.* files are optimized to
+be used for the building of SALOME modules from sources (see <span
+ style="font-weight: bold;">README </span>file provided with the
+installation procedure on th CD). The salome.* files are optimized for
+the SALOME launching. This difference is defined by the environment
+variable<span style="font-weight: bold;"> </span><b>ENV_FOR_LAUNCH</b>
+which is set to 0 in env_products.* files and to 1 in salome.* files.<br>
+<b><br>
+</b>
<hr>
-<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 contains the information relating
-to checking preinstalled products for the Linux.RedHat 8.0 platform
-<br>
-<table BORDER WIDTH="100%" NOSAVE >
-<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.2</td>
-
-<td>ver=`/usr/bin/gcc --version | grep 'gcc (GCC) .*' | cut -b 11-13`</td>
-
-<td>
-<center>-</center>
-</td>
-
-<td>ver should be equal 3.2
-<br>It is recommended to use native gcc on Linux RedHat 8.0</td>
-</tr>
-
-<tr NOSAVE>
-<td>tcl 8.3</td>
-
-<td NOSAVE>existence of TCLHOME
-<br>existence of tclsh8.3
-<br>existence of wish8.3
-<br>existence of libtcl8.3.so
-<br>existence of libtk8.3.so
-<br>existence of libtclx8.3.so
-<br>existence of libtkx8.3.so</td>
-
-<td>set TCLHOME if you have preinstalled version of tcl.
-<br>set LD_LIBRARY_PATH on a directory where libs can be found.</td>
-
-<td>It is recommended to use native tcl on Linux RedHat 8.0</td>
-</tr>
-
-<tr>
-<td>Cascade 4.0</td>
-
-<td>existence of CASROOT environment variable</td>
-
-<td>set CASROOT if you have preinstalled version of CASCADE</td>
-
-<td>Unfortunately we can't say anything exactly about CASCADE 4.0 and we
-only check CASROOT environment variable. If you have problem with preinstalled
-version of CASCADE reinstall it</td>
-</tr>
-
-<tr>
-<td>Python 2.2.1</td>
-
-<td>existence of PYTHONHOME
-<br>isPython=`which python`
-<br>ver=`python -V`</td>
-
-<td>set PYTHONHOME to root Python folder
-<br>set PATH on a directory where python can be found</td>
-
-<td>Python should exist and ver should be equal to 2.2.1
-<br>It is recommended to use native Python on Linux RedHat 8.0</td>
-</tr>
-
-<tr>
-<td>Mesa 3.4.2</td>
-
-<td>existence of libGL.so.1.2.030402</td>
-
-<td>set LD_LIBRARY_PATH on a directory where libGL.so.1.2.030402 can be
-found</td>
-
-<td>You have a possibility to build products (vtk & qt) with Mesa drivers
-from the package supplied with this installation procedure or to use OpenGL
-drivers installed on your computer locally. This check procedure concerns
-only supplied Mesa driver.</td>
-</tr>
-
-<tr>
-<td>Swig 1.3.17</td>
-
-<td>isSwig=`which swig`
-<br>ver=`swig -version`
-<br>ver=`echo $ver | awk '{print $3}'`</td>
-
-<td>set PATH on a directory where swig can be found</td>
-
-<td>Swig should exist and ver should be equal to 1.3.17</td>
-</tr>
-
-<tr>
-<td>Qt 3.0.5</td>
-
-<td>existence of QTDIR
-<br>existence of libqt-mt.so.3.0.5</td>
-
-<td>set QTDIR if you have preinstalled version of qt</td>
-
-<td>We try to find libqt-mt.so.3.0.5 in ${QTDIR}/lib folder.
-<br>You should set MESA_HOME only if you have preinstalled version of Mesa
-3.4.2.
-<br>It is recommended to use native Qt on Linux RedHat 8.0</td>
-</tr>
-
-<tr>
-<td>Qwt 0.4.1</td>
-
-<td>existence of QWTHOME
-<br>existence of libqwt.so.0.4.1</td>
-
-<td>set QWTHOME if you have preinstalled version of qwt</td>
-
-<td>We try to find libqwt.so.0.4.1 in the ${QWTHOME}/lib folder. </td>
-</tr>
-
-<tr>
-<td>Hdf 5-1.4.4</td>
-
-<td>existence of HDF5HOME
-<br>existence of libhdf5.so.0.0.0
-<br>existence of libhdf5.settings</td>
-
-<td>set HDF5HOME if you have preinstalled version of hdf</td>
-
-<td>We try to find libhdf5.so.0.0.0 and libhdf5.settings in ${HDF5HOME}/lib
-folder.
-<br>File libhdf5.settings should contain the following entry:
-<br>HDF5 Version: 1.4.4</td>
-</tr>
-
-<tr>
-<td>Med 2.1.6</td>
-
-<td>existence of MED2HOME
-<br>existence of libmed.so.0.0.0</td>
-
-<td>set MED2HOME if you have preinstalled version of med</td>
-
-<td>Unfortunately we can't check version number.
-<br>We try to find libmed.so.0.0.0 in ${MED2HOME}/lib folder.
-<br>If you have problem with preinstalled version of med reinstall it.</td>
-</tr>
-
-<tr>
-<td>Vtk 4.2</td>
-
-<td>existence of VTKHOME
-<br>existence of libvtkCommon.so</td>
-
-<td>set VTKHOME if you have preinstalled version of vtk</td>
-
-<td>Unfortunately we can't check the version number.
-<br>We try to find libvtkCommon.so in ${VTKHOME}/lib/vtk folder.
-<br>If you have problem with preinstalled version of vtk reinstall it.</td>
-</tr>
-
-<tr>
-<td>OmniORB 3.0.5,
-<br>OmniORBpy 1.5,
-<br>OmniNotify 1.2</td>
-
-<td>existence of OMNIORBDIR
-<br>existence of libomniORB3.so.0.5
-<br>existence of _omnipymodule.so.0.5
-<br>existence of libCOSNotify3.so.0.5
-<br>existence of notifd
-<br>existence of THIS_IS_omniORB_3_0_5
-<br>existence of THIS_IS_omniNotify_1_2
-<br>existence of THIS_IS_OMNIORBPY_1_5</td>
-
-<td>set OMNIORBDIR if you have preinstalled version of omni</td>
-
-<td>We try to find libomniORB3.so.0.5, _omnipymodule.so.0.5 and libCOSNotify3.so.0.5
-in ${OMNIORBDIR}/lib/i586_linux_2.0_glibc2.1 folder.
-<br>We try to find notifd in ${OMNIORBDIR}/bin/i586_linux_2.0_glibc2.1
-folder.
-<br>Additional checking - omni add special files THIS_IS_...
-<br>We try to find THIS_IS_omniORB_3_0_5 in ${OMNIORBDIR} folder.
-<br>We try to find THIS_IS_omniNotify_1_2 in ${OMNIORBDIR}/src/services/omniNotify.
-<br>We try to find THIS_IS_OMNIORBPY_1_5 in ${OMNIORBDIR}/src/lib/omniORBpy
-folder.</td>
-</tr>
-
-<tr>
-<td>Numeric 22.0</td>
-
-<td>existence of Numeric folder
-<br>existence of _numpy.so</td>
-
-<td>set PYTHONHOME if you have preinstalled version of python</td>
-
-<td>Unfortunately we can't check the version number.
-<br>We try to find Numeric folder in ${PYTHONHOME}/lib/python2.2/site-packages/Numeric
-folder.
-<br>If you have problem with preinstalled version of numeric 22.0 reinstall
-it.</td>
-</tr>
-
-<tr>
-<td>Sip 3.3.2</td>
-
-<td>existence of SIPDIR
-<br>existence of sip
-<br>existence of libsip.so.9.1.0</td>
-
-<td>set SIPDIR to directory where you have sip preinstalled</td>
-
-<td>We try to find sip and libsip.so.9.1.0 in $SIPDIR folder if you set
-SIPDIR , otherwise searching is done using $PATH and $LD_LIBRARY_PATH accordingly.
-<br>It is recommended to use native Sip on Linux RedHat 8.0</td>
-</tr>
-
-<tr>
-<td>PyQt 3.3.2</td>
-
-<td>existence of PYQTDIR
-<br>existence of libqtxmlcmodule.so.1.0.0</td>
-
-<td>set PYQTDIR to directory where you have sip preinstalled</td>
-
-<td>Unfortunately we can't check the version number.
-<br>We try to find libqtxmlcmodule.so.1.0.0 in $PYQTDIR folder if you set
-PYQTDIR, otherwise searching is done using $LD_LIBRARY_PATH .
-<br>If you have problem with preinstalled version of PyQt 3.3.2 reinstall
-it.
-<br>It is recommended to use native PyQt on Linux RedHat 8.0</td>
-</tr>
-
-<tr>
-<td>HappyDoc 2.1</td>
-
-<td>existence of happydoc
-<br>ver=`happydoc | grep "HappyDoc version 2.1"`</td>
-
-<td>set PYTHONHOME if you have preinstalled version of python</td>
-
-<td>We try to find happydoc in $PYTHONHOME/bin folder.
-<br>ver should not be empty.
-<br>This product is not obligatory. It was added only for your comfort.</td>
-</tr>
-
-<tr>
-<td>Doxygen 1.3-rc2</td>
-
-<td>existence of doxygen
-<br>existence of doxysearch
-<br>existence of doxytag
-<br>existence of doxywizard</td>
-
-<td>set QTDIR if you have preinstalled version of qt
-<br>set PATH on a directory where doxygen, doxysearch, doxytag and doxywizard
-can be found</td>
-
-<td>Unfortunately we can't check the version number.
-<br>It's necessary to have compiled Qt in order to build doxywizard.
-<br>If you have problem with preinstalled version of doxygen 1.3-rc2 reinstall
-it.
-<br>This product is not obligatory. It was added only for your comfort.</td>
-</tr>
-
-<tr>
-<td>Graphviz 1.9</td>
-
-<td>existence of dot</td>
-
-<td>add GraphViz's bin directory to the PATH environment variable</td>
-
-<td>Unfortunately we can't check the version number.
-<br>We try to find dot program in the $PATH</td>
-</tr>
-
-<tr>
-<td>SALOME PRO binaries</td>
-
-<td>existence of SALOME_ROOT_DIR
-<br>existence of VERSION file
-<br>ver=`cat $SALOME_ROOT_DIR/bin/VERSION | awk -F: '{print $2}' | tr -d
-'[:space:]'`</td>
-
-<td>set SALOME_ROOT_DIR if you have preinstalled binaries of SALOME PRO
-version 1.2d</td>
-
-<td>SALOME PRO binaries should exist and ver should be equal to 1.2d</td>
-</tr>
-
-<tr>
-<td>SALOME PRO sources</td>
-
-<td>existence of SALOMEPRO_SRC
-<br>existence of VERSION file
-<br>ver=`cat $SALOMEPRO_SRC/bin/VERSION | awk -F: '{print $2}' | tr -d
+<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 SALOMEPRO_SRC if you have preinstalled sources of SALOME PRO version
-1.2d</td>
-
-<td>SALOME PRO sources should exist and ver should be equal to 1.2d</td>
-</tr>
+ <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>Note: 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 $PATH and $LD_LIBRARY_PATH
-variables <b><font color="#FF0000">before</font></b> starting Installation
-Wizard. Otherwise installation script will fail to find preinstalled products.
+<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>
-
-<h3>
-<a NAME="pick_up_env"></a>Pick up the <font color="#FF0000">environment</font></h3>
-Please, read carefully the following information. This section describes
-how the installation procedure collects environment.
-<p>After installing each product shell script creates in the product root
-folder special environment file. The name of the file is generated from
-the name of product by the following scheme: <b>env_<product_name>.sh.</b>
+<h3> <a name="pick_up_env"></a>Pick up the <font color="#ff0000">environment</font></h3>
+Please, read carefully the following information. This section
+describes how the installation procedure collects the environment.
+<p>After installing each product shell script creates special
+environment file for each product in its target folder . The name of
+the file is generated
+from
+the name of product by the following scheme: <b>env_<product_name>.sh.</b>
This file includes all necessary product settings. For example for Vtk
the file is <b>env_Vtk.sh</b>. Environment files allows to pick up all
-environment settings which are necessary to build and launch SALOME. When
-installing SALOME sources and/or binaries, installation procedure picks
-up all the settings files and generate two scripts: <b>salome.sh</b> and
-<b>salome.csh
-</b>for
-sh and csh correspondingly. Such approach helps to save time when reinstalling
-products and you may not to care about setting all environment variables
-manually to build/launch SALOME. What you need is just to use one of these
-scripts.
+environment settings which are necessary to build and launch SALOME.
+When installing SALOME
+sources and/or binaries, installation procedure picks up all the
+settings files and generate two scripts: <b>salome.sh</b> and <b>salome.csh
+</b>for sh and csh correspondingly. Such approach helps to save time
+when reinstalling products and you may not to care about setting all
+environment variables
+manually to build/launch SALOME. What you need is just to use one of
+these
+scripts. </p>
<p>This concerns also those products which are not currently installed.
-For example, you install some SALOME binaries to the directory where you
-have previously installed other products. Installation procedure
-still tries to collect environment files from the target directory if it
-find necessary products there. If some product is not found in the target
-directory the corresponding section of <b>salome.sh/salome.csh</b> files
-will be skipped.
-<br>For native products (<i><b>gcc, tcl, python, qt, sip, pyqt </b>for
-RedHat-8.0<b>)</b></i> instal script tries to find them using <b>$PATH</b>
-/ <b>$LD_LIBRARY_PATH</b> variables and then in the system default directories
-(<b>/usr/bin, /usr/lib</b> etc., depending on the product).
-<p>In any case you may edit <b>salome.*</b> files after installation procedure
-finishes, as you want.
-<p>
+For example, you install some SALOME binaries to the directory where
+you have previously installed other products. Installation
+procedure still tries to collect environment files from the target
+directory if it finds necessary products there. If some product is not
+found in the target directory the corresponding
+section of <b>salome.sh/salome.csh</b> files will be skipped. <br>
+For native products (like <i><b>gcc, tcl, etc...</b><b>)</b></i>
+installation procedure tries to find them first using <b>PATH</b>
+/ <b>LD_LIBRARY_PATH</b> variables and then in the system default
+directories (<b>/usr/bin, /usr/lib</b> etc., depending on the product).
+</p>
+<p>In any case you may edit <b>salome.*</b> files after installation
+procedure finishes, as you want.<br>
+<span style="font-weight: bold;">Note:</span> as it was mentioned <a
+ href="#env_files">above</a> there are two more environment files which
+are generated by the installation procedure: <span
+ style="font-weight: bold;">env_products.csh</span> and <span
+ style="font-weight: bold;">env_products.sh</span>. These files can be
+found in the target installation root directory.<br>
+</p>
<hr>
-<h3>
-<a NAME="xml_files"></a>Modifying <font color="#FF0000">XML</font> configuration
-<font color="#FF0000">file</font></h3>
-<font color="#000000">You can create your own configuration. Installation
-Wizard then can take it as command line argument to provide list of products
-you want to install with it. The list of products and some another settings
-for the Installation Wizard are provided in xml file. The default file
-which Installation Wizard looks for if no command line arguments ar given,
-is
-<b>config.xml</b>. This section describes the format of configuration
-file.</font>
-<br><font color="#000000">Xml tags are in bold blue, optional sections/tags
+<h3><a name="xml_files"></a>Modifying <font color="#ff0000">XML</font>
+configuration <font color="#ff0000">file</font></h3>
+<font color="#000000">You can create your own configuration file.
+Installation Wizard then can take it as command line argument to
+provide list of products you want to install with it. The list of
+products and some another settings for the Installation Wizard are
+provided in XML file. The default file which Installation Wizard looks
+for if no command line arguments are given, is <b>config.xml</b>. This
+section describes the structure of the configuration file.</font> <br>
+<font color="#000000">XNL tags are in bold blue, optional sections/tags
are in brackets.</font>
-<p><b><font color="#000099"><document></font></b>
-<br><font color="#000000"><b> </b>[</font><b><font color="#000099"><config</font></b><font color="#000000">
-[version=<install_wizard_version>]</font>
-<br><font color="#000000">
-[caption=<install_wizard_caption>]</font>
-<br><font color="#000000">
-[copyright=<install_wizard_copyright>]</font>
-<br><font color="#000000">
-[license=<install_wizard_license_info>]</font>
-<br><font color="#000000">
-[os=<target_paltform>]</font><b><font color="#000099">/></font></b><font color="#000000">]</font>
-<br><font color="#000000"><b> </b>[</font><b><font color="#000099"><path</font></b><font color="#000000">
-[targetdir=<target_directory>]</font>
-<br><font color="#000000">
-[tempdir=<temp_directory>]</font><b><font color="#000099">/></font></b><font color="#000000">]</font>
-<br><font color="#000000"> [</font><b><font color="#000099"><product</font></b><font color="#000000">
-name=<product_name></font>
-<br><font color="#000000">
-version=<product_version></font>
-<br><font color="#000000">
-install=<installation_mode></font>
-<br><font color="#000000">
-supported=<supported_installation_modes></font>
-<br><font color="#000000">
-disable=<disable_flag></font>
-<br><font color="#000000">
-dependancies=<list_of_prerequisites></font>
-<br><font color="#000000">
-installdiskspace=<install_disk_space></font>
-<br><font color="#000000">
-temporarydiskspace=<tmp_disk_space></font>
-<br><font color="#000000">
-script=<installation_script_name></font><font color="#000099">/<b>></b></font><font color="#000000">]</font>
-<br><font color="#000000"> [</font><b><font color="#000099"><product</font></b><font color="#000000">
-... </font><font color="#000099">/<b>></b></font><font color="#000000">]</font>
-<br><font color="#000000"> <b> .</b></font><b><font color="#000099">..</font></b>
-<br><b><font color="#000099"></document></font></b>
-<h4>
-<font color="#000000"><config> section</font></h4>
-<font color="#000000">This is optional section - contains general information
-Installation Wizard itself.</font>
+<font face="Courier"><p><b><font color="#000099"><document></font></b>
+<br>
+<font color="#000000"><b> </b>[</font><b><font
+ color="#000099"> <config</font></b><font color="#000000">
+[ version=<install_wizard_version> ]</font> <br>
+<font color="#000000">
+ [
+caption=<install_wizard_caption> ]</font> <br>
+<font color="#000000">
+ [
+copyright=<install_wizard_copyright> ]</font> <br>
+<font color="#000000">
+ [
+license=<install_wizard_license_info> ]</font> <br>
+<font color="#000000">
+ [ os=<target_platform>
+]</font><b><font color="#000099"><br>
+ /></font></b><font color="#000000"> <br>
+ ]</font> <br>
+<font color="#000000"><b> </b>[ </font><b><font
+ color="#000099"><path</font></b><font color="#000000">
+[ targetdir=<target_directory> ]</font> <br>
+<font color="#000000">
+
+[ tempdir=<temp_directory> ]</font><b><font
+ color="#000099"><br>
+ /> </font></b><font color="#000000"><br>
+ ]</font> <br>
+<font color="#000000"> [</font><b><font
+ color="#000099"> <product</font></b><font color="#000000">
+name=<product_name></font> <br>
+<font color="#000000">
+
+version=<product_version></font> <br>
+ [
+context=<product_context>
+]<br>
+ [
+description=<product_description> ]<br>
+<font color="#000000">
+
+install=<installation_mode></font> <br>
+<font color="#000000">
+
+supported=<supported_installation_modes></font> <br>
+<font color="#000000">
+ disable=<disable_flag><br>
+ [
+pickupenv=<pickup_env_flag> ]</font><font
+ color="#000000"><br>
+
+
+dependancies=<list_of_prerequisites></font> <font
+ color="#000000"><br>
+
+ installdiskspace=<install_disk_space></font>
+<font color="#000000"><br>
+
+ temporarydiskspace=<tmp_disk_space></font> <font
+ color="#000000"><br>
+
+ script=<installation_script_name></font><font
+ color="#000099"><br>
+ /<b>></b></font><font color="#000000">
+<br>
+ ]</font> <font color="#000000"><br>
+ [</font><b><font color="#000099"> <product</font></b><font
+ color="#000000"> ... </font><font color="#000099"><br>
+ /<b>></b></font><font color="#000000">
+<br>
+ ]</font> <font color="#000000"><br>
+ <b> .</b></font><b><font color="#000099">..</font></b>
+<b><font color="#000099"><br>
+</document></font></b> </p></font>
+<h4><font color="#000000"><config> section</font></h4>
+<font color="#000000">This is optional section - contains general
+information Installation Wizard itself.</font>
<ul>
-<li>
-<font color="#000000"><b>version</b>: Installation Wizard's version number;</font></li>
-
-<li>
-<font color="#000000"><b>caption</b>: Installation Wizard's main window
-title - if this string contains '%1' text - the title will contain in this
-place version number (see above);</font></li>
-
-<li>
-<font color="#000000"><b>copyright</b>: Installation Wizard's copyright
-information (appears on the first page of program);</font></li>
-
-<li>
-<font color="#000000"><b>license</b>: Installation Wizard's license information
-(appears on the first page of program);</font></li>
-
-<li>
-<font color="#000000"><b>os</b>: Contains directory name (relative from
-./Products/BINARIES) where Installation Wizard should search precompiled
-binaries packages. If this tag is skipped, binaries are implied to be in
+ <li> <font color="#000000"><b>version</b>: Installation Wizard's
+version number;</font></li>
+ <li> <font color="#000000"><b>caption</b>: Installation Wizard's
+main
+window title - if this string contains '%1' text - the title will
+contain
+in this place version number (see above);</font></li>
+ <li> <font color="#000000"><b>copyright</b>: Installation Wizard's
+copyright information (appears on the first page of program);</font></li>
+ <li> <font color="#000000"><b>license</b>: Installation Wizard's
+license information (appears on the first page of program);</font></li>
+ <li> <font color="#000000"><b>os</b>: Contains directory name
+(relative from ./Products/BINARIES) where Installation Wizard should
+search precompiled binaries packages. If this tag is skipped, binaries
+are implied to be in
the ./Products/BINARIES directory.</font></li>
</ul>
-
-<h4>
-<b><font color="#000000"><path> section</font></b></h4>
+<h4> <b><font color="#000000"><path> section</font></b></h4>
This is optional section - contains default directories.
<ul>
-<li>
-<font color="#000000"><b>targetdir</b>: Starting target directory - path
-to the directory where products should be installed;</font></li>
-
-<li>
-<font color="#000000"><b>tempdir</b>: Starting temp directory - path to
-the directory for the temporary files.</font></li>
+ <li> <font color="#000000"><b>targetdir</b>: Starting target
+directory - path to the directory where products should be installed;</font></li>
+ <li> <font color="#000000"><b>tempdir</b>: Starting temp directory -
+path to the directory for the temporary files.</font></li>
</ul>
-
-<h4>
-<b><product> section</b></h4>
-This section describes product to be installed with the Installation Wizard.
-All tags are obligatory. Products appears in the products tree and are
-installed in the order they are described in the configuration file. It
-is recommended to insert native products at the top of the list before
-all other products.
+<h4> <b><product> section</b></h4>
+This section describes product to be installed with the Installation
+Wizard. Products appear in the products tree
+and are installed in the order they are described in the configuration
+file. It is recommended to insert native products at the top of the
+list before all other products.
<ul>
-<li>
-<font color="#000000"><b>name</b>: Name of the product;</font></li>
-
-<li>
-<font color="#000000"><b>version</b>: Version of the product;</font></li>
-
-<li>
-<font color="#000000"><b>supported</b>: Supported modes of installation,
-should contain one or more of the following options, separated by comma:
-<i>install
-sources</i>, <i>install binaries</i>, <i>use native</i>. Installation script
-should contain corresponding functions for each of supported installation
-modes;</font></li>
-
-<li>
-<font color="#000000"><b>install</b>: Default (starting) installation mode;</font></li>
-
-<li>
-<font color="#000000"><b>disable</b>: If this flag has 'true' value, corresponding
-product will not appear in the list of products tree and will not be installed;</font></li>
-
-<li>
-<font color="#000000"><b>dependancies</b>: list of prerequisite products,
-which are necessary to build this product, separated by comma;</font></li>
-
-<li>
-<font color="#000000"><b>installdiskspace</b>: Total amount space (integer,
-in Kbytes), which product occupies on the hard drive after the installation;</font></li>
-
-<li>
-<font color="#000000"><b>temporarydiskspace</b>: Disk space (integer, in
-Kbytes) for the temporary files, which is necessary to build the product
-from the sources;</font></li>
-
-<li>
-<font color="#000000"><b>script</b>: Installation script name. This script
-is in charge of installation of the product. It is called when necessary
-from the main program. See <a href="#new_products">next section</a> for
+ <li> <font color="#000000"><b>name</b>: Name of the product;</font></li>
+ <li> <font color="#000000"><b>version</b>: Version of the product;</font></li>
+ <li> <font color="#000000"><b>description</b>: Description of the
+product (optional);</font></li>
+ <li> <font color="#000000"><b>context</b>: Context of the product
+(optional); the possible values are <b>'salome sources'</b>, <b>'salome
+binaries'</b> and <b>'prerequisite'</b>;</font></li>
+ <li> <font color="#000000"><b>supported</b>: Supported modes of
+installation, should contain one or more of the following options,
+separated by comma: <i>install sources</i>, <i>install binaries</i>, <i>use
+native</i>. Installation script should contain corresponding functions
+for each of supported installation modes;</font></li>
+ <li> <font color="#000000"><b>install</b>: Default (starting)
+installation mode;</font></li>
+ <li> <font color="#000000"><b>disable</b>: If this flag has 'true'
+value, corresponding product will not appear in the list of products
+tree and will not be installed;</font></li>
+ <li><b>pickupenv</b>: This flag points that pickup environment
+procedure
+should be performed for this module. If this flag equal to <b>true</b>,
+ salome.sh
+and salome.csh files will be created in the product's
+installation
+directory. Usually this option is set to true for SALOME KERNEL module
+sources and binaries pakcge. This is optional key, default value is <b>false.</b><br>
+ </li>
+ <li> <font color="#000000"><b>dependancies</b>: list of prerequisite
+products, which are necessary to build this product, separated by comma;</font></li>
+ <li> <font color="#000000"><b>installdiskspace</b>: Total amount
+space (integer, in Kbytes), which product occupies on the hard drive
+after the
+installation;</font></li>
+ <li> <font color="#000000"><b>temporarydiskspace</b>: Disk space
+(integer, in Kbytes) for the temporary files, which is necessary to
+build the product from the sources;</font></li>
+ <li> <font color="#000000"><b>script</b>: Installation script name.
+This script is in charge of installation of the product. It is called
+when necessary from the main program. See <a href="#new_products">next
+section</a> for
more information.</font></li>
</ul>
<b>Note:</b> If you add new products to be installed with Installation
-Wizard, you should also provide installation script for this product. See
+Wizard, you should also provide installation script for this product.
+See
next section for more details.
-<p>
<hr>
-<h3>
-<a NAME="new_products"></a>Implementing <font color="#FF0000">installation
+<h3><a name="new_products"></a>Implementing <font color="#ff0000">installation
scripts</font> for the new products</h3>
-When you want some product to be installed with the Installation Wizard,
-you should add it's description it <a href="#xml_files">in the configuration
-file</a> and create bash installation script, following described in this
-section rules.
-<br>There are some obligatory functions to be provided in this installation
+When you want some product to be installed with the Installation
+Wizard, you should add it's description it <a href="#xml_files">in the
+configuration file</a> and create bash installation script, following
+described in this section rules. <br>
+There are some obligatory functions to be provided in this installation
script. These functions are automatically called by master installation
-script or/and GUI shell when it is necessary.
+script
+or/and its GUI shell when it is necessary.<br>
+<font color="#000000">File <b>common.sh</b> contains some service
+functions
+which can be used in your installation script, like <b>make_env()</b>,<b>
+make_dir()</b>, <b>try_existing()</b>, <b>sort_path()</b>,<b>
+find_in_path()</b>,
+etc.</font>
<ul>
-<li>
-<b>check_version()</b>: This function allows to check the version
-of the product already installed on the computer. It should try to find
-product (native or preinstalled in the target directory) and check it version.
-This helps to avoid unnecessary reinstallation. This is internal function
-and is not called</li>
-
-<li>
-<b><font color="#000000">try_native()</font></b><font color="#000099">:
-</font><font color="#000000">This
-function is called when <i>'use native' </i>installation mode is selected
-by the user. The function should try to find native version of the product
-and define possibility of it usage. Should create environment for the product
-in the temporary directory (see also description of <b>print_env(</b>)
+ <li> <b>check_version()</b>: This function allows to check the
+version of the product already installed on the computer. It should try
+to find product (native or preinstalled in the target directory) and
+check
+it version. This helps to avoid unnecessary reinstallation. This is
+internal
+function and is not called</li>
+ <li> <b><font color="#000000">try_native()</font></b><font
+ color="#000099">: </font><font color="#000000">This function is
+called when <i>'use native' </i>installation mode is selected by the
+user. The function should try to find native version of the product and
+define possibility of it usage. Should create environment for the
+product in the temporary directory (see also description of <b>print_env(</b>)
function). If you do not provide native mode installation, you can omit
this function.</font></li>
-
-<li>
-<font color="#000000"><b>install_source()</b>: This function is called
-when <i>'install sources</i>' installation mode is selected by the user.
-The function is responsible for the building of the product from the sources
-package. Should create environment for the product in the temporary directory
-(see also description of <b>print_env(</b>) function). If you do not provide
-sources mode installation, you can omit this function</font></li>
-
-<li>
-<font color="#000000"><b>install_binary()</b>: This function is called
-when <i>'install binaries'</i> installation mode is selected by the user.
-The function is responsible for the extracting of the product from the
-binaries package. Should create environment for the product in the temporary
-directory (see also description of <b>print_env(</b>) function). If you
-do not provide binaries mode installation, you can omit this function.</font></li>
-
-<li>
-<b>try_preinstalled()</b>: <font color="#000000">This function is called
-when<i> 'not install'</i> installation mode is selected by the user. In
-this case script should inspect target directory to try to find already
-preinstalled product, pick up and check environment from there. See <a href="#pick_up_env">here</a>
-for more details.</font></li>
-
-<li>
-<font color="#000000"><b>print_env()</b>: This function is in charge of
-creation environment script. It should create file with name </font><b>env_<product_name>.sh</b>
-in the temporary directory and then copy it into the product installation
-directory. The file should contain all necessary environment variables
-settings for the product. It will be collected during the 'pick-up-environment'
-procedure.</li>
+ <li> <font color="#000000"><b>install_source()</b>: This function is
+called when <i>'install sources</i>' installation mode is selected by
+the
+user. The function is responsible for the building of the product from
+the
+sources package. Should create environment for the product in the
+temporary
+directory (see also description of <b>print_env(</b>) function). If
+you do
+not provide sources mode installation, you can omit this function</font></li>
+ <li> <font color="#000000"><b>install_binary()</b>: This function is
+called when <i>'install binaries'</i> installation mode is selected by
+the
+user. The function is responsible for the extracting of the product
+from
+the binaries package. Should create environment for the product in the
+temporary
+directory (see also description of <b>print_env(</b>) function). If
+you do
+not provide binaries mode installation, you can omit this function.</font></li>
+ <li> <b>try_preinstalled()</b>: <font color="#000000">This function
+is called when<i> 'not install'</i> installation mode is selected by
+the user. In this case script should inspect target directory to try to
+find already preinstalled product, pick up and check environment from
+there. See <a href="#pick_up_env">here</a> for more details.</font></li>
+ <li> <font color="#000000"><b>print_env()</b>: This function is in
+charge of creation environment script. It should create file with name </font><b>env_<product_name>.sh</b>
+in the temporary directory and then copy it into the product
+installation directory. The file should contain all necessary
+environment variables settings for the product. It will be collected
+during the 'pick-up-environment' procedure.</li>
+ <li><b>pickup_env()</b>: This procedure corresponds <b>pickupenv</b>
+tag
+of the configuration xml file (see previous section). Should call <b>make_env</b>
+procedure to perform pick-up environment procedure for the product.<br>
+ </li>
</ul>
<font color="#000000">The calling signature of the product installation
-script is following:</font>
-<br><b><font color="#000000"><product_script_name> <function_name>
-<temp_folder> <products_directory> <target_directory> <dependancies>
-<product_name></font></b>
-<p><font color="#000000">where</font>
-<br><font color="#000000"><b><product_script_name></b> - installation
-script name (described in configuration xml file);</font>
-<br><font color="#000000"><b><function_name></b> - the name of function,
-corresponding to the selected installation mode: <i>try_native, install_source,
-install_binary</i> or <i>try_preinstalled</i>;</font>
-<br><font color="#000000"><b><temp_folder></b> - temporary files directory;</font>
-<br><font color="#000000"><b><products_directory></b> - directory where
-the sources/binaries package can be found. You should provide sources package
-in the <i><Install_Wizard_root_directory>/Products/SOURCES</i> directory
-and binaries package in the <i><InstallWizard_root_directory>/Products/BINARIES/<os_version></i>,
-where <os_version> is target platform description, which appears in
-the corresponding section of the <a href="#xml_files">configuration xml
-file</a>.</font>
-<br><font color="#000000"><b><target_directory></b> - root target directory
-where product should be installed to;</font>
-<br><font color="#000000"><b><dependancies></b> - single-quoted list
-of prerequisite products, separated by space;</font>
-<br><font color="#000000"><b><product_name> </b>- product name itself.</font>
-<p><font color="#000000">Example:</font>
-<br><i><font color="#000000">med-2.1.6.sh install_binary /tmp/work ./Products/BINARIES/RedHat8.0
-/usr/salome 'gcc Hdf' med</font></i>
-<p><font color="#000000">Copy created script into the <i><Install_Wizard_root_directory>/config_files</i>
-sub-directory. File <b>common.sh</b> contains some service functions which
-can be used in your installation script.</font>
-<p>
-<hr>
+script is following:</font> <br>
+<b><font color="#000000"><product_script_name>
+<function_name> <temp_folder> <products_directory>
+<target_directory>
+<dependancies> <product_name></font></b>
+<p><font color="#000000">where</font> <br>
+<font color="#000000"><b><product_script_name></b> - installation
+script name (described in configuration xml file);</font> <br>
+<font color="#000000"><b><function_name></b> - the name of
+function, corresponding to the selected installation mode: <i>try_native,
+install_source, install_binary</i> or <i>try_preinstalled</i>;</font> <br>
+<font color="#000000"><b><temp_folder></b> - temporary files
+directory;</font> <br>
+<font color="#000000"><b><products_directory></b> - directory
+where the sources/binaries package can be found. You should provide
+sources package in the <i><Install_Wizard_root_directory>/Products/SOURCES</i>
+directory and binaries package in the <i><InstallWizard_root_directory>/Products/BINARIES/<os_version></i>,
+where <os_version> is target platform description, which appears
+in the corresponding section of the <a href="#xml_files">configuration
+xml
+file</a>.</font> <br>
+<font color="#000000"><b><target_directory></b> - root target
+directory where product should be installed to;</font> <br>
+<font color="#000000"><b><dependancies></b> - single-quoted list
+of prerequisite products, separated by space;</font> <br>
+<font color="#000000"><b><product_name> </b>- product name
+itself.</font> </p>
+<p><font color="#000000">Example:</font> <br>
+<i><font color="#000000">med-2.2.2.sh install_binary /tmp/work
+./Products/BINARIES/Mandrake10.1 /usr/salome 'gcc Hdf' med</font></i> </p>
+<p><font color="#000000">Copy created script into the <i><Install_Wizard_root_directory>/config_files</i>
+sub-directory where all installation scripts are stored. Installation
+Wizard
+will automatically search and call your script during the installation
+procedure.</font>
+</p>
+<hr> <br>
+<br>
</body>
</html>
