X-Git-Url: http://git.salome-platform.org/gitweb/?a=blobdiff_plain;ds=sidebyside;f=doc%2Freadme.html;h=ae2c85aa4721f16aa54f486ae8a517467fe56697;hb=a5c3695f9bee99a732f34867b36cba824c17257c;hp=9e16af3305174bcf1452d88b65791c3efbbc2569;hpb=eb9de328d5830612894de3a1a8524f176a625aa5;p=tools%2Finstall.git diff --git a/doc/readme.html b/doc/readme.html index 9e16af3..ae2c85a 100755 --- a/doc/readme.html +++ b/doc/readme.html @@ -1,827 +1,833 @@ - +
- - - -
--- |
-
-
--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.
+
+
[ 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 uses 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, given in the configuration
+xml file.
+ -tmp <tmp-dir>
+ The directory, which is used to contain
+ temporary files. If used, overloads temporary directory, given in the
+configuration xml file.
+-h
+ Prints help information.
+
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.
+(currently it provides only configuration scripts for 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. -
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.
-
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.
+ 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.
+ +In the advanced mode you have the possibility to select products to be
+installed (see Fig.1 ). Each product can have several
+options of installation: you have a possibility to use native products, install
+already precompiled binaries, build product from the sources or not install it
+at all. Possible options and default choice are provided by the configuration
+file. You can mark the products, you want to install, by clicking the corresponding
+radiobuttons in the list view in the left part of the page. Note that some
+products can be installed only together with other products (or these prerequisite
+products should be already installed on your computer). The installation procedure
+has a special feature to automatically mark these products in the list view.
+For example, in order to install 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.
The box at the right side of the page displays the information about currently +highlighted product: name, version, short description (if provided), required +disk space, temporary files disk space, list of prerequisites and user choice. +
+ +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 + 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 to the folder you want to use or click on the corresponding "Browse..." -button. + 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. + 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 + 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. +Therefore you are strongly recommended not to use directory names containing +spaces.
+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 +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: -
Figure 2: "Check your choice" 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"
-button. It launches the shell installation script and you will be able
-to see the output of the script in the topmost dialog's frame. In case
-of any installation problems (for example, you have accidentally removed
-the temporary directory) the script will ask you:
-"Would you like to
-continue : (Y,N) ?". You can answer this question by typing [Y] or
-[N] in the middle text edit control frame.
-
Note: press [Enter] when you finish typing data.
-
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.
+ 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" button.
+It launches the shell installation script and you will be able to see the
+output of the script in the topmost dialog's frame. In case of any installation
+problems (for example, you have accidentally removed the temporary directory)
+the script will ask you: "Would you like to continue : (Y,N) ?". You
+can answer this question by typing [Y] or [N] in the middle text edit control
+frame.
+ Note: press [Enter] when you finish typing data.
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. +"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: -
Figure 4: "Finish installation" 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.
+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 + 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. -
-
- |
-
-
- |
-
-
- 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 +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 + in the target directory. + + + Notes on check +products version procedure+ Unfortunately under Linux platform there is no exact algorithm to identify + the product's version. The table below contains the information relating +to checking preinstalled products for the Linux RedHat 8.0 platform+ +
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.
- - + +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. 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 (inluding 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. + +-Pick up the environment-Please, read carefully the following information. This section describes -how the installation procedure collects environment. + +Pick up the environment+ Please, read carefully the following information. This section describes + how the installation procedure collects environment.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 + 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.
- 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. In any case you may edit salome.* files after installation procedure -finishes, as you want. - - - -Modifying XML configuration -file-You can create your own configuration. Installation -Wizard then can take it as command line argument to provide list of products -you want to install with it. The list of products and some another settings -for the Installation Wizard are provided in xml file. The default file -which Installation Wizard looks for if no command line arguments ar given, -is -config.xml. This section describes the format of configuration -file. -Xml tags are in bold blue, optional sections/tags -are in brackets. - <document>
- -<config> section-This is optional section - contains general information -Installation Wizard itself. + finishes, as you want. + ++ Modifying XML configuration + file+ You can create your own configuration. Installation + Wizard then can take it as command line argument to provide list of products + you want to install with it. The list of products and some another settings + for the Installation Wizard are provided in xml file. The default file which +Installation Wizard looks for if no command line arguments ar given, is config.xml. +This section describes the format of configuration file.+ Xml tags are in bold blue, optional sections/tags +are in brackets. + <document> <config> section+ This is optional section - contains general information + Installation Wizard itself.
-<path> section-This is optional section - contains default directories. + +<path> section+ This is optional section - contains default directories.
-<product> section-This section describes product to be installed with the Installation Wizard. -All tags are obligatory. Products appears in the products tree and are -installed in the order they are described in the configuration file. It -is recommended to insert native products at the top of the list before -all other products. + +<product> section+ This section describes product to be installed with the Installation Wizard. + All tags are obligatory. Products appears in the products tree and are installed +in the order they are described in the configuration file. It is recommended +to insert native products at the top of the list before all other products. +
- - -Implementing installation -scripts for the new products-When you want some product to be installed with the Installation Wizard, -you should add it's description it in the configuration -file and create bash installation script, following described in this -section rules. -There are some obligatory functions to be provided in this installation -script. These functions are automatically called by master installation -script or/and GUI shell when it is necessary. +next section for more details. + + Implementing installation + scripts for the new products+ When you want some product to be installed with the Installation Wizard, + you should add it's description it in the configuration + file and create bash installation script, following described in this + section rules.+ There are some obligatory functions to be provided in this installation +script. These functions are automatically called by master installation script +or/and GUI shell when it is necessary. +File common.sh contains some service functions +which can be used in your installation script, like make_env(), +make_dir(), try_existing(), sort_path(), find_in_path(), +etc.
<product_script_name> <function_name> -<temp_folder> <products_directory> <target_directory> <dependancies> -<product_name> - where
- Example:
- 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. - - + The calling signature of the product installation +script is following: + <product_script_name> <function_name> + <temp_folder> <products_directory> <target_directory> +<dependancies> <product_name> + where Example: 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. + + ++ |