X-Git-Url: http://git.salome-platform.org/gitweb/?a=blobdiff_plain;f=doc%2Freadme.html;h=137f24800cebd8501c2b72842f35f4fb857c42f1;hb=57a88d00ae1e926c9854ea7377647e7fd039a103;hp=6034edd9a00d20bb5966218e79bc266fa264cb85;hpb=6c3acc98eefa7c09d071fe25e53458bda0d3b5a9;p=tools%2Finstall.git diff --git a/doc/readme.html b/doc/readme.html index 6034edd..137f248 100755 --- a/doc/readme.html +++ b/doc/readme.html @@ -6,8 +6,8 @@ - + content="Alexander KOVALEV, Open CASCADE SAS (alexander.kovalev@opencascade.com)"> +
[ python ] runInstall [options]
+
[ 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:
+Wizard in the GUI mode.
+The default installation settings can be overridden 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
--s / --single-directory
+-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
+
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.
+The usage of configuration XML files provides a flexible way to modify
+the list of products to be installed by the Installation Wizard without
+changing the source code of the application. Just create your own XML
+configuration file and implement installation scripts for the prerequisite products you
need and then use this XML file with the Installation Wizard. This can
be done, for example, for some 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 +
The GUI of the Installation Wizard has been +developed with Qt +3.3.8 toolkit by +Trolltech . 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.
+buttons in the lower part of the wizard window. "Cancel" button +closes the wizard window and quits the installation procedure after user +confirmation. "Help" button opens a window with the help information.The first "Introduction" -page is shown at the Figure 1. Skip this page -by pressing "Next" -button: +page is shown in 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.
+
In the second page you are proposed to select the type of the
+SALOME installation.
+
+At this step three possible types of installation are available:
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 case you select "Install sources and make compilation" +installation type, then you can also check "Remove sources and +temporary files after compilation" option.
-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: "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 2: "Installation settings" +
Figure 3: "Installation platform" page
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.
+
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.
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. 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.
+
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
-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.
+
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
-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.
+
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.
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 8: Installation without GUI mode
-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 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 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.
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.
-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
+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 automaticaly when the installation finishes.
+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
-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, 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 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
+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 stopped installation
-process; it will be re-started from the very beginning.
+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
-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 8: "Finish installation" page
+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
-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
+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 Release Notes file by clicking on the corresponding
+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
+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
+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 installation scripts collects the environment, see here. These files are: salome.csh + salome.sh
-in the KERNEL module sources
+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
+module binaries
+root directories and env_products.csh
+ env_products.sh and env_build.csh
-+ env_build.sh in the
++ 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.
-
After installing of each product shell the script creates special +
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 product by the following scheme: env_<product_name>.sh +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 the -settings files and generate from them two common environment files: salome.sh +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. 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 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. 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).
+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 may edit salome.* files after installation
-procedure finishes, if you want.
+
In any case you are able to edit salome.*
+files after the installation procedure finished.
-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
+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=<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>
+
+
+<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> ]
+
+ />
+
+
+[ <buttons>
+
+
+[ <button
+
+label=<button_label>
+
-
+
[ tooltip=<button_tooltip> ]
-
- script=<button_script>
-
-[ disable=<disable_flag> ]
- />
+
+script=<button_script>
+
+
+
+[ disable=<disable_flag> ]
+ />
+
+ ]
+
+[
+<button
+...
+ />
+
+
+]
+
+...
+
+ </buttons>
+
]
- [ <button ...
- />
- ]
- [ <product
+ [ <products>
+
+
+[
+<product
name=<product_name>
-
-
-version=<product_version>
- [
-context=<product_context>
-]
- [
+
+
+
+type=<product_type>
+
+ [
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>
+
+
+<installation
+os=<installation_platform>
+
+
+
+
+version=<product_version>
+
+
+
+ [
+disable=<disable_flag>
+ ]
+
+
+
+ [
+woguimode=<without_gui_mode_flag> ]
-
- temporarydiskspace=<tmp_disk_space>
-
- script=<installation_script_name>
- />
+
+
+installdiskspace=<install_disk_space>
+
+
+ [
+pickupenv=<pickup_env_flag>
+ ]
+
+
+
+
+
+script=<installation_script_name>
+
+/>
+
+...
+
+ />
+
+ ]
+ [ <product ...
+ />
+ ]
+
+...
+ </products>
+
+ ]
+ [ <dependencies>
+
+
+[
+<product
+name=<product_name> >
+
+[
+<dep> <prerequisite_name>
+ </dep>
+]
+
+...
+ </product>
- ]
- [ <product ...
- />
+
+]
+
+...
+ </dependencies>
- ]
- ...
+ ]
-</document>
where
<product_script_name> -
-installation
-script name (described in configuration xml file); <product_script_name>
+-
+the name of the installation script (described in the 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
+
+<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 target platform description, which appears
+where <os_version> is the 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.
+
+<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.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 +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> -
+ <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
+- the name of the function;
+<target_directory>
+- the root target
+directory where the product is
installed to;
<temp_folder>
- - temporary files directory;
+ - the directory for the temporary files.
-Note: The standard Installation Wizard buttons "Launch
+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.
+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
+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.