-
-
- |
-
-
-SALOME Professional Installation Wizard -Help |
-
-
- |
-
-
-
- |
-
-
-SALOME Professional Installation Wizard -Help |
-
-
- |
-
|
+ |
+
+ SALOME Installation +Wizard Help+ |
+
+ |
+
[ python ] runInstall [ -g | b ] [ -f <xml-file> ] [ -t <target-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 examle, 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.
-
So, to run the Installation Wizard in the GUI mode, just type runInstall. -
The installation procedure can support some different Linux platforms
-(currently it provides configuration scripts for RedHat-7.1 and
-RedHat-8.0)
-and various number of products.
-
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
-modifying
-XML configuration file and implementing installation
-scripts for the new products for more information.
-
The Installation Wizard was built with -using of the Qt library. The program contains several -pages. To navigate between pages use "Next" and "Back" buttons -in the lower part of the wizard window. "Cancel" button closes dialog -window and quits the installation procedure. To invoke this help information -click -"Help" button. -
Skip the first "Introduction" page by pressing "Next" -button. -
In the second page you are proposed to enter the target directory where
-all selected products will be installed to. You can also press "Browse..."
-button and choose the folder for installation using standard Qt
-browse directory dialog box.
-
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.
-
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 "More..." button. +
[ python ] runInstall [options]
+
Without options this script will launch the SALOME Installation
+Wizard in the default mode (GUI).
+The default installation settings can be overriden by using of command
+line options. Each
+option has short and long notations:
+
-g / --gui
+
-b / --batch
+
-f FILE / --file=FILE
+
-d DIR / --target=DIR
+
-t DIR / --tmp=DIR
+-a / --all-from-sources
+ +-h / --help
+
+-v / --version
+
+
+The installation procedure supports different Linux
+platforms
+and installs various installation 3d-party prerequisite products which
+are required by SALOME platform. As it was mentioned above, the basic
+target platform for SALOME 3.0 and newer is Linux Mandrake 10.1.
+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 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 Linux
+platform which is not supported directly by the Installation
+Wizard. See Modifying XML configuration file
+and Implementing installation scripts for the
+new products sections for more information.
The Installation Wizard's GUI has been +developed +with +using of the Trolltech's Qt +3.0.5 toolkit. 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 "Next" and "Back" +buttons in the +lower part of the wizard window. "Cancel" button closes the +wizard +window and quits the installation procedure after user's +confirmation. "Help" button opens an additional window to show +the help information.
+The first "Introduction" +page is shown at the Figure 1. Skip this page +by pressing "Next" +button: +
+
+Figure 1: "Introduction" page
+In the second page you are proposed to enter the target directory
+where the SALOME platform should be installed to. You can also press "Browse..."
+button and choose the destination folder using standard browse
+directory dialog box.
+If the directory you want to install products does not exist you are
+prompted to confirm directory creation. If you type wrong directory
+path, or if you do not have write permissions for the directory you
+use, the
+corresponding message box is shown.
+
You can also change the temporary directory (which is used to store
+temporary files required for the installation).
+In the bottom part of the window the total disk space required for the
+installation and for the temporary files is displayed (see below for
+more details).
+
In the GUI mode the Installation Wizard provides two different
+options
+to install the SALOME platform: basic
+(which is default) and
+advanced. In the basic mode the
+user should enter the target installation
+directory and temporary folder. All other installation options are
+taken from the XML
+configuration file (see Fig.2):
+
+Figure 2: "Installation settings" +
+In addition, you have choice to use "Install all products from
+sources" check box. If this option is turned on, all the products will
+be installed from the sources (using their own build procedures). This
+check box correspond to the --all-from-sources
+(-a) option of the runInstall script (see here). Note: the installation of all
+products from sources is a long-time operation.
+
To switch to the advanced +option, click "More..." button (see Fig.3 +).
In the advanced mode you have the possibility to select products to
-be installed (see Fig.1 ). 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 pyqt it's necessary to have
-gcc, python,
-qt and
-sip installed. Therefore all these products
-will be marked when you check on
-pyqt. This feature can be
-switched off by clicking "Auto set prerequisites products" checkbox.
-
Special button in the right part of the page - "Unselect All" -
-allows to reset quickly all products to the "not install" state.
-
If you want to use native Linux Red Hat 8.0 products (these are gcc,
-tcl, Python, Qt, Sip and PyQt), select "use native" option.
+be installed. Each product can
+have several options of installation: you have a possibility to use
+native product (provided with Linux distribution and installed in the
+system folders), install already precompiled binaries, build product
+from the sources or not install it at all. Avaiable options and default
+option are taken from the XML 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 may require some other pre-requisite products to be
+installed (or
+these prerequisite products should be already available 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 PyQt it's necessary to
+have
+gcc, Python, Qt and Sip
+installed.
+Therefore all these products will be also turned on when you check on PyQt.
+This feature can be switched off by clicking "Automatic
+dependencies" checkbox. Turn on this checkbox if you
+want all prerequisite products to be automatically checked when you
+select some product to be installed. Turn off this checkbox if you
+want to disable this feature.
+
+Figure 3: "Installation settings" page in the 'advanced' mode
+If you want to use native products (like gcc, tcl, etc.), select "use native" option.
+
+Special button in the right part of the page - "Unselect All" -
+allows to reset quickly all products to the "not install"
+state.
+
There are also two checkboxes on this page: "SALOME sources"
+and "SALOME binaries".
+These three-state checkboxes allow quick selecting/unselecting SALOME
+modules sources/binaries packages
+for the installation.
+
In addition, when some SALOME sources are selected, one more check
+box becomes available: "Build SALOME
+sources". If this option is turned on, the selected SALOME
+modules will be built and installed from sources.
+Note: if this check box is turned on,
+the corresponding SALOME module binaries package installation is
+disabled, because of conflicting of SALOME module sources an binaries
+packages (see Fig. 4 below).
+
+Figure 4: "Build SALOME sources" check box usage
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. -
-Figure 1: "Installation settings" page in the advanced mode
The "Total disk space required:" field displays how much disk
-space on the hard drive is required for installation of selected products.
-
Note: Please, take into account that displayed amount of required
-disk space is approximate and may differ when you install products on your
-hard drive.
-
Installation procedure uses a special directory to store temporary files. -The "Space for temporary files:" 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 and short description, +required +disk space, disk space required for temporary files, list of +prerequisites (this information is +provided in the XML file) and current user +choice. +
+The "Disk space required:" field displays how much +disk space on the hard drive is required for installation of selected +products.Note: Please, take into account that displayed amount of +required disk space is approximate and may differ when you install +products on your hard drive.
+The installation procedure uses a special directory to store +temporary files. The "Space for temporary files:" field shows +the information about required disk space on the hard drive for +extracting and compiling of the selected products. You can change the +temporary directory - just type path to the folder you want to use or click on the corresponding "Browse..." -button. -
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. -
Note: 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 gcc won't -work if you pass the following parameter: --prefix="/New Folder 1". -Therefore -you are strongly recommended not to use directory names containing spaces. -
To proceed further click "Next" button. At this moment program
+button.
+Note: actually, temporary files
+are stored not directly in the directory entered by user. The
+Installation
+Wizard creates in this directory an additional folder named
+something like INSTALLWORKXXXXX
+where XXXXX is unique number. This allows to launch several
+Installation Wizards simultaneously. This temporary directory is
+removed automaticaly when the installation finishes.
+
The installation procedure also checks available disk space. If +there is no +enough disk space on your hard drive you will see the corresponding +error message box.
+Note: you are strongly recommended not to use directory +names +containing +spaces. Otherwise you can experience some troubles with the +installation.
+To proceed further click "Next" 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, check for native products installation, +dependencies +(prerequisites) for each product you have selected to be +installed. +If any test fails you will see the corresponding warning message box. +Otherwise +the wizard will proceed to the next page:
Figure 2: "Check your choice" page
This page summarizes the installation settings you've made on the previous
-pages. You can check again your choice to change it if necessary.
-
When you are sure that everything is OK, press "Next" button
-to follow to the next page.
-
-Figure 3: "Installation progress" page
To start installation of the selected products click "Start"
+
+
+
Figure 5: "Check your choice" page
+ +This page summarizes the installation options you've made on the
+previous pages. You can check again your choice and change it if
+necessary by getting back to previous page.
+When you are sure that everything is OK, press "Next" button to
+follow to the next page.
Figure 6: "Installation progress" page
+The "Installation Status" frame window shows you the progress -of installation. It contains a list of all selected products with brief -descriptions. "Waiting" description means -that installation of this product have not started yet. Currently installing -product is marked as "Processing". All installed -products have "Completed" description. -
You can abort installation and close the installation procedure using -"Cancel" -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. -
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 "Next" button to go the Readme page:
+to see the output of the script in the topmost dialog's frame. If any
+errors
+occur during the installation progress the corresponding messages
+will be printed to the log window in the bold red font.
+
Note:
+in the current
+implementation it is not possible to resume stopped installation
+process; it will be re-started from the very beginning.
+
+Figure 7: "Installation progress" page: installation in +progress
+The "Installation Status" frame window shows you the +progress of installation. "Waiting" status +means that installation of this product has not been started +yet. The product currently being installed is marked as "Processing". +All installed products have "Completed" +status.
+You can abort installation and close the installation procedure
+using
+"Cancel" button.
+Note: this button sends the
+signal "SIGTERM" to the shell
+script.
+The script tries 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.
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 "Next" button to go the Readme page:
Figure 4: "Finish installation" page
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.
-
You can also launch SALOME Desktop from this page by clicking "Launch
-SALOME" button.
-
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 -here. 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. -
Figure 8: "Finish installation" page
+ +In this page you can read important information about the
+Instalation Wizard itself and some tips: 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.
+You can also launch SALOME Desktop from this
+page or read Release Notes file by clicking on the corresponding
+buttons in the lower part of the page (see here
+and here for more information about
+customizing these buttons).
+
+Figure 9: Batch mode
+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 here. These files are: salome.csh + salome.sh
+in the KERNEL module sources
+and KERNEL
+module binaries root directories and env_products.csh
++ env_products.sh and env_build.csh
++ env_build.sh in the
+target installation directory.
+
If you have native products installed to different from +default +directories (not /usr/bin, /usr/lib...), it is +recommended to follow above mentioned instructions. Or you should +properly set PATH and LD_LIBRARY_PATH variables before +starting the Installation Wizard. Otherwise +the installation script will fail to find preinstalled/native products. +
+Note: for some native products (e.g. gcc, Python) the rules
+of version
+checking are not so strict as described in the table. Only major and
+minor numbers of version
+should coincide with prerequisite. Newer version of the product can be
+used also. If some native product has version number larger than that
+required by
+the
+installation procedure, user will be prompted by the warning message
+like this: "You have
+newer version of gcc installed
+on your computer than that is required (3.4.1). Continue?". You can
+press "Yes" button
+to proceed with the installation but in this case you should be aware
+of what you are doing.
+SALOME binaries (including other products) are compiled with the
+predefined prerequisites
+and most likely can not be run successfully if these products are not
+found.
+This can be helpful only if you plan to build all products from
+sources.
+
|
- |
-
-
- |
-
-
- of installation procedure |
-
-
- |
-
|---|---|---|---|
| gcc 3.2 | - -ver=`/usr/bin/gcc --version | grep 'gcc (GCC) .*' | cut -b 11-13` | - -
- |
-
-ver should be equal 3.2
- It is recommended to use native gcc on Linux RedHat 8.0 |
-
| tcl 8.3 | - -existence of TCLHOME
- existence of tclsh8.3 - existence of wish8.3 - existence of libtcl8.3.so - existence of libtk8.3.so - existence of libtclx8.3.so - existence of libtkx8.3.so |
-
-set TCLHOME if you have preinstalled version of tcl.
- set LD_LIBRARY_PATH on a directory where libs can be found. |
-
-It is recommended to use native tcl on Linux RedHat 8.0 | -
| Cascade 4.0 | - -existence of CASROOT environment variable | - -set CASROOT if you have preinstalled version of CASCADE | - -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 | -
| Python 2.2.1 | - -existence of PYTHONHOME
- isPython=`which python` - ver=`python -V` |
-
-set PYTHONHOME to root Python folder
- set PATH on a directory where python can be found |
-
-Python should exist and ver should be equal to 2.2.1
- It is recommended to use native Python on Linux RedHat 8.0 |
-
| Mesa 3.4.2 | - -existence of libGL.so.1.2.030402 | - -set LD_LIBRARY_PATH on a directory where libGL.so.1.2.030402 can be -found | - -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. | -
| Swig 1.3.17 | - -isSwig=`which swig`
- ver=`swig -version` - ver=`echo $ver | awk '{print $3}'` |
-
-set PATH on a directory where swig can be found | - -Swig should exist and ver should be equal to 1.3.17 | -
| Qt 3.0.5 | - -existence of QTDIR
- existence of libqt-mt.so.3.0.5 |
-
-set QTDIR if you have preinstalled version of qt | - -We try to find libqt-mt.so.3.0.5 in ${QTDIR}/lib folder.
- You should set MESA_HOME only if you have preinstalled version of Mesa -3.4.2. - It is recommended to use native Qt on Linux RedHat 8.0 |
-
| Qwt 0.4.1 | - -existence of QWTHOME
- existence of libqwt.so.0.4.1 |
-
-set QWTHOME if you have preinstalled version of qwt | - -We try to find libqwt.so.0.4.1 in the ${QWTHOME}/lib folder. | -
| Hdf 5-1.4.4 | - -existence of HDF5HOME
- existence of libhdf5.so.0.0.0 - existence of libhdf5.settings |
-
-set HDF5HOME if you have preinstalled version of hdf | - -We try to find libhdf5.so.0.0.0 and libhdf5.settings in ${HDF5HOME}/lib
-folder.
- File libhdf5.settings should contain the following entry: - HDF5 Version: 1.4.4 |
-
| Med 2.1.6 | - -existence of MED2HOME
- existence of libmed.so.0.0.0 |
-
-set MED2HOME if you have preinstalled version of med | - -Unfortunately we can't check version number.
- We try to find libmed.so.0.0.0 in ${MED2HOME}/lib folder. - If you have problem with preinstalled version of med reinstall it. |
-
| Vtk 4.2 | - -existence of VTKHOME
- existence of libvtkCommon.so |
-
-set VTKHOME if you have preinstalled version of vtk | - -Unfortunately we can't check the version number.
- We try to find libvtkCommon.so in ${VTKHOME}/lib/vtk folder. - If you have problem with preinstalled version of vtk reinstall it. |
-
| OmniORB 3.0.5,
- OmniORBpy 1.5, - OmniNotify 1.2 |
-
-existence of OMNIORBDIR
- existence of libomniORB3.so.0.5 - existence of _omnipymodule.so.0.5 - existence of libCOSNotify3.so.0.5 - existence of notifd - existence of THIS_IS_omniORB_3_0_5 - existence of THIS_IS_omniNotify_1_2 - existence of THIS_IS_OMNIORBPY_1_5 |
-
-set OMNIORBDIR if you have preinstalled version of omni | - -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.
- We try to find notifd in ${OMNIORBDIR}/bin/i586_linux_2.0_glibc2.1 -folder. - Additional checking - omni add special files THIS_IS_... - We try to find THIS_IS_omniORB_3_0_5 in ${OMNIORBDIR} folder. - We try to find THIS_IS_omniNotify_1_2 in ${OMNIORBDIR}/src/services/omniNotify. - We try to find THIS_IS_OMNIORBPY_1_5 in ${OMNIORBDIR}/src/lib/omniORBpy -folder. |
-
| Numeric 22.0 | - -existence of Numeric folder
- existence of _numpy.so |
-
-set PYTHONHOME if you have preinstalled version of python | - -Unfortunately we can't check the version number.
- We try to find Numeric folder in ${PYTHONHOME}/lib/python2.2/site-packages/Numeric -folder. - If you have problem with preinstalled version of numeric 22.0 reinstall -it. |
-
| Sip 3.3.2 | - -existence of SIPDIR
- existence of sip - existence of libsip.so.9.1.0 |
-
-set SIPDIR to directory where you have sip preinstalled | - -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.
- It is recommended to use native Sip on Linux RedHat 8.0 |
-
| PyQt 3.3.2 | - -existence of PYQTDIR
- existence of libqtxmlcmodule.so.1.0.0 |
-
-set PYQTDIR to directory where you have sip preinstalled | - -Unfortunately we can't check the version number.
- We try to find libqtxmlcmodule.so.1.0.0 in $PYQTDIR folder if you set -PYQTDIR, otherwise searching is done using $LD_LIBRARY_PATH . - If you have problem with preinstalled version of PyQt 3.3.2 reinstall -it. - It is recommended to use native PyQt on Linux RedHat 8.0 |
-
| HappyDoc 2.1 | - -existence of happydoc
- ver=`happydoc | grep "HappyDoc version 2.1"` |
-
-set PYTHONHOME if you have preinstalled version of python | - -We try to find happydoc in $PYTHONHOME/bin folder.
- ver should not be empty. - This product is not obligatory. It was added only for your comfort. |
-
| Doxygen 1.3-rc2 | - -existence of doxygen
- existence of doxysearch - existence of doxytag - existence of doxywizard |
-
-set QTDIR if you have preinstalled version of qt
- set PATH on a directory where doxygen, doxysearch, doxytag and doxywizard -can be found |
-
-Unfortunately we can't check the version number.
- It's necessary to have compiled Qt in order to build doxywizard. - If you have problem with preinstalled version of doxygen 1.3-rc2 reinstall -it. - This product is not obligatory. It was added only for your comfort. |
-
| Graphviz 1.9 | - -existence of dot | - -add GraphViz's bin directory to the PATH environment variable | - -Unfortunately we can't check the version number.
- We try to find dot program in the $PATH |
-
| SALOME PRO binaries | - -existence of SALOME_ROOT_DIR
- existence of VERSION file - ver=`cat $SALOME_ROOT_DIR/bin/VERSION | awk -F: '{print $2}' | tr -d -'[:space:]'` |
-
-set SALOME_ROOT_DIR if you have preinstalled binaries of SALOME PRO -version 1.2d | - -SALOME PRO binaries should exist and ver should be equal to 1.2d | -
| SALOME PRO sources | - -existence of SALOMEPRO_SRC
- existence of VERSION file - ver=`cat $SALOMEPRO_SRC/bin/VERSION | awk -F: '{print $2}' | tr -d -'[:space:]'` |
-
-set SALOMEPRO_SRC if you have preinstalled sources of SALOME PRO version -1.2d | - -SALOME PRO sources should exist and ver should be equal to 1.2d | -
Note: For native products installation procedure sets proper environment
-variables itself, and you do not need to set such variables like, e.g.
-TCLHOME
-or PYTHONHOME.
-
If you have native products installed to different from default directories
-(not /usr/bin, /usr/lib...), it is recommended to follow
-above description. Or you should set properly $PATH and $LD_LIBRARY_PATH
-variables before starting Installation
-Wizard. Otherwise installation script will fail to find preinstalled products.
-
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: env_<product_name>.sh. -This file includes all necessary product settings. For example for Vtk -the file is env_Vtk.sh. 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: salome.sh and -salome.csh -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. -
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 salome.sh/salome.csh files
-will be skipped.
-
For native products (gcc, tcl, python, qt, sip, pyqt for
-RedHat-8.0) instal script tries to find them using $PATH
-/ $LD_LIBRARY_PATH variables and then in the system default directories
-(/usr/bin, /usr/lib etc., depending on the product).
-
In any case you may edit salome.* files after installation procedure -finishes, as you want. -
+
After installing of each product shell the script creates special +environment file for the product in its installation folder. The name +of +the file is generated +from +the name of product by the following scheme: env_<product_name>.sh +(for example env_Vtk.sh for the Vtk). +This file includes all necessary environment settings. At the final +step of the installation the script picks up all the +settings files and generate from them two common environment files: salome.sh +and salome.csh +for bash and csh shells 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 source one of +these +environment files.
+This concerns also those products which are not being installed.
+For example, you install some SALOME binaries to the directory where
+you have previously installed other products. Installation
+procedure tries to collect environment files from the target
+directory if it finds necessary products installed there. If some
+product is not
+found in the target directory the corresponding
+section of salome.sh/salome.csh files will be skipped.
+For native products (like gcc, tcl, etc...)
+installation procedure tries to find them first using PATH
+/ LD_LIBRARY_PATH variables and then in the system default
+directories (/usr/bin, /usr/lib etc., depending on the product).
+
In any case you may edit salome.* files after installation
+procedure finishes, if you want.
+
+Note: as it was mentioned above there
+are another environment files which
+are generated by the installation procedure: env_products.csh + env_products.sh and env_build.csh + env_build.sh. These files can be
+found in the target installation root directory.
+
<document>
-
[<config
-[version=<install_wizard_version>]
-
-[caption=<install_wizard_caption>]
-
-[copyright=<install_wizard_copyright>]
-
-[license=<install_wizard_license_info>]
-
-[os=<target_paltform>]/>]
-
[<path
-[targetdir=<target_directory>]
-
-[tempdir=<temp_directory>]/>]
-
[<product
-name=<product_name>
-
-version=<product_version>
-
-install=<installation_mode>
-
-supported=<supported_installation_modes>
-
-disable=<disable_flag>
-
-dependancies=<list_of_prerequisites>
-
-installdiskspace=<install_disk_space>
-
-temporarydiskspace=<tmp_disk_space>
-
-script=<installation_script_name>/>]
-
[<product
-... />]
-
...
-
</document>
-
+
+ <document>
+
+ [ <config
+[ version=<install_wizard_version> ]
+
+ [
+caption=<install_wizard_caption> ]
+
+ [
+copyright=<install_wizard_copyright> ]
+
+ [
+license=<install_wizard_license_info> ]
+
+ [ os=<target_platform>
+]
+ />
+ ]
+ [ <path
+[ targetdir=<target_directory> ]
+
+
+[ tempdir=<temp_directory> ]
+ />
+ ]
+ [ <button
+ label=<button_label>
+
+
+[ tooltip=<button_tooltip> ]
+
+
+ script=<button_script>
+
+
+[ disable=<disable_flag> ]
+ />
+ ]
+ [ <button ...
+ />
+ ]
+ [ <product
+name=<product_name>
+
+
+version=<product_version>
+ [
+context=<product_context>
+]
+ [
+description=<product_description> ]
+
+
+install=<installation_mode>
+
+
+supported=<supported_installation_modes>
+
+ [ disable=<disable_flag>
+ ]
+ [
+pickupenv=<pickup_env_flag> ]
+
+
+dependancies=<list_of_prerequisites>
+
+ installdiskspace=<install_disk_space>
+
+
+ temporarydiskspace=<tmp_disk_space>
+
+ script=<installation_script_name>
+ />
+
+ ]
+ [ <product ...
+ />
+
+ ]
+ ...
+
+</document>
+
where
-
<product_script_name> - installation
-script name (described in configuration xml file);
-
<function_name> - the name of function,
-corresponding to the selected installation mode: try_native, install_source,
-install_binary or try_preinstalled;
-
<temp_folder> - temporary files directory;
-
<products_directory> - directory where
-the sources/binaries package can be found. You should provide sources package
-in the <Install_Wizard_root_directory>/Products/SOURCES directory
-and binaries package in the <InstallWizard_root_directory>/Products/BINARIES/<os_version>,
-where <os_version> is target platform description, which appears in
-the corresponding section of the configuration xml
-file.
-
<target_directory> - root target directory
-where product should be installed to;
-
<dependancies> - single-quoted list
-of prerequisite products, separated by space;
-
<product_name> - product name itself.
-
Example:
-
med-2.1.6.sh install_binary /tmp/work ./Products/BINARIES/RedHat8.0
-/usr/salome 'gcc Hdf' med
-
Copy created script into the <Install_Wizard_root_directory>/config_files -sub-directory. File common.sh contains some service functions which -can be used in your installation script. -
-
where
+
<product_script_name> -
+installation
+script name (described in configuration xml file);
+<function_name> - the name of
+function, corresponding to the selected installation mode: try_native,
+install_source, install_binary or try_preinstalled;
+<temp_folder> - temporary files
+directory;
+<products_directory> - directory
+where the sources/binaries package can be found. You should provide
+sources package in the <Install_Wizard_root_directory>/Products/SOURCES
+directory and binaries package in the <InstallWizard_root_directory>/Products/BINARIES/<os_version>,
+where <os_version> is target platform description, which appears
+in the corresponding section of the configuration
+xml
+file.
+<target_directory> - root target
+directory where product should be installed to;
+<dependancies> - single-quoted list
+of prerequisite products, separated by space;
+<product_name> - product name
+itself.
Example:
+med-2.2.3.sh install_binary /tmp/work
+./Products/BINARIES/Mandrake10.1 /usr/salome 'gcc Hdf' med
Copy created script into the <Install_Wizard_root_directory>/config_files +sub-directory where all installation scripts are stored. Installation +Wizard +will automatically search and call your script during the installation +procedure. +
+
+
where
+
<product_script_name> -
+the script name itself (retrieved from the XML configuration xml
+file);
+<function_name>
+- the name of function;
+<target_directory> - root target
+directory where product are
+installed to;
+<temp_folder>
+ - temporary files directory;
+
+Note: The standard Installation Wizard buttons "Launch
+SALOME" and "Release Notes" are implemented with this
+feature. Refer to the scripts start_salome.sh and
+release_notes.sh for sample implementation.
+
+Note: Any button (even standard) can be ignored by the
+Installation Wizard if the attribute <disable> in the XML
+configuration file is set to the "true" value.
+
-