X-Git-Url: http://git.salome-platform.org/gitweb/?a=blobdiff_plain;f=doc%2Freadme.html;h=137f24800cebd8501c2b72842f35f4fb857c42f1;hb=57a88d00ae1e926c9854ea7377647e7fd039a103;hp=9141215b88ef4ba481aad44af3e54aeaf34bcc16;hpb=17f39f0497193306fa2f9f6937496efacb269b5e;p=tools%2Finstall.git diff --git a/doc/readme.html b/doc/readme.html index 9141215..137f248 100755 --- a/doc/readme.html +++ b/doc/readme.html @@ -1,828 +1,1239 @@
- - - -
+
+
+
updated for the version 2.2.6
-
--
+
++
|
- |
-
- |
-
- - of installation procedure |
-
- |
-
---|---|---|---|
gcc 3.2 | -ver=`gcc -dumpversion` | -
- |
- ver should be 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/tk on Linux RedHat 8.0 | -
boost 1.30.2 - |
- ver=`egrep 'BOOST_VERSION [0-9]+' ${BOOSTDIR}/boost/version.hpp
-| sed 's/.*BOOST_VERSION \([0-9]\+\)/\1/g'` - |
- set BOOSTDIR if you have preinstalled version of
-boost - |
- It is impossible to use native BOOST and to install
-BOOST from binaries. - |
-
Open CASCADE 5.2 - |
- existence of CASROOT environment variable ver_major=`grep "!define OCC_VERSION_MAJOR" ${CASROOT}/inc/Standard_Version.hxx | awk '{print $3}'` -ver_minor=`grep "!define OCC_VERSION_MINOR" ${CASROOT}/inc/Standard_Version.hxx | awk '{print $3}'` -ver="$ver_major.$ver_minor" - |
- set CASROOT if you have preinstalled version of Open CASCADE | -CASCADE's Standard_Version.hxx file provides version information. | -
Patch for Open CASCADE 5.2 - |
- - | - | Open CASCADE 5.2 provided with the Installation Wizard already includes the patch, -necessary for SALOME 2.2.x. In addition the Installation Wizard provides the sources of a Open CASCADE patch -which can be applied to original Open CASCADE 5.2 sources before its compilation. | -
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 - ver=`grep "QT_VERSION_STR" ${QTDIR}/include/qglobal.h | sed -e 's%^#define QT_VERSION_STR\([[:space:]]*\)%%g' -e 's%\"%%g'` |
- set QTDIR if you have preinstalled version of qt | -Qt's qglobal.h file provides version information: ver should be 3.0.5. - 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 ver=`grep "HDF5 Version:" ${HDF5HOME}/lib/libhdf5.settings | awk '{print $3}'` |
- 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.2.2 | -existence of MED2HOME - existence of libmed.so.1.0.1 |
- set MED2HOME if you have preinstalled version of med | -Unfortunately we can't check version number. - We try to find libmed.so.1.0.1 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. |
-
Netgen 4.3 - |
- existence of NETGENROOT - |
- set NETGENROOT if you have preinstalled version of
-Netgen. - |
- Unfortunarely we can't find anything about netgen
-version. -We just check if NETGENROOT environment varible is set. - |
-
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. +The Installation Wizard can be launched in two modes: GUI and batch. +The root directory of the Installation Wizard +contains Python script runInstall. +To run the Installation Wizard just type ./runInstall in the +terminal +window: + [ python ] ./runInstall [options] Without options this script will launch the SALOME Installation
+Wizard in the GUI mode. -g / --gui Runs the Installation Wizard in the
+GUI
+mode (this is the default mode).
++ -b / --batch Runs the Installation Wizard in
+the terminal mode.
++ -f FILE / --file=FILE
+This is the XML configuration file used by the Installation Wizard.
+If this option is not used, the installation script tries to define
+theLinux version and to use the corresponding XML file
+if it is present.
+For example, for Linux Mandriva
+2010 the config_Mandriva_2010.0.xml
+file
+will be used by default.
+
+ -d DIR / --target=DIR This is the target installation
+directory for SALOME platform. If used, this option overrides
+the default target directory, given in the
+configuration XML file (usually
+${HOME}/salome_<version>).
++ -t DIR / --tmp=DIR +This is the directory, for
+temporary files. If given, this option overrides the default
+temporary directory, given in the configuration xml file
+(usually /tmp
+).
++ -a / --all-from-sources +
+Force all the products to be installed from sources (including all
+SALOME modules). If this option is used, all the default installation
+modes for all the products are ignored.
++This option is helpful when the user wants to install SALOME on the +platform which is not officially supported. In this case, the user can +try to run the SALOME Installation Wizard with the -a option in order to build all the +products from sources. +Note, that this is long-time operation which can take more than +24 hours depending on the computer. + -s / --single-directory +Install all SALOME binaries packages
+to one directory.
++This option is ignored when --all-from-sources (-a) option is used. + -h / --help Prints help information on
+the usage of the Installation Wizard.
+
++
+-v / --version Prints version information
+(Note: this
+is the version number of the Installation Wizard, not of SALOME platform).
++ + +The installation procedure supports different Linux
+platforms and installs various 3d-party installation prerequisite products, which
+are required by SALOME platform. Among supported Linux platforms there are Mandriva 2008
+(32bit and 64bit), Mandriva 2010 (32bit and 64bit), Debian 4.0 Etch (32bit and 64bit),
+Debian 5.0 Lenny 64bit, Debian 6.0 Squeeze 64bit and other ones. GUI
+mode
+ |
-
Numeric 22.0 | -ver=`python -c 'import Numeric; print Numeric.__version__' 2>/dev/null` | -set PYTHONHOME if you have preinstalled version of Numeric package | -If you have problem with preinstalled version of numeric 22.0 reinstall it. | -
Sip 3.3.2 | -existence of SIPDIR sip_ver=`${SIPDIR}/sip -V | awk '{print $1}'` |
- set SIPDIR to directory where you have sip preinstalled | -Searching for the sip binary is performed in the folder pointed by the $SIPDIR variable if it is set
-and then by using $PATH variable. - 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 PATH variable to the directory where you have HappyDoc installed. | -We try to find happydoc in $PATH. - 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 ver=`doxygen --version` |
- set QTDIR if you have preinstalled version of qt - set PATH on a directory where doxygen, doxysearch, doxytag and doxywizard - can be found |
- doxygen, doxysearch, doxytag, doxywizard binaries should exist; ver should be 1.3-rc2. -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 binary. ver=`dot -V 2>&1 | awk '{print $3}'` |
- add GraphViz's bin directory to the PATH environment variable | -We try to find dot program in the $PATH. | -
MODULE binaries - (MODULE=KERNEL,GEOM, ...) - |
- existence of MODULE_ROOT_DIR - existence of VERSION file - ver=`cat $MODULE_ROOT_DIR/bin/salome/VERSION | awk -F: '{print $2}' | tr --d '[:space:]'` |
- set MODULE_ROOT_DIR if you have preinstalled binaries of MODULE - version 2.2.4 | -MODULE binaries should exist and ver should be equal to 2.2.4 | -
MODULE sources - (MODULE=KERNEL,GEOM, ...) - |
- existence of MODULE_SRC_DIR - existence of VERSION file - ver=`cat $MODULE_SRC/bin/VERSION | awk -F: '{print $2}' | tr -d '[:space:]'` |
- set MODULE_SRC_DIR if you have preinstalled sources of MODULE -version 2.2.4 | -MODULE sources should exist and ver should be equal to 2.2.4 | -
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.
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. Release number can be larger. It is done for making a possibility -to use native products for newer versions of Red Hat (for example, Linux Red Hat 9 includes native -gcc 3.2.2 installation). -If native product has version number larger than that required by installation procedure, -you will be prompted by the warning message like this: "You have newer version of gcc installed -on your computer than that is required (3.2). Continue?". You can press "Yes" button -to procede 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 prerequisites from the list -and most likely can not be run successfully if this products are not found. -This can be only helpful if you intend to build all products from sources.
- -In case you select "Install sources and make compilation" +installation type, then you can also check "Remove sources and +temporary files after compilation" option. +
+Figure 2: "Type of installation" page +
+After the installation type has been selected you click "Next" +button and the Installation Wizard tries to determine the Linux +platform to load the corresponding configuration file. If the operating +system is not defined or the current SALOME package does not support +this system, the warning message will appear ("Install binaries" +and "Install sources" installation types only): +
+Figure 3: "Installation platform" page +
+If "Install sources and make compilation"
+installation type has been selected, the warning message will be
+slightly different: "Your Linux platform is not supported by
+this SALOME package and compilation is not tested on this one".
+There is a list of all platforms supported by SALOME, but only those
+supported by the current package are available for selection. in this
+page you need to to select the reference platform, if you wish to
+proceed with the present installation procedure.
+Note: this page is not displayed if the installation
+platform has been defined automatically.
+
In the next page you are proposed to enter the target
+installation directory for SALOME platform. You can also press "Browse..."
+button and choose the destination folder using the standard browse
+directory dialog box.
+If the necessary directory does not exist you are
+prompted to confirm the directory creation. If you type a wrong
+directory
+path, or if you do not have the permissions to write to the chosen
+directory, the corresponding message box is shown.
+
Note: you are strongly recommended to avoid using +directory names containing spaces. Otherwise you can +experience some troubles with the +installation. +
+Figure 4: "Installation directory" page +
+You can select the products to be installed in the "Choice of
+the products to be installed" page.
+In the default mode it gives you the possibility to view and select
+SALOME modules only. There is a hidden list of 3d-party prerequisite
+products. To show it, just click "Show prerequisites..."
+button.
+
Figure 5: Choice of the SALOME modules +
+In the full mode you also have the possibility to select
+prerequisites.
+The checkbox before each product indicates if this one will be
+installed or not (checked or unchecked). The second column shows the
+disk space occupied by the corresponding module. This value depends on
+the selected type of installation.
+To hide the prerequisites list - click "Hide prerequisites"
+button.
Figure 6: Choice of the prerequisites +
++Some products may require some other prerequisite products to be +installed. So the installation procedure has a special feature to +automatically mark these products in the list view. For example, to +install PyQt it is necessary to have gcc, Python, Qt and Sip installed, +and these products will be also turned on when you check on PyQt. GEOM +module requires KERNEL, GUI modules and such prerequisites as: +OpenCascade, Python, Swig, Qt, etc. +
+The dependencies between SALOME modules are managed in the +following way: +
+Dependency between modules and prerequisites is realized in +the following way: +
+Figure 7: Dependencies between modules and +prerequisites +
+The "Installation with GUI" checkbox allows
+managing the installation of the graphical interface. Only modules for that
+'woguimode' attribute is set to "true" value in the XML file
+(see here for more information about
+customizing this installation mode) support without GUI mode and
+will be checked and installed with their necessary prerequisites in
+case of installation without GUI. And other modules are unchecked with no
+possibility to check them in this mode (see figure below).
+By default 'Installation with GUI' checkbox is switched on.
+
Figure 8: Installation without GUI mode +
+The box at the right side of the page displays the information +about the currently selected product: name, version and short description, +required disk space, disk space required for the temporary files and +the list of prerequisites (this information is provided in the XML +file). +
+The "Disk space required:" field displays
+how much
+disk space on the hard drive is required for installation of the
+selected
+products.
+Note: please, take into account that the displayed
+amount of
+the required disk space is approximate and may differ when you actually
+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 the required disk space on the hard drive for
+extracting and compiling the selected products. You can change the
+temporary directory (this information is provided in the XML file) to
+the folder you want.
+Note:
+actually, the temporary files
+are not stored directly in the directory selected by the user. The
+Installation Wizard creates in this directory an additional folder
+named
+like INSTALLWORKXXXXX
+where XXXXX is a unique number. This allows launching several
+Installation Wizards simultaneously. This temporary directory is
+removed automatically when the installation finishes.
+
The installation procedure also checks the available disk +space. If +there is not enough disk space on your hard drive you will see the +corresponding error message box. +
+Also in the current version of Installation Wizard is possible
+to install all binaries of the selected SALOME modules into a single
+directory. It is "SALOME" directory.
+For this purpose there is a checkbox "Install modules to a
+single directory" checkbox exists (see Fig.8).
+This feature helps to get shorter PYTHONPATH and LD_LIBRARY_PATH
+environment variables.
+Note: the installation into a single directory is
+available with the binaries installation type only.
+
To proceed further, click "Next" button. +At this moment +the program will make some tests to check the installation settings: if +there is enough disk space on the hard drive, check for the +dependencies 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 9: "Check your choice" page +
+This page summarizes the installation options you've selected
+in the
+previous pages. You can review again your choices and change them if
+necessary returning to the previous pages.
+When you are sure that everything is OK, press "Next"
+button to
+follow to the progress page.
+
Figure 10: "Installation progress" page: +not started yet +
+Note:
+in the current
+implementation it is not possible to resume the stopped installation
+process; the installation will restart from the very beginning.
+
Figure 11: "Installation progress" page: +installation in +progress +
+The "Installation Status" frame window +shows you the +progress of installation. "Waiting" +status +means that the installation of this product has not started +yet. The product currently being installed is marked as "Processing" and is displayed in +the status bar under "Installation Status" view. All installed products +have "Completed" +status. +
+You can abort the 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 the temporary files can take some time, so the
+installation wizard will wait for 3 seconds before closing.
+
At the end of the installation "Installation completed" +message will appear in the status bar. You can return to the previous +pages to start a new installation or click "Next" +button to go to the readme page:
+Figure 12: "Finish installation" page +
+In this page you can read important information about the
+Installation Wizard itself and some tips: how to run and test SALOME or
+how to build SALOME from the sources. This is also described 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 the 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 the procedure of launching SALOME. These
+shell scripts set
+all necessary environment variables for all products you have
+installed.
+To learn how the installation scripts collect 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.
+
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.
- -<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>]/>]
- [<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 ... />]
- ...
+Please, read carefully the following information. This section
+describes how the installation procedure generates the environment
+scripts for the SALOME platform being installed.
+
After the installation of each product the shell script +creates a special +environment file for the product in its installation folder. The name +of the file is generated from the name of the 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 settings files and +generates from them two common environment files: salome.sh +and salome.csh +for bash +and csh +shells correspondingly. This +approach helps to save time when reinstalling products and you may can +avoid setting all environment variables +manually to build/launch SALOME. What you need is to source one of +these environment files.
+This also concerns the products which are not being installed.
+For example, you install some SALOME binaries to the directory where
+you have previously installed other products. The
+installation
+procedure tries to collect the environment files from the target
+directory if it finds necessary products installed there. If a
+product is not found in the target directory the corresponding
+section of salome.sh/salome.csh files will be
+commented.
+For the native products (like gcc, tcl, etc...)
+the 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 are able to edit salome.*
+files after the installation procedure finished.
+
+Note: as it has been mentioned above
+there
+are other environment files 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=<application_version>
+ ]
+
+
+ [
+caption=<application_caption>
+ ]
+
+
+ [
+copyright=<application_copyright> ]
+
+
+
+ [
+license=<application_license_info> ]
+
+
+
+platforms=<target_platform>
+
+
+ [
+targetdir=<target_directory>
+ ]
+
+
+
+
+[
+tempdir=<temp_directory>
+ ]
+
+ [
+optionallibs=<optional_libraries> ]
-</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.
-
<product_script_name>
+-
+the name of the installation script (described in the configuration XML
+file);
+<function_name>
+- the name of
+the function, corresponding to the selected installation type and
+currently installed product;
+
+<temp_folder> - the directory for the
+temporary files;
+<products_directory>
+- the 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 the target platform description,
+which appears
+in the corresponding section of the configuration
+xml
+file.
+
+<target_directory> - the root target
+directory where the product should be installed to;
+
+<all_products> - single-quoted list
+of all products, separated by space;
+
+<product_name> - product name
+itself;
+
+<install_products> - single-quoted list
+of all products to be installed, separated by space;
+
+<sources_directory> - the directory
+where the sources package can be found (it is usable if the
+<products_directory> parameter gives the binaries
+directory path);
+
+<remove_sources_flag> - bool parameter, that
+is equal to 'TRUE' if 'Remove sources and temporary files after
+compilation' option has been selected by the user (see Fig.2 in the GUI part);
+
+<binaries_directory> - the directory
+where the binaries package can be found (it is usable if the
+<products_directory> parameter gives the sources
+directory path);
+
+<single_directory_flag> - bool parameter,
+that is equal to 'TRUE' if 'Install modules to a single directory'
+option is selected by the user (see Fig.5
+above).
+
Example:
- med-2.2.2.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 where all installation scripts are stored. Installation Wizard -will automatically search and call your script during the installation procedure. -
- +med.sh install_binary +/tmp/INSTALLWORK21797 +./Products/BINARIES/Mandriva2010.0 +'gcc tcltk tcltk_src Python Python_src Qt Qt_src ... DOCUMENTATION +DOCUMENTATION_src' +Med +'gcc Hdf Med' +./Products/SOURCES +FALSE +./Products/BINARIES/Mandriva2010.0 + +Copy the created script +into +the <Install_Wizard_root_directory>/config_files +sub-directory where all installation scripts are stored. The 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 the function;
+<target_directory>
+- the root target
+directory where the product is
+installed to;
+<temp_folder>
+ - the directory for the temporary files.
+
+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 the 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.
+