-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 Linux version and uses corresponding xml file.
- For example, for the Mandrake 10.1 config_Mandrake10_1.xml file
- is supposed to be used by default. If the appropriate file
- is not found, config.xml is used by default. This file usually
- refers to the default target platform. For SALOME version 3.0.0
- and higher default target platform is Linux Mandrake 10.1.
+ automatically the Linux platform and use the corresponding xml file
+ if there is one provided.
+ For example, for Linux Mandrake 10.1 config_Mandrake_10.1.xml file
+ will be used by default. If the appropriate file is not found,
+ default config.xml will be used. This file contains default
+ installation settings. From SALOME version 3.0.0
+ the default target platform is Linux Mandrake 10.1.
-t <target-dir>
The target directory SALOME products to be installed to.
After you set environment you can start SALOME. Go to the KERNEL
module's binaries directory (KERNEL_3.0.0/bin/salome for the version
- 3.0.0) by using of cd command and then type:
+ 3.0.0) by using of 'cd' command and then type:
runSalome [<parameters>]
- This will start SALOME according to the configuration parameters which
+ This will start SALOME according to the launching parameters which
are described in the configuration files: SalomeApp.xml in the
<GUI_ROOT_DIR>/share/salome/resources folder and .SalomeApprc.<version_number>
file, located in your home directory (where <version_number> is number
- of SALOME version). If the latest file does not exist, it is created during
- the first launch of SALOME.
+ of SALOME version). If the latest file does not exist, it is automatically
+ created during the first launch of SALOME.
You can modify SALOME launching options by editing your
~/.SalomeApprc.<version_number> file:
</section>
Some parameters described in configuration file can be overrided by
- using of corresponding command-line keys for runSalome script:
+ using of corresponding command-line options for runSalome script:
--gui
Launch GUI desktop
time of the installation is:
- from binaries: ~10 minutes;
- - from sources: up to 7 hours.
+ - from sources: more than 24 hours.
+
+ Note, the most time-consuming process is compiling of CASCADE libraries from
+ sources - it takes about 90% of time needed for compilation of all products.
3.2. Log files
When running, the script loads different modules (Geometry, Mesh, Med,
Post-Pro and Supervisor) and tests different functionality of these
- modules. You can watch script running progress in the python console
- window.
+ modules. You can watch script running progress in the embedded
+ python console window.
================================================================================
If you want to build SALOME modules from sources, install all prerequisite
products, required for the platform and SALOME modules sources.
Then follow the scenario described below.
- In the scenario below it is supposed that you have installed SALOME
+ In this scenario it is supposed that you have installed SALOME
modules sources in the /home/salome directory. The name of each module
sources directory depends on the version of the platform, for example,
KERNEL_SRC_3.0.0 for KERNEL module of SALOME version 3.0.0.
Sample modules:
- * COMPONENT -> KERNEL
- * PYCALCULATOR -> KERNEL,
+ * COMPONENT -> KERNEL, MED
+ * PYCALCULATOR -> KERNEL, MED
+ * CALCULATOR -> KERNEL, MED
* HELLO -> KERNEL, GUI
- * PYHELLO -> KERNEL, GUI
+ * PYHELLO -> KERNEL
* LIGHT -> KERNEL, GUI
Note: SMESH plugins and sample modules are optional. You may skip
- compiling them if you do not plan to use NETGEN and/or GHS3D mesher
+ compiling them if you do not plan to use NETGEN and/or GHS3D meshing
algorithms and do not want to build samples.
In general, each module (except KERNEL and GUI, of course) is optional for
- create a configuration script by typing
- ../KERNEL_SRC_3.3.0/build_configure
+ ../KERNEL_SRC_3.0.0/build_configure
- run configure script which will check the environment and create
Makefile files:
- ../KERNEL_SRC_3.3.0/configure --prefix=/home/salome/KERNEL_install
+ ../KERNEL_SRC_3.0.0/configure --prefix=/home/salome/KERNEL_install
Note, that --prefix option defines the directory where you want to
install KERNEL module after 'make install' procedure. configure script
4.2. Automatic build procedure: build.csh script
- From version 2.2.0 SALOME Installation Wizard provides the script
+ From version 2.2.0 SALOME Installation Wizard includes the script
for automatic building of SALOME modules from sources packages:
build.csh. It is installed into the top-level target directory
(the same directory where env_products.[c]sh files are generated.
./build.csh
- and that's all.
-
By default, build.csh only compiles the modules but does not install them,
i.e. does not perform 'make install' step.
To do this, use -i option or -p <prefix> where <prefix> is target
When you run build.csh at first time it is not necessary to pass
-b, -c parameters. The script detects if build procedure has not yet
- been performed and runs build_configure, configure procedures
+ been performed and runs build_configure, configure scripts
in this case automatically.
Note: for avoiding of collisions it is recommended not to install
