- 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>
-
-<p><b>-g</b><br>
- 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><br>
- Runs the Installation Wizard in the batch
-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>Red Hat </i>version and uses 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><br>
- The target directory, SALOME products to
-be installed to. If used, overloads target directory, given in the configuration
-xml file. <br>
- <b>-tmp <tmp-dir></b><br>
- The directory, which is used to contain
- temporary files. If used, overloads temporary directory, given in the
-configuration xml file.<br>
-<b>-h</b><br>
- Prints help information. <br>
- </p>
-
-<p>So, to run the Installation Wizard in the GUI mode, just type <b>runInstall</b>.
- </p>
-
-<p>The installation procedure can support some different Linux platforms
-(currently it provides only configuration scripts for <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>
-
-<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 click
-<i>"Help"</i> button. </p>
-
-<p>Skip the first <i>"Introduction"</i> page by pressing <i>"Next"</i> button.
- </p>
-
-<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 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>
-
-<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. </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 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 Linux Red Hat 8.0 products (these are gcc, tcl,
-Python, Qt, Sip and PyQt), select <i>"use native" </i>option. </p>
-
-<p>The box at the right side of the page displays the information about currently
-highlighted product: name, version, short description (if provided), required
-disk space, temporary files disk space, list of prerequisites and user choice.
-</p>
-
-<center><a name="ProductPage"></a><br>
- <img src="productpage.png" height="525" width="565" alt="">
-
-<p><b>Figure 1:</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>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>
-
-<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>
-
-<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: </p>
-
-<center>
-<p><a name="ChoicePage"></a><br>
- <img src="choicepage.png" height="525" width="565" alt="">
- </p>
-
-<p><b>Figure 2:</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" height="525" width="565" alt="">
-
-<p><b>Figure 3:</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>
-
-<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="525" width="565" alt="">
- </p>
-
-<p><b>Figure 4:</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>
-
-<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 <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. </p>
-
-<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="1" width="100%" nosave="">
- <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.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 valign="top">boost 1.30.2<br>
- </td>
- <td valign="top">ver=`egrep 'BOOST_VERSION [0-9]+' ${BOOSTDIR}/boost/version.hpp
-| sed 's/.*BOOST_VERSION \([0-9]\+\)/\1/g'`<br>
- </td>
- <td valign="top">set BOOSTDIR if you have preinstalled version of
-boost<br>
- </td>
- <td valign="top">It is impossible to use native BOOST and to install
-BOOST from binaries.<br>
- </td>
- </tr>
- <tr>
- <td>Open CASCADE 5.2<br>
- </td>
- <td>existence of CASROOT environment variable</td>
- <td>set CASROOT if you have preinstalled version of Open CASCADE</td>
- <td>Unfortunately we can't say anything exactly about CASCADE 5.2
-and we only check CASROOT environment variable. If you have problem with
-preinstalled version of Open CASCADE, reinstall it</td>
- </tr>
- <tr>
- <td>Patch for Open CASCADE 5.2<br>
- </td>
- <td></td>
- <td></td>
- <td>Open CASCADE 5.2 provided with the Installation Wizard already includes the patch,
-necessary for PAL/SALOME 2.1.0. In addition the Installation Wizard provides the sources of a Open CASCADE patch
-which can be applied to original Open CASCADE 5.2. sources before compilation.</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 valign="top">Netgen 4.3<br>
- </td>
- <td valign="top">existence of NETGENROOT<br>
- </td>
- <td valign="top">set NETGENROOT 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 NETGENROOT environment varible is set.<br>
- </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.
+The Installation Wizard can be launched in two modes: <span
+ style="font-weight: bold;">GUI </span>and <span
+ style="font-weight: bold;">batch</span>. <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 the
+terminal
+window:<span style="font-weight: bold;"></span><span
+ style="font-weight: bold;"></span>
+<p>[ python ] <b>./runInstall </b>[options]<b><br>
+</b></p>
+<p>Without options this script will launch the SALOME Installation
+Wizard in the GUI mode.<br>
+The default installation settings can be overridden by using of command
+line options. Each option has short and long notations:<br>
+</p>
+<p><b>-g / --gui</b><br>
+</p>
+<div style="margin-left: 40px;">Runs the Installation Wizard in the
+GUI
+mode (this is the default mode).<br>
+</div>
+<p><b>-b / --batch</b><br>
+</p>
+<div style="margin-left: 40px;">Runs the Installation Wizard in
+the terminal mode. <br>
+</div>
+<p><b>-f FILE / --file=</b><span style="font-weight: bold;">FILE<br>
+</span></p>
+<div style="margin-left: 40px;">
+This is the XML configuration file used by the Installation Wizard.
+If this option is not used, the installation script tries to define
+the<i>Linux </i>version and to use the corresponding XML file
+if it is present.
+For example, for <span style="color: rgb(0, 0, 153);">Linux Mandriva
+2010</span> the <b>config_Mandriva_2010.0.xml</b>
+file
+will be used by default.
+</div>
+<p> <b>-d DIR / --target=DIR</b><br>
+</p>
+<div style="margin-left: 40px;">This is the target installation
+directory for SALOME platform. If used, this option overrides
+the default target directory, given in the
+configuration XML file (usually<span style="font-weight: bold;">
+${HOME}/salome_<version></span><!--,
+see
+<a href="#xml_files">here</a> for more details-->).<br>
+</div>
+<p><b>-t DIR / --tmp=DIR </b></p>
+<div style="margin-left: 40px;">This is the directory, for
+temporary files. If given, this option overrides the 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="#xml_files">here</a> for more information-->).<br>
+</div>
+<p><b>-a / --all-from-sources</b></p>
+<div style="margin-left: 40px;">
+Force all the products to be installed from sources (including all
+SALOME modules). If this option is used, all the default installation
+modes for all the products are ignored.<br>
+This option is helpful when the user wants to install SALOME on the
+platform which is not officially supported. In this case, the user can
+try to run the SALOME Installation Wizard with the <span
+ style="font-weight: bold;">-a</span> option in order to build all the
+products from sources.<br>
+<b>Note, that this is long-time operation which can take more than
+24 hours depending on the computer.</b><br>
+</div>
+<p><b>-s / --single-directory </b></p>
+<div style="margin-left: 40px;">Install all SALOME binaries packages
+to one directory.<br>
+<b>This option is ignored when --all-from-sources (-a) option is used.
+</b></div>
+<p><b>-h / --help</b><br>
+</p>
+<div style="margin-left: 40px;">Prints help information on
+the usage of the Installation Wizard. <br>
+</div>
+<p></p>
+<p>
+<b>-v / --version</b><br>
+</p>
+<div style="margin-left: 40px;">Prints version information
+(<span style="font-weight: bold;">Note: </span>this
+is the version number of the Installation Wizard, not of SALOME platform). <br>
+</div>
+<p>
+</p>
+<p>The installation procedure supports different <span style="color: rgb(0, 0, 153);">Linux
+</span>platforms and installs various 3d-party installation prerequisite products, which
+are required by SALOME platform. Among supported Linux platforms there are Mandriva 2008
+(32bit and 64bit), Mandriva 2010 (32bit and 64bit), Debian 4.0 Etch (32bit and 64bit),
+Debian 5.0 Lenny 64bit, Debian 6.0 Squeeze 64bit and other ones.<br>
+The usage of configuration XML files provides a flexible way to modify
+the list of products to be installed by the Installation Wizard without
+changing the source code of the application. Just create your own XML
+configuration file and implement installation scripts for the prerequisite products you
+need and then use this XML file with the Installation Wizard. This can
+be done, for example, for some <span style="color: rgb(0, 0, 153);">Linux
+</span>platform which is not supported directly by the
+Installation Wizard. See <a href="#xml_files">Modifying XML
+configuration file</a> and <a href="#new_products">Implementing installation
+scripts for the new products</a> sections for more information. </p>
+<h3 style="margin-left: 40px;"> <a name="gui_mode"></a>GUI
+mode<br>
+</h3>
+<p>The GUI of the <font color="#ff0000">Installation Wizard</font> has been
+developed with <span style="font-weight: bold;"><span style="color: rgb(0, 0, 153);">Qt
+3.3.8 </span> </span>toolkit by <span style="color: rgb(0, 0, 153);">
+Trolltech </span>. After launching the Installation Wizard
+in the GUI mode the wizard window is shown to the user. This wizard
+guides the user through several subsequent pages. To navigate between
+the pages use <i>"Next"</i> and <i>"Back"</i>
+buttons in the lower part of the wizard window. <i>"Cancel"</i> button
+closes the wizard window and quits the installation procedure after user
+confirmation. <i>"Help"</i> button opens a window with the help information. </p>
+<p>The first "<span style="font-style: italic;">Introduction"</span>
+page is shown in <a href="#IntroPage">Figure 1</a>.
+Skip this page by pressing <i>"Next"</i> button:
+</p>
+<center><a name="IntroPage"></a><br>
+<img alt="Intro page" src="intropage.png" style="width: 606px; height: 422px;">
+<p><b>Figure 1:</b> "Introduction" page</p>
+</center>
+<p>In the second page you are proposed to select the type of the
+SALOME installation.<br>
+<br>
+At this step three possible types of installation are available:<br>
+</p>
+<ol>
+ <li><span style="font-style: italic;"> <font color="#ff0000"><b>"Install binaries"</b></font></span>
+type:<br>
+ <ul>
+ <li>all binaries and sources of the chosen modules are
+installed;</li>
+ <li>all binaries of the chosen prerequisites are installed.</li>