--- /dev/null
+================================================================================
+ README
+ SALOME Professional Installation Wizard
+================================================================================
+
+ Contents of this file:
+
+ 1. Running of the Installation Wizard
+
+ 2. Running of SALOME
+ 2.1. Setting of the environment for SALOME
+ 2.2. Launching of SALOME
+
+ 3. Installation notes
+ 3.1. Time required for the installation
+ 3.2. Log files
+ 3.3. Testing of the installed SALOME platform
+
+ 4. How to build SALOME from sources
+
+================================================================================
+
+ 1. Running of the Installation Wizard
+
+ You can run the Installation Wizard in two modes: batch and gui.
+ It's root directory contains python script runInstall.py:
+
+ [python] runInstall [-g|b] [-f <xml-file>] [-t <taget-dir>] [-tmp <tmp-dir>]
+
+ -g
+ 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.
+
+ -b
+ Runs the Installation Wizard in the batch mode.
+
+ -f <xml-file>
+ The configuration file to be used by the Installation Wizard.
+ If this parameter is missed then the script tries to define
+ the Red Hat version and use corresponding xml file.
+ For example, for the Red Hat 8.0 config_RedHat8_0.xml file
+ is supposed to be used by default. If the appropriate file
+ is not found, config.xml is used by default.
+
+ -t <target-dir>
+ The target directory, SALOME products to be installed to.
+ If used, overloads target directory, described in the
+ configuration file.
+
+ -tmp <tmp-dir>
+ The directory, which is used to contain temporary files.
+ If used, overloads temporary directory, described in the
+ configuration file.
+
+ -h
+ Prints help information.
+
+ For more detailed information about the Installation Wizard refer to the
+ readme.html file in the doc directory.
+
+================================================================================
+
+ 2. Running of SALOME
+
+ This section describes how to run SALOME platform after its installation with
+ the Installation Wizard.
+
+ 2.1. Setting of the environment for SALOME
+
+ Installation Wizard creates some environment files to simplify
+ the procedure of launching of SALOME. These shell scripts set all
+ necessary environment variables for all products you have installed.
+ These files are: salome.csh + salome.sh in the SALOME PRO sources and
+ SALOME PRO binaries root directories and env_products.csh +
+ env_products.sh in the target directory.
+
+ To set SALOME environment just type in the terminal window:
+
+ cd <SALOME_DIR>
+ source salome.sh
+ or
+ cd <SALOME_DIR>
+ source salome.csh
+
+ where <SALOME_DIR> is SALOME binaries directory, e.g. SalomePro-1.2d
+ for the 1.2d version.
+
+
+ 2.2. Launching of SALOME
+
+ After you set environment you can start SALOME. Go to the SALOME
+ binaries directory (SalomePro-1.2d for the version 1.2d) by using
+ of cd command and then type:
+
+ salome --gui
+
+ This will start SALOME servers and launch GUI desktop. If you want
+ to launch SALOME in the batch mode, use --batch option:
+
+ salome --batch
+
+ If you want to launch SALOME using specific port, use --port key:
+
+ salome --gui --port XXXX
+
+ where XXXX is a port number.
+ Note, that in this case you have to write the same port number into
+ your ORB configuration file, which should be referenced by the
+ $(OMNIORB_CONFIG) environment variable (usually it is an omniORB.cfg
+ file), e.g.:
+
+ ORBInitRef NameService=corbaname::<host-name>:<port-number>
+
+ <host-name> is a name of host where Naming Service should be run
+ and <port-number> is a number of port to be used.
+ The default port number is 2809. The using of non-default port
+ is useful when it is necessary for several users to launch
+ SALOME on the same host.
+
+ Use --help key to display additional information to learn other
+ salome script options.
+
+ Note: salome script is included into SALOME package only from 1.2d
+ version. In order to run salome for the previous versions you should
+ use runSalome script from the bin sub-directory of SALOME:
+
+ cd bin
+ runSalome
+
+================================================================================
+
+ 3. Installation notes
+
+ 3.1. Time required for the installation
+
+ Installation of all products which are necessary to build and
+ start SALOME is a time-consuming process and needs from the user to be
+ patient.
+ The quickest way to install SALOME is installation from the binaries.
+ In this mode the Installation Wizard just extracts all precompiled
+ products from the corresponding archives.
+ The installation from sources requires much more time than from
+ binaries because in this case the Installation Wizard extracts and
+ then builds each product using the product's own installation
+ procedure.
+ The installation time also depends on the computer and platform used.
+ For example, to install SALOME on Pentium III-800, Linux Red Hat 8.0,
+ time of the installation is:
+
+ - from binaries: ~10 minutes;
+ - from sources: up to 7 hours.
+
+ 3.2. Log files
+
+ The Installation Wizard displays the installation progress in the
+ corresponding windows (see readme.html). The Wizard uses a temporary
+ directory to store and build the products. During the installation
+ it produces some log files in this directory. If you suspect that
+ program hangs you can check the log files. These files have names
+ in capital letters like CONFIGURE.LOG, MAKE.LOG or MAKEINSTALL.LOG.
+
+ 3.3. Testing of installed SALOME platform
+
+ There is a python script which allows to test shortly all SALOME
+ modules. This script can help to check if SALOME has been installed
+ successfully.
+ To test SALOME platform, run SALOME desktop (see section 2), then
+ create a new study window (menu command 'File/New') and then type
+ in the study's python console window:
+
+ import salome_test
+
+ When running, the script loads diferent modules (Geometry, SMESH, Med,
+ Visu and Supervision) and tests different functionalty of these
+ modules. You can watch script running progress in the python console
+ window.
+
+================================================================================
+
+ 4. How to build SALOME from sources
+
+ If you want to build SALOME from sources, please install all products
+ necessary for the platform and then follow the scenario described below.
+ In the sample scenario it is supposed that you have installed SALOME
+ in the /home/salome directory. The name of the SALOME sources directory
+ depends on the version of the platform, in the scenario it is
+ SALOME_ROOT_1.2d (for the version 1.2d).
+
+ - go to SALOME sources directory:
+
+ cd /home/salome/SALOME_ROOT_1.2d
+
+ - set environment variables (use bash or csh script, depending on
+ your shell):
+
+ sources salome.c[s]h
+
+ - create a configuration script by typing
+
+ ./build_configure
+
+ - go to the parent directory and create a build directory:
+
+ cd ..
+ mkdir build
+
+ - configure the sources and create Makefile files:
+
+ cd build
+ ../SALOME_ROOT_1.2d/configure --prefix=/home/salome/SALOME
+
+ --prefix option defines the directory where you want to install
+ SALOME after make install procedure.
+
+ - build and install SALOME:
+
+ make
+ make install
+
+ - build and install SALOME documentation if necessary:
+
+ cd doc
+ make doc
+ make install
+
+ The last step is not necessary for the SALOME of version 1.2d, because
+ it is included into main make (and make install) step.
+
+ After you have completed this scenario, SALOME is built and installed
+ into /home/salome/SALOME directory.
+
+================================================================================
--- /dev/null
+<document>
+ <config version="1.2d"
+ caption="SALOME Professional v%1 Installation Wizard"
+ copyright="Copyright (C) 2003 CEA/DEN, EDF R&D"
+ license="All right reserved"
+ os="RedHat7.1"/>
+ <path targetdir="/tmp/salome"
+ tempdir="/tmp"/>
+ <product name="gcc"
+ version="2.95.3"
+ install="install sources"
+ supported="install sources"
+ disable="false"
+ dependancies=""
+ installdiskspace="193905"
+ temporarydiskspace="659468"
+ script="gcc-2.95.3.sh"/>
+ <product name="tcltk"
+ version="8.3.3"
+ install="install binaries"
+ supported="install sources,install binaries"
+ disable="false"
+ dependancies="gcc"
+ installdiskspace="30906"
+ temporarydiskspace="47748"
+ script="tcltk8.3.3.sh"/>
+ <product name="Python"
+ version="2.2.1"
+ install="install binaries"
+ supported="install sources,install binaries"
+ disable="false"
+ dependancies="gcc"
+ installdiskspace="30906"
+ temporarydiskspace="47748"
+ script="Python-2.2.1.sh"/>
+ <product name="Mesa"
+ version="3.4.2"
+ install="install binaries"
+ supported="install sources,install binaries"
+ disable="false"
+ dependancies="gcc"
+ installdiskspace="9995"
+ temporarydiskspace="44649"
+ script="Mesa-3.4.2.sh"/>
+ <product name="Qt"
+ version="3.0.5"
+ install="install binaries"
+ supported="install sources,install binaries"
+ disable="false"
+ dependancies="gcc,Mesa"
+ installdiskspace="76093"
+ temporarydiskspace="148942"
+ script="qt-x11-free-3.0.5.sh"/>
+ <product name="Sip"
+ version="3.3.2"
+ install="install binaries"
+ supported="install sources,install binaries"
+ disable="false"
+ dependancies="gcc,Python,Qt"
+ installdiskspace="199"
+ temporarydiskspace="818"
+ script="sip-3.3.2.sh"/>
+ <product name="PyQt"
+ version="3.3.2"
+ install="install binaries"
+ supported="install sources,install binaries"
+ disable="false"
+ dependancies="gcc,Python,Qt,Sip"
+ installdiskspace="46618"
+ temporarydiskspace="52789"
+ script="PyQt-3.3.2.sh"/>
+ <product name="Swig"
+ version="1.3.17"
+ install="install sources"
+ supported="install sources"
+ disable="false"
+ dependancies="gcc,Python,tcltk"
+ installdiskspace="1947"
+ temporarydiskspace="12308"
+ script="SWIG-1.3.17.sh"/>
+ <product name="OpenCascade"
+ version="4.0"
+ install="install binaries"
+ supported="install binaries"
+ disable="false"
+ dependancies=""
+ installdiskspace="264302"
+ temporarydiskspace="2"
+ script="CAS4.0.sh"/>
+ <product name="Qwt"
+ version="0.4.1"
+ install="install binaries"
+ supported="install sources,install binaries"
+ disable="false"
+ dependancies="gcc,Qt,Mesa"
+ installdiskspace="3045"
+ temporarydiskspace="3528"
+ script="qwt-0.4.1.sh"/>
+ <product name="Hdf"
+ version="5-1.4.4"
+ install="install binaries"
+ supported="install sources,install binaries"
+ disable="false"
+ dependancies="gcc"
+ installdiskspace="3163"
+ temporarydiskspace="24860"
+ script="hdf5-1.4.4.sh"/>
+ <product name="Med"
+ version="2.1.6"
+ install="install binaries"
+ supported="install sources,install binaries"
+ disable="false"
+ dependancies="gcc,Hdf"
+ installdiskspace="1067"
+ temporarydiskspace="7971"
+ script="med-2.1.6.sh"/>
+ <product name="Vtk"
+ version="4.2"
+ install="install binaries"
+ supported="install sources,install binaries"
+ disable="false"
+ dependancies="gcc,tcltk,Python,Mesa"
+ installdiskspace="38220"
+ temporarydiskspace="173232"
+ script="VTK-4.2.2.sh"/>
+ <product name="OmniORB"
+ version="3.0.5"
+ install="install binaries"
+ supported="install sources,install binaries"
+ disable="false"
+ dependancies="gcc,Python"
+ installdiskspace="342662"
+ temporarydiskspace="0"
+ script="omniORB-3.0.5.sh"/>
+ <product name="Numeric"
+ version="22.0"
+ install="install binaries"
+ supported="install sources,install binaries"
+ disable="false"
+ dependancies="gcc,Python"
+ installdiskspace="2625"
+ temporarydiskspace="8340"
+ script="Numeric-22.0.sh"/>
+ <product name="HappyDoc"
+ version="2.1"
+ install="install binaries"
+ supported="install sources,install binaries"
+ disable="false"
+ dependancies="Python"
+ installdiskspace="1482"
+ temporarydiskspace="4186"
+ script="HappyDoc-r2_1.sh"/>
+ <product name="Doxygen"
+ version="1.3-rc2"
+ install="install binaries"
+ supported="install sources,install binaries"
+ disable="false"
+ dependancies="gcc,Qt"
+ installdiskspace="6066"
+ temporarydiskspace="29083"
+ script="doxygen-1.3-rc2.sh"/>
+ <product name="Graphviz"
+ version="1.9"
+ install="install binaries"
+ supported="install sources,install binaries"
+ disable="false"
+ dependancies="gcc,tcltk"
+ installdiskspace="17724"
+ temporarydiskspace="61528"
+ script="graphviz-1.9.sh"/>
+ <product name="SalomePro-Src"
+ version="1.2d"
+ install="install sources"
+ supported="install sources"
+ disable="false"
+ dependancies="gcc,tcltk,OpenCascade,Python,Numeric,Swig,Qt,Qwt,Hdf,Med,Vtk,OmniORB,Sip,PyQt,Doxygen,Graphviz,HappyDoc"
+ installdiskspace="432954,39336"
+ temporarydiskspace="0"
+ script="SALOME_ROOT_1.2.sh"/>
+ <product name="SalomePro-Bin"
+ version="1.2d"
+ install="install binaries"
+ supported="install binaries"
+ disable="false"
+ dependancies="gcc,tcltk,OpenCascade,Python,Numeric,Swig,Qt,Qwt,Hdf,Med,Vtk,OmniORB,Sip,PyQt,Doxygen,Graphviz,HappyDoc"
+ installdiskspace="432954,39336"
+ temporarydiskspace="0"
+ script="SalomePro-1.2.sh"/>
+ <product name="SalomePro-Doc"
+ version="1.2d"
+ install="install sources"
+ supported="install sources"
+ disable="false"
+ dependancies=""
+ installdiskspace="6798"
+ temporarydiskspace="0"
+ script="SalomeDoc-1.2.sh"/>
+</document>
--- /dev/null
+<document>
+ <config version="1.2d"
+ caption="SALOME Professional v%1 Installation Wizard"
+ copyright="Copyright (C) 2003 CEA/DEN, EDF R&D"
+ license="All right reserved"
+ os="RedHat8.0"/>
+ <path targetdir="/tmp/salome"
+ tempdir="/tmp"/>
+ <product name="gcc"
+ version="3.2"
+ install="use native"
+ supported="use native"
+ disable="false"
+ dependancies=""
+ installdiskspace="193905"
+ temporarydiskspace="659468"
+ script="gcc-3.2.sh"/>
+ <product name="tcltk"
+ version="8.3.3"
+ install="use native"
+ supported="use native"
+ disable="false"
+ dependancies="gcc"
+ installdiskspace="30906"
+ temporarydiskspace="47748"
+ script="tcltk8.3.3.sh"/>
+ <product name="Python"
+ version="2.2.1"
+ install="use native"
+ supported="install sources,install binaries,use native"
+ disable="false"
+ dependancies="gcc"
+ installdiskspace="30906"
+ temporarydiskspace="47748"
+ script="Python-2.2.1.sh"/>
+ <product name="Mesa"
+ version="3.4.2"
+ install="install binaries"
+ supported="install sources,install binaries"
+ disable="false"
+ dependancies="gcc"
+ installdiskspace="9995"
+ temporarydiskspace="44649"
+ script="Mesa-3.4.2.sh"/>
+ <product name="Qt"
+ version="3.0.5"
+ install="use native"
+ supported="install sources,install binaries,use native"
+ disable="false"
+ dependancies="gcc,Mesa"
+ installdiskspace="76093"
+ temporarydiskspace="148942"
+ script="qt-x11-free-3.0.5.sh"/>
+ <product name="Sip"
+ version="3.3.2"
+ install="use native"
+ supported="install sources,install binaries,use native"
+ disable="false"
+ dependancies="gcc,Python,Qt"
+ installdiskspace="199"
+ temporarydiskspace="818"
+ script="sip-3.3.2.sh"/>
+ <product name="PyQt"
+ version="3.3.2"
+ install="use native"
+ supported="install sources,install binaries,use native"
+ disable="false"
+ dependancies="gcc,Python,Qt,Sip"
+ installdiskspace="46618"
+ temporarydiskspace="52789"
+ script="PyQt-3.3.2.sh"/>
+ <product name="Swig"
+ version="1.3.17"
+ install="install sources"
+ supported="install sources"
+ disable="false"
+ dependancies="gcc,Python,tcltk"
+ installdiskspace="1947"
+ temporarydiskspace="12308"
+ script="SWIG-1.3.17.sh"/>
+ <product name="OpenCascade"
+ version="4.0"
+ install="install binaries"
+ supported="install binaries"
+ disable="false"
+ dependancies=""
+ installdiskspace="264302"
+ temporarydiskspace="2"
+ script="CAS4.0.sh"/>
+ <product name="Qwt"
+ version="0.4.1"
+ install="install binaries"
+ supported="install sources,install binaries"
+ disable="false"
+ dependancies="gcc,Qt,Mesa"
+ installdiskspace="3045"
+ temporarydiskspace="3528"
+ script="qwt-0.4.1.sh"/>
+ <product name="Hdf"
+ version="5-1.4.4"
+ install="install binaries"
+ supported="install sources,install binaries"
+ disable="false"
+ dependancies="gcc"
+ installdiskspace="3163"
+ temporarydiskspace="24860"
+ script="hdf5-1.4.4.sh"/>
+ <product name="Med"
+ version="2.1.6"
+ install="install binaries"
+ supported="install sources,install binaries"
+ disable="false"
+ dependancies="gcc,Hdf"
+ installdiskspace="1067"
+ temporarydiskspace="7971"
+ script="med-2.1.6.sh"/>
+ <product name="Vtk"
+ version="4.2"
+ install="install binaries"
+ supported="install sources,install binaries"
+ disable="false"
+ dependancies="gcc,tcltk,Python,Mesa"
+ installdiskspace="34156"
+ temporarydiskspace="168048"
+ script="VTK-4.2.2.sh"/>
+ <product name="OmniORB"
+ version="3.0.5"
+ install="install binaries"
+ supported="install sources,install binaries"
+ disable="false"
+ dependancies="gcc,Python"
+ installdiskspace="342662"
+ temporarydiskspace="0"
+ script="omniORB-3.0.5.sh"/>
+ <product name="Numeric"
+ version="22.0"
+ install="install binaries"
+ supported="install sources,install binaries"
+ disable="false"
+ dependancies="gcc,Python"
+ installdiskspace="2625"
+ temporarydiskspace="8340"
+ script="Numeric-22.0.sh"/>
+ <product name="HappyDoc"
+ version="2.1"
+ install="install binaries"
+ supported="install sources,install binaries"
+ disable="false"
+ dependancies="Python"
+ installdiskspace="1482"
+ temporarydiskspace="4186"
+ script="HappyDoc-r2_1.sh"/>
+ <product name="Doxygen"
+ version="1.3-rc2"
+ install="install binaries"
+ supported="install sources,install binaries"
+ disable="false"
+ dependancies="gcc,Qt"
+ installdiskspace="6066"
+ temporarydiskspace="29083"
+ script="doxygen-1.3-rc2.sh"/>
+ <product name="Graphviz"
+ version="1.9"
+ install="install binaries"
+ supported="install sources,install binaries"
+ disable="false"
+ dependancies="gcc,tcltk"
+ installdiskspace="17724"
+ temporarydiskspace="61528"
+ script="graphviz-1.9.sh"/>
+ <product name="SalomePro-Src"
+ version="1.2d"
+ install="install sources"
+ supported="install sources"
+ disable="false"
+ dependancies="gcc,tcltk,OpenCascade,Python,Numeric,Swig,Qt,Qwt,Hdf,Med,Vtk,OmniORB,Sip,PyQt,Doxygen,Graphviz,HappyDoc"
+ installdiskspace="432954,39336"
+ temporarydiskspace="0"
+ script="SALOME_ROOT_1.2.sh"/>
+ <product name="SalomePro-Bin"
+ version="1.2d"
+ install="install binaries"
+ supported="install binaries"
+ disable="false"
+ dependancies="gcc,tcltk,OpenCascade,Python,Numeric,Swig,Qt,Qwt,Hdf,Med,Vtk,OmniORB,Sip,PyQt,Doxygen,Graphviz,HappyDoc"
+ installdiskspace="432954,39336"
+ temporarydiskspace="0"
+ script="SalomePro-1.2.sh"/>
+ <product name="SalomePro-Doc"
+ version="1.2d"
+ install="install sources"
+ supported="install sources"
+ disable="false"
+ dependancies=""
+ installdiskspace="6798"
+ temporarydiskspace="0"
+ script="SalomeDoc-1.2.sh"/>
+</document>
--- /dev/null
+#!/bin/sh
+
+check_version(){
+if [ -n "${SALOMEPRO_SRC}" ]; then
+ check_lib_version VERSION ${SALOMEPRO_SRC}/bin
+ if [ "$?" -eq "0" ]; then
+ ver=`cat ${SALOMEPRO_SRC}/bin/VERSION | awk -F: '{print $2}' | tr -d '[:space:]' `
+ if [ "$ver" = "1.2d" ]; then
+ return 0
+ fi
+ fi
+fi
+return 1
+}
+
+print_env(){
+cat > ${INSTALL_WORK}/env_${PRODUCT_TYPE}.sh <<EOF
+#$DELIM ${PRODUCT_TYPE} $DELIM
+export SALOMEPRO_SRC=\${INSTALL_ROOT}/${PRODUCT}
+##
+EOF
+(test -w ${PRODUCT_DIR} && cp ${INSTALL_WORK}/env_${PRODUCT_TYPE}.sh ${PRODUCT_DIR})
+(make_env ${INSTALL_ROOT} ${INSTALL_WORK} "${PRODUCT_SEQUENCE}" ${PRODUCT_TYPE} ${PRODUCT_DIR})
+}
+
+# looks for the native product and collects it's environment (used by make_env())
+try_native(){
+check_version
+if [ $? -eq 0 ] ; then
+ cat > ${INSTALL_WORK}/env_${PRODUCT_TYPE}.sh <<EOF
+#$DELIM ${PRODUCT_TYPE} $DELIM
+export SALOMEPRO_SRC=${SALOMEPRO_SRC}
+##
+EOF
+ make_env ${INSTALL_ROOT} ${INSTALL_WORK} "${PRODUCT_SEQUENCE}"
+ return 0
+fi
+return 1;
+}
+
+try_preinstalled(){
+try_existing ${PRODUCT_DIR} ${INSTALL_ROOT} ${INSTALL_WORK} "${PRODUCT_SEQUENCE}" ${PRODUCT_TYPE}
+return $?
+}
+
+install_source()
+{
+make_env ${INSTALL_ROOT} ${INSTALL_WORK} "${PRODUCT_SEQUENCE}" ${PRODUCT_TYPE}
+source ${INSTALL_WORK}/$SHRC
+
+check_jb tar xfz ${SOURCE_DIR}/SALOMEPROsourcesV1.2d.tar.gz -C ${INSTALL_ROOT}
+
+print_env
+}
+
+install_binary()
+{
+return 1
+}
+
+export PROCEDURE=$1;
+export INSTALL_WORK=$2;
+export SOURCE_DIR=$3;
+export INSTALL_ROOT=$4;
+export PRODUCT_SEQUENCE=$5;
+if [ $# == 6 ] ; then export PRODUCT_TYPE=$6 ; else export PRODUCT_TYPE="salomesources" ; fi
+export PRODUCT="SALOME_ROOT_1.2d"
+export PRODUCT_DIR=${INSTALL_ROOT}/${PRODUCT}
+export PRODUCT_WORK=${INSTALL_WORK}/${PRODUCT}
+source ./common.sh
+$PROCEDURE
--- /dev/null
+#!/bin/sh
+
+check_version(){
+if [ -n "${SALOME_ROOT_DIR}" ]; then
+ check_lib_version VERSION ${SALOME_ROOT_DIR}/bin
+ if [ "$?" -eq "0" ]; then
+ ver=`cat ${SALOME_ROOT_DIR}/bin/VERSION | awk -F: '{print $2}' | tr -d '[:space:]' `
+ if [ "$ver" = "1.2d" ]; then
+ return 0
+ fi
+ fi
+fi
+return 1
+}
+
+print_env(){
+cat > ${INSTALL_WORK}/env_${PRODUCT_TYPE}.sh <<EOF
+#$DELIM ${PRODUCT_TYPE} $DELIM
+export SALOME_ROOT_DIR=\${INSTALL_ROOT}/${PRODUCT}
+export PYTHONPATH=\${SALOME_ROOT_DIR}/bin:\${SALOME_ROOT_DIR}/lib:\${SALOME_ROOT_DIR}/lib/python2.2/site-packages/salome:\${PYTHONPATH}
+export LD_LIBRARY_PATH=\${SALOME_ROOT_DIR}/lib:\${LD_LIBRARY_PATH}
+export PATH=.:\${SALOME_ROOT_DIR}/bin:\${PATH}
+##
+EOF
+(test -w ${PRODUCT_DIR} && cp ${INSTALL_WORK}/env_${PRODUCT_TYPE}.sh ${PRODUCT_DIR})
+(make_env ${INSTALL_ROOT} ${INSTALL_WORK} "${PRODUCT_SEQUENCE}" ${PRODUCT_TYPE} ${PRODUCT_DIR})
+}
+
+# looks for the native product and collects it's environment (used by make_env())
+try_native(){
+check_version
+if [ $? -eq 0 ] ; then
+ cat > ${INSTALL_WORK}/env_${PRODUCT_TYPE}.sh <<EOF
+#$DELIM ${PRODUCT_TYPE} $DELIM
+export SALOME_ROOT_DIR=\${INSTALL_ROOT}/${PRODUCT}
+export PYTHONPATH=\${SALOME_ROOT_DIR}/bin:\${SALOME_ROOT_DIR}/lib:\${SALOME_ROOT_DIR}/lib/python2.2/site-packages/salome:\${PYTHONPATH}
+export LD_LIBRARY_PATH=\${SALOME_ROOT_DIR}/lib:\${LD_LIBRARY_PATH}
+export PATH=.:\${SALOME_ROOT_DIR}/bin:\${PATH}
+##
+EOF
+ make_env ${INSTALL_ROOT} ${INSTALL_WORK} "${PRODUCT_SEQUENCE}"
+ return 0
+fi
+return 1;
+}
+
+try_preinstalled(){
+try_existing ${PRODUCT_DIR} ${INSTALL_ROOT} ${INSTALL_WORK} "${PRODUCT_SEQUENCE}" ${PRODUCT_TYPE}
+return $?
+}
+
+install_source()
+{
+return 1
+}
+
+install_binary()
+{
+make_env ${INSTALL_ROOT} ${INSTALL_WORK} "${PRODUCT_SEQUENCE}" ${PRODUCT_TYPE}
+source ${INSTALL_WORK}/$SHRC
+
+check_jb tar xfz ${SOURCE_DIR}/SALOMEPRObinariesV1.2d.tar.gz -C ${INSTALL_ROOT}
+
+print_env
+}
+
+export PROCEDURE=$1;
+export INSTALL_WORK=$2;
+export SOURCE_DIR=$3;
+export INSTALL_ROOT=$4;
+export PRODUCT_SEQUENCE=$5;
+if [ $# == 6 ] ; then export PRODUCT_TYPE=$6 ; else export PRODUCT_TYPE="salomebin" ; fi
+export PRODUCT="SalomePro-1.2d"
+export PRODUCT_DIR=${INSTALL_ROOT}/${PRODUCT}
+export PRODUCT_WORK=${INSTALL_WORK}/${PRODUCT}
+source ./common.sh
+$PROCEDURE
--- /dev/null
+#!/bin/sh
+
+check_version()
+{
+check_lib_version doxygen $PATH
+if [ "$?" -ne "0" ]; then
+ return 1
+fi
+check_lib_version doxysearch $PATH
+if [ "$?" -ne "0" ]; then
+ return 1
+fi
+check_lib_version doxytag $PATH
+if [ "$?" -ne "0" ]; then
+ return 1
+fi
+check_lib_version doxywizard $PATH
+if [ "$?" -eq "0" ]; then
+ #echo "The product ${PRODUCT} has been already installed on yours system"
+ return 0
+fi
+return 1
+}
+
+print_env()
+{
+cat > ${INSTALL_WORK}/env_${PRODUCT_TYPE}.sh <<EOF
+#$DELIM ${PRODUCT_TYPE} $DELIM
+export PATH=\${INSTALL_ROOT}/${PRODUCT}/bin:\${PATH}
+##
+EOF
+(test -w ${PRODUCT_DIR} && cp ${INSTALL_WORK}/env_${PRODUCT_TYPE}.sh ${PRODUCT_DIR})
+make_env ${INSTALL_ROOT} ${INSTALL_WORK} "${PRODUCT_SEQUENCE}"
+}
+
+# looks for the native product and collects it's environment (used by make_env())
+try_native(){
+check_version
+if [ $? -eq 0 ] ; then
+ doxygen="`find_in_path doxygen ${PATH}`"
+ tmp="${doxygen} ${doxygen} \${PATH} ${PATH}";
+ path=`sort_path ${tmp}`
+ cat > ${INSTALL_WORK}/env_${PRODUCT_TYPE}.sh <<EOF
+#$DELIM ${PRODUCT_TYPE} $DELIM
+export PATH=${path}
+##
+EOF
+ make_env ${INSTALL_ROOT} ${INSTALL_WORK} "${PRODUCT_SEQUENCE}"
+ return 0
+fi
+return 1;
+}
+
+try_preinstalled(){
+try_existing ${PRODUCT_DIR} ${INSTALL_ROOT} ${INSTALL_WORK} "${PRODUCT_SEQUENCE}" ${PRODUCT_TYPE}
+return $?
+}
+
+install_source()
+{
+make_env ${INSTALL_ROOT} ${INSTALL_WORK} "${PRODUCT_SEQUENCE}" env_${PRODUCT_TYPE}.sh
+source ${INSTALL_WORK}/$SHRC
+
+check_jb tar xfz ${SOURCE_DIR}/doxygen-1.3-rc2.tar.gz -C ${INSTALL_WORK}
+
+cd ${PRODUCT_WORK}
+makedir ${PRODUCT_DIR}
+check_job ${PRODUCT_DIR}/CONFIGURE.LOG configure --with-doxywizard --prefix ${PRODUCT_DIR}
+GCC=`which gcc`
+cat >> ${PRODUCT_DIR}/MAKE.LOG <<EOF
+used gcc=$GCC
+EOF
+check_job ${PRODUCT_DIR}/MAKE.LOG make
+check_job ${PRODUCT_DIR}/MAKEINSTALL.LOG make install
+
+which epstopdf >/dev/null 2>&1; ISFOUND=$?
+if [ ${ISFOUND} -eq 0 ] ; then which makeindex >/dev/null 2>&1; ISFOUND=$?; fi
+if [ ${ISFOUND} -eq 0 ] ; then which latex >/dev/null 2>&1; ISFOUND=$?; fi
+if [ ${ISFOUND} -eq 0 ] ; then which latex2html >/dev/null 2>&1; ISFOUND=$?; fi
+if [ ${ISFOUND} -eq 0 ] ; then which pdflatex >/dev/null 2>&1; ISFOUND=$?; fi
+if [ ${ISFOUND} -eq 0 ] ; then which pslatex >/dev/null 2>&1; ISFOUND=$?; fi
+if [ ${ISFOUND} -eq 0 ] ; then which pstoimg >/dev/null 2>&1; ISFOUND=$?; fi
+if [ ${ISFOUND} -eq 0 ] ; then
+ check_job ${PRODUCT_DIR}/MAKEDOCS.LOG make docs
+ check_job ${PRODUCT_DIR}/MAKEINSTALLDOCS.LOG make install_docs
+else
+ cat >> ${PRODUCT_DIR}/MAKEDOCS.LOG <<EOF
+Can't find \"epstopdf\" and \"latex\" or another executables on the computer.
+doxygen documentation will not be built!
+SALOME DOCUMENTATION ALSO CAN NOT BE BUILT!
+EOF
+ check_job ${PRODUCT_DIR}/MAKEDOCS.LOG make docs
+ rm -fr ${PRODUCT_WORK}
+# echo -e "Can't find \"epstopdf\" and \"latex\" or another executables on the computer."
+# echo -e "doxygen documentation will not be built!"
+# echo -e "SALOME DOCUMENTATION ALSO CAN NOT BE BUILT!"
+# echo -n "Would you like continue : (Y,N) [Y] : "
+# read rep;
+# rep=`echo $rep | tr "[A-Z]" "[a-z]"`
+# if test -z $rep || [ $rep != "y" ] ; then
+# rm -fr ${PRODUCT_WORK}
+# exit 1
+# fi
+fi
+
+rm -fr ${PRODUCT_WORK}
+print_env
+}
+
+install_binary()
+{
+make_env ${INSTALL_ROOT} ${INSTALL_WORK} "${PRODUCT_SEQUENCE}" env_${PRODUCT_TYPE}.sh
+source ${INSTALL_WORK}/$SHRC
+
+check_jb tar xfz ${SOURCE_DIR}/doxygen-1.3-rc2.tar.gz -C ${INSTALL_ROOT}
+which epstopdf >/dev/null 2>&1; ISFOUND=$?
+if [ ${ISFOUND} -eq 0 ] ; then which makeindex >/dev/null 2>&1; ISFOUND=$?; fi
+if [ ${ISFOUND} -eq 0 ] ; then which latex >/dev/null 2>&1; ISFOUND=$?; fi
+if [ ${ISFOUND} -eq 0 ] ; then which latex2html >/dev/null 2>&1; ISFOUND=$?; fi
+if [ ${ISFOUND} -eq 0 ] ; then which pdflatex >/dev/null 2>&1; ISFOUND=$?; fi
+if [ ${ISFOUND} -eq 0 ] ; then which pslatex >/dev/null 2>&1; ISFOUND=$?; fi
+if [ ${ISFOUND} -eq 0 ] ; then which pstoimg >/dev/null 2>&1; ISFOUND=$?; fi
+if [ ${ISFOUND} -ne 0 ] ; then
+ cat >> ${PRODUCT_DIR}/DOCS.LOG <<EOF
+Can't find \"epstopdf\" and \"latex\" or another executables on the computer.
+doxygen documentation will not be built!
+SALOME DOCUMENTATION ALSO CAN NOT BE BUILT!
+EOF
+ check_job ${PRODUCT_DIR}/DOCS.LOG make
+ rm -fr ${PRODUCT_WORK}
+# echo -e "Can't find \"epstopdf\" and \"latex\" or another executables on the computer."
+# echo -e "doxygen documentation will not be built!"
+# echo -e "SALOME DOCUMENTATION ALSO CAN NOT BE BUILT!"
+# echo -n "Would you like continue : (Y,N) [Y] : "
+# read rep;
+# rep=`echo $rep | tr "[A-Z]" "[a-z]"`
+# if test -z $rep || [ $rep != "y" ] ; then
+# rm -fr ${PRODUCT_WORK}
+# exit 1
+# fi
+fi
+
+print_env
+}
+
+export PROCEDURE=$1;
+export INSTALL_WORK=$2;
+export SOURCE_DIR=$3;
+export INSTALL_ROOT=$4;
+export PRODUCT_SEQUENCE=$5;
+if [ $# == 6 ] ; then export PRODUCT_TYPE=$6 ; else export PRODUCT_TYPE="doxygen" ; fi
+export PRODUCT="doxygen-1.3-rc2"
+export PRODUCT_DIR=${INSTALL_ROOT}/${PRODUCT}
+export PRODUCT_WORK=${INSTALL_WORK}/${PRODUCT}
+source ./common.sh
+$PROCEDURE
--- /dev/null
+#!/bin/sh
+
+check_version()
+{
+if [ -z "$HDF5HOME" ]; then
+ #echo "HDF5HOME doesn't set"
+ return 1
+fi
+check_lib_version libhdf5.so.0.0.0 ${HDF5HOME}/lib
+if [ "$?" -ne "0" ]; then
+ return 1
+fi
+#check libhdf5.settings file in a ${HDF5HOME}/lib
+check_lib_version libhdf5.settings ${HDF5HOME}/lib
+if [ "$?" -eq "0" ]; then
+ #check that libhdf5.settings file contains following entry:
+ #HDF5 Version: hdf5-1.4.4
+ entry=`grep "HDF5 Version:" ${HDF5HOME}/lib/libhdf5.settings`
+ ver=`echo $entry | awk '{print $3}'`
+ if [ "$ver" = "1.4.4" ]; then
+ #echo "The product ${PRODUCT} has been already installed on yours system"
+ return 0
+ fi
+fi
+return 1
+}
+
+print_env()
+{
+cat > ${INSTALL_WORK}/env_${PRODUCT_TYPE}.sh <<EOF
+#$DELIM ${PRODUCT_TYPE} $DELIM
+export HDF5HOME=\${INSTALL_ROOT}/hdf5-1.4.4
+export PATH=\${HDF5HOME}/bin:\$PATH
+export LD_LIBRARY_PATH=\${HDF5HOME}/lib:\${LD_LIBRARY_PATH}
+##
+EOF
+(test -w ${PRODUCT_DIR} && cp ${INSTALL_WORK}/env_${PRODUCT_TYPE}.sh ${PRODUCT_DIR})
+make_env ${INSTALL_ROOT} ${INSTALL_WORK} "${PRODUCT_SEQUENCE}"
+}
+
+# looks for the native product and collects it's environment (used by make_env())
+try_native(){
+check_version
+if [ $? -eq 0 ] ; then
+ tmp="\${HDF5HOME}/bin ${HDF5HOME}/bin \${PATH} ${PATH}";
+ path=`sort_path ${tmp}`
+ tmp="\${HDF5HOME}/lib ${HDF5HOME}/lib \${LD_LIBRARY_PATH} ${LD_LIBRARY_PATH}";
+ ld_library_path=`sort_path ${tmp}`
+ cat > ${INSTALL_WORK}/env_${PRODUCT_TYPE}.sh <<EOF
+#$DELIM ${PRODUCT_TYPE} $DELIM
+export HDF5HOME=${HDF5HOME}
+export PATH=${path}
+export LD_LIBRARY_PATH=${ld_library_path}
+##
+EOF
+ make_env ${INSTALL_ROOT} ${INSTALL_WORK} "${PRODUCT_SEQUENCE}"
+ return 0
+fi
+return 1;
+}
+
+try_preinstalled(){
+try_existing ${PRODUCT_DIR} ${INSTALL_ROOT} ${INSTALL_WORK} "${PRODUCT_SEQUENCE}" ${PRODUCT_TYPE}
+return $?
+}
+
+install_source()
+{
+make_env ${INSTALL_ROOT} ${INSTALL_WORK} "${PRODUCT_SEQUENCE}" ${PRODUCT_TYPE}
+source ${INSTALL_WORK}/$SHRC
+
+check_jb tar xfz ${SOURCE_DIR}/hdf5-1.4.4.tar.gz -C ${INSTALL_WORK}
+cd ${PRODUCT_WORK}
+makedir ${PRODUCT_DIR}
+check_job ${PRODUCT_DIR}/CONFIGURE.LOG \
+ ./configure --prefix=${PRODUCT_DIR} --enable-threadsafe --enable-hdf5v1_2 \
+ --enable-stream-vfd --disable-hsizet --with-pthread=/usr/include,/usr/lib
+# find . -name .depend ! -size 0 -print
+GCC=`which gcc`
+cat >> ${PRODUCT_DIR}/MAKE0.LOG <<EOF
+used gcc=$GCC
+EOF
+check_job ${PRODUCT_DIR}/MAKE0.LOG make
+# 1
+sed -e 's%$(srcdir)/usr%/usr%g' ./src/.depend > ./src/.dependnew
+mv ./src/.dependnew ./src/.depend
+cat >> ${PRODUCT_DIR}/MAKE1.LOG <<EOF
+used gcc=$GCC
+EOF
+check_job ${PRODUCT_DIR}/MAKE1.LOG make
+# 2
+sed -e 's%$(srcdir)/usr%/usr%g' ./test/.depend > ./test/.dependnew
+mv ./test/.dependnew ./test/.depend
+cat >> ${PRODUCT_DIR}/MAKE2.LOG <<EOF
+used gcc=$GCC
+EOF
+check_job ${PRODUCT_DIR}/MAKE2.LOG make
+# 3
+sed -e 's%$(srcdir)/usr%/usr%g' ./tools/lib/.depend > ./tools/lib/.dependnew
+mv ./tools/lib/.dependnew ./tools/lib/.depend
+cat >> ${PRODUCT_DIR}/MAKE3.LOG <<EOF
+used gcc=$GCC
+EOF
+check_job ${PRODUCT_DIR}/MAKE3.LOG make
+# 4
+sed -e 's%$(srcdir)/usr%/usr%g' ./tools/h5dump/.depend > ./tools/h5dump/.dependnew
+mv ./tools/h5dump/.dependnew ./tools/h5dump/.depend
+cat >> ${PRODUCT_DIR}/MAKE4.LOG <<EOF
+used gcc=$GCC
+EOF
+check_job ${PRODUCT_DIR}/MAKE4.LOG make
+# 5
+sed -e 's%$(srcdir)/usr%/usr%g' ./tools/h5ls/.depend > ./tools/h5ls/.dependnew
+mv ./tools/h5ls/.dependnew ./tools/h5ls/.depend
+cat >> ${PRODUCT_DIR}/MAKE5.LOG <<EOF
+used gcc=$GCC
+EOF
+check_job ${PRODUCT_DIR}/MAKE5.LOG make
+# 6
+sed -e 's%$(srcdir)/usr%/usr%g' ./tools/misc/.depend > ./tools/misc/.dependnew
+mv ./tools/misc/.dependnew ./tools/misc/.depend
+cat >> ${PRODUCT_DIR}/MAKE6.LOG <<EOF
+used gcc=$GCC
+EOF
+check_job ${PRODUCT_DIR}/MAKE6.LOG make
+# 7
+#sed -e 's%$(srcdir)/usr%/usr%g' ./examples/.depend > ./examples/.dependnew
+#mv ./examples/.dependnew ./examples/.depend
+#cat >> ${PRODUCT_DIR}/MAKE7.LOG <<EOF
+#used gcc=$GCC
+#EOF
+#check_job ${PRODUCT_DIR}/MAKE7.LOG make
+##
+#check_job ${PRODUCT_DIR}/MAKECHECK.LOG make check
+check_job ${PRODUCT_DIR}/MAKEINSTALL.LOG make install
+
+rm -fr ${PRODUCT_WORK}
+print_env
+}
+
+install_binary()
+{
+make_env ${INSTALL_ROOT} ${INSTALL_WORK} "${PRODUCT_SEQUENCE}" ${PRODUCT_TYPE}
+source ${INSTALL_WORK}/$SHRC
+
+check_jb tar xfz ${SOURCE_DIR}/hdf5-1.4.4.tar.gz -C ${INSTALL_ROOT}
+
+print_env
+}
+
+export PROCEDURE=$1;
+export INSTALL_WORK=$2;
+export SOURCE_DIR=$3;
+export INSTALL_ROOT=$4;
+export PRODUCT_SEQUENCE=$5;
+if [ $# == 6 ] ; then export PRODUCT_TYPE=$6 ; else export PRODUCT_TYPE="hdf" ; fi
+export PRODUCT="hdf5-1.4.4"
+export PRODUCT_DIR=${INSTALL_ROOT}/${PRODUCT}
+export PRODUCT_WORK=${INSTALL_WORK}/${PRODUCT}
+source ./common.sh
+$PROCEDURE
--- /dev/null
+<!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>
+</head>
+<body text="#000000" bgcolor="#FFFFE5" link="#0000EE" vlink="#551A8B" alink="#FF0000">
+
+<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>
+
+<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>
+</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
+click
+<i>"Help"</i> button.
+<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
+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.
+<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.
+<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
+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
+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
+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:
+<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>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:
+<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
+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>
+<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
+'[: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>
+</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.
+<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>
+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.
+<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>
+<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
+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>
+<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
+the ./Products/BINARIES directory.</font></li>
+</ul>
+
+<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>
+</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.
+<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
+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
+next section for more details.
+<p>
+<hr>
+<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
+script. These functions are automatically called by master installation
+script or/and GUI shell when it is necessary.
+<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>)
+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>
+</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>
+</body>
+</html>
