================================================================================
README
- SALOME Professional Installation Wizard
+ SALOME Installation Wizard
================================================================================
Contents of this file:
3.2. Log files
3.3. Testing of the installed SALOME platform
- 4. How to build SALOME from sources
+ 4. How to build SALOME modules from sources
+ 4.1. General procedure
+ 4.2. Automatic build procedure: build.csh script
================================================================================
1. Running of the Installation Wizard
You can run the Installation Wizard in two modes: batch and gui.
- It's root directory contains python script runInstall.py:
+ It's root directory contains python script runInstall:
[python] runInstall [-g|b] [-f <xml-file>] [-t <taget-dir>] [-tmp <tmp-dir>]
-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.
+ the Red Hat version and uses corresponding xml file.
For example, 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.
+ 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, described in the
- configuration file.
+ If used, overloads temporary directory, given in the
+ configuration xml file.
-h
Prints help information.
2. Running of SALOME
- This section describes how to run SALOME platform after its installation with
- the Installation Wizard.
+ This section describes how to run SALOME platform after its installation
+ with the Installation Wizard.
2.1. Setting of the environment for SALOME
Installation Wizard creates some environment files to simplify
the procedure of launching of SALOME. These shell scripts set all
necessary environment variables for all products you have installed.
- 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.
+ These files are:
+ * salome.csh + salome.sh in the KERNEL module's sources/binaries
+ root directories;
+ * env_products.csh + env_products.sh in the target directory.
To set SALOME environment just type in the terminal window:
- cd <SALOME_DIR>
+ cd <KERNEL_ROOT_DIR>
source salome.sh
or
- cd <SALOME_DIR>
+ cd <KERNEL_ROOT_DIR>
source salome.csh
- where <SALOME_DIR> is SALOME binaries directory, e.g. SalomePro-1.2d
- for the 1.2d version.
-
+ where <KERNEL_ROOT_DIR> is KERNEL binaries directory, e.g.
+ KERNEL_2.2.0 for the 2.2.0 version.
2.2. Launching of SALOME
- After you set environment you can start SALOME. Go to the SALOME
- binaries directory (SalomePro-1.2d for the version 1.2d) by using
- of cd command and then type:
-
- salome --gui
-
- This will start SALOME servers and launch GUI desktop. If you want
- to launch SALOME in the batch mode, use --batch option:
-
- salome --batch
-
- If you want to launch SALOME using specific port, use --port key:
-
- salome --gui --port XXXX
-
- where XXXX is a port number.
- Note, that in this case you have to write the same port number into
- your ORB configuration file, which should be referenced by the
- $(OMNIORB_CONFIG) environment variable (usually it is an omniORB.cfg
- file), e.g.:
-
- ORBInitRef NameService=corbaname::<host-name>:<port-number>
-
- <host-name> is a name of host where Naming Service should be run
- and <port-number> is a number of port to be used.
- The default port number is 2809. The using of non-default port
- is useful when it is necessary for several users to launch
- SALOME on the same host.
-
- Use --help key to display additional information to learn other
- salome script options.
-
- Note: salome script is included into SALOME package only from 1.2d
- version. In order to run salome for the previous versions you should
- use runSalome script from the bin sub-directory of SALOME:
-
- cd bin
- runSalome
+ After you set environment you can start SALOME. Go to the KERNEL
+ module's binaries directory (KERNEL_2.2.0/bin/salome for the version
+ 2.2.0) by using of cd command and then type:
+
+ runSalome [<parameters>]
+
+ This will start SALOME according to the configuration parameters which
+ are described into salome.launch file, located in your home directory
+ ( $HOME/.salome_<version-number>/salome.launch ),
+ where <version_number> is number of SALOME version.
+
+ If this file does not exists, it is created on the first launch of
+ SALOME from <KERNEL_ROOT_DIR>/bin/salome/salome.launch.
+
+ You can modify SALOME launching options by editing
+ salome_<version_number>.launch file:
+
+ <Configuration-list>
+ <launchoptions>
+ <gui>yes</gui>
+ <logger>no</logger>
+ <xterm>no</xterm>
+ <portkill>yes</portkill>
+ <killall>no</killall>
+ </launchoptions>
+ <modules-list>
+ <module name="...">
+ <plugin name="..."/>
+ </module>
+ </modules-list>
+ <embedded-list>
+ <embeddedserver>...</embeddedserver>
+ </embedded-list>
+ <standalone-list>
+ <standaloneserver>...</standaloneserver>
+ </standalone-list>
+ </Configuration-list>
+
+ Each parameter described in salome.launch file can be overrided by
+ using corresponding keys for runSalome script:
+
+ --gui
+ Launch GUI desktop
+ --logger
+ Use logger server
+ --xterm
+ Start each server in its own xterm console window
+ --portkill
+ Kill SALOME, running on the current port
+ --killall
+ Kill SALOME, running on all ports
+ --modules=<module>,<module>,...,<module>
+ Use module(s), possible values are GEOM,SMESH,VISU,MED,SUPERV
+ --embedded=<container>,<container>,...<container>
+ Start specified container(s) embedded in SALOME Session server
+ (i.e. running in the same process), possible values are registry,
+ study, moduleCatalog, cppContainer, pyContainer, supervContainer
+ --standalone=<container>,<container>,...<container>
+ Start standalone container(s), possible values are registry,
+ study, moduleCatalog, cppContainer, pyContainer, supervContainer
+
+ Note that there is no key which corresponds to the <plugin> tag.
+ This tag can be used currently only for SMESH module to point external
+ meshers plugins which should be loaded by SMESH dynamically.
+ Refer <SMESH_ROOT_DIR>/doc/salome/tui/SMESH/PluginMeshers.html
+ for more information om meshers plugins.
================================================================================
directory to store and build the products. During the installation
it produces some log files in this directory. If you suspect that
program hangs you can check the log files. These files have names
- in capital letters like CONFIGURE.LOG, MAKE.LOG or MAKEINSTALL.LOG.
+ in capital letters like CONFIGURE.LOG, MAKE.LOG, MAKEINSTALL.LOG, etc.
3.3. Testing of installed SALOME platform
import salome_test
- When running, the script loads diferent modules (Geometry, SMESH, Med,
- Visu and Supervision) and tests different functionalty of these
+ When running, the script loads diferent 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.
================================================================================
- 4. How to build SALOME from sources
+ 4. How to build SALOME modules from sources
+
+ This section describes the way how to build SALOME modules manually from
+ sources packages provided with Installation Wizard.
+ 4.1. General procedure
+
+ If you want to build SALOME modules from sources, install all products
+ necessary 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
+ 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_2.2.0 for KERNEL module of SALOME version 2.2.0.
+
+ The order of compilation and installation should be performed according
+ to the dependancies between modules:
+
+ * KERNEL -> no dependancies
+ * GEOM -> KERNEL
+ * MED -> KERNEL
+ * SMESH -> KERNEL, GEOM, MED
+ * VISU -> KERNEL, MED
+ * SUPERV -> KERNEL
+ * COMPONENT -> KERNEL
+ * PYCALCULATOR -> KERNEL
+ * NETGENPLUGIN -> KERNEL, SMESH
+ * GHS3DPLUGIN -> KERNEL, SMESH
+
+ Note: NETGENPLUGIN, GHS3DPLUGIN are optional components. You may skip
+ compiling them if you do not plan to use NETGEN and/or GHS3D mesher
+ algorithms.
+ In general, each module (except KERNEL, of course) is optional for
+ SALOME. If you do not need any module, just do not compile or install
+ it. But remember that some modules require other ones to be built first
+ (see dependancies table above).
+
+ - go to KERNEL module's sources directory:
+
+ cd /home/salome/KERNEL_SRC_2.2.0
+
+ - set environment variables (use bash or csh script, depending on
+ your shell):
+
+ source salome.csh
+ or
+ source salome.sh
+
+ - create a configuration script by typing
+
+ ./build_configure
+
+ - go to the parent directory and create build directory:
+
+ cd ..
+ mkdir KERNEL_build
+
+ - run configure script which will check the environment and create
+ Makefile files:
+
+ cd KERNEL_build
+ ../KERNEL_SRC_2.2.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.
+ More about certain module's configure options you can learn by using
+ --help (-h) parameter.
+
+ - build and install KERNEL module:
+
+ make
+ make install
+
+ After you have completed this scenario, KERNEL module is built and
+ installed into /home/salome/KERNEL_install directory.
+
+ - set environment:
+
+ * for bash:
+
+ export KERNEL_ROOT_DIR=/home/salome/KERNEL_install
+ or
+ export KERNEL_ROOT_DIR=/home/salome/KERNEL_build
+ (if make install step was not performed).
+
+ * for csh:
- If you want to build SALOME from sources, please install all products
- necessary for the platform and then follow the scenario described below.
- In the sample scenario it is supposed that you have installed SALOME
- in the /home/salome directory. The name of the SALOME sources directory
- depends on the version of the platform, in the scenario it is
- SALOME_ROOT_1.2d (for the version 1.2d).
+ setenv KERNEL_ROOT_DIR /home/salome/KERNEL_install
+ or
+ setenv KERNEL_ROOT_DIR /home/salome/KERNEL_build
+ (if make install step was not performed).
- - go to SALOME sources directory:
+ - then repeat this scenario for other modules you want to build taking
+ into account the dependancies between modules (see dependancies table
+ above).
- cd /home/salome/SALOME_ROOT_1.2d
+ Note: if the compilation fails it may be caused by bad environment.
+ In this case you should check that environment script you use
+ (salome.csh or salome.sh) contains the following lines for each module:
- - set environment variables (use bash or csh script, depending on
- your shell):
+ * for bash:
- sources salome.c[s]h
+ export PATH=${<module>_ROOT_DIR}/bin/salome:${PATH}
+ export LD_LIBRARY_PATH=${<module>_ROOT_DIR}/lib/salome:${LD_LIBRARY_PATH}
+ export PYTHONPATH=${<module>_ROOT_DIR}/bin/salome:${PYTHONPATH}
+ export PYTHONPATH=${<module>_ROOT_DIR}/lib/salome:${PYTHONPATH}
+ export PYTHONPATH=${<module>_ROOT_DIR}/lib/python2.2/site-packages/salome:${PYTHONPATH}
+ export PYTHONPATH=${<module>_ROOT_DIR}/lib/python2.2/site-packages/salome/shared_modules:${PYTHONPATH}
- - create a configuration script by typing
+ * for csh:
- ./build_configure
+ setenv PATH ${<module>_ROOT_DIR}/bin/salome:${PATH}
+ setenv LD_LIBRARY_PATH ${<module>_ROOT_DIR}/lib/salome:${LD_LIBRARY_PATH}
+ setenv PYTHONPATH ${<module>_ROOT_DIR}/bin/salome:${PYTHONPATH}
+ setenv PYTHONPATH ${<module>_ROOT_DIR}/lib/salome:${PYTHONPATH}
+ setenv PYTHONPATH ${<module>_ROOT_DIR}/lib/python2.2/site-packages/salome:${PYTHONPATH}
+ setenv PYTHONPATH ${<module>_ROOT_DIR}/lib/python2.2/site-packages/salome/shared_modules:${PYTHONPATH}
+
+ 4.2. Automatic build procedure: build.csh script
- - go to the parent directory and create a build directory:
+ From version 2.2.0 SALOME Installation Wizard provides 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.
- cd ..
- mkdir build
+ To use this script just install SALOME sources packages with
+ Installation Wizard, then cd to the SALOME isntallation directory
+ and type:
- - configure the sources and create Makefile files:
+ ./build.csh
- cd build
- ../SALOME_ROOT_1.2d/configure --prefix=/home/salome/SALOME
+ and that's all.
+
+ By default, build.csh only compiles the modules but not installs them,
+ i.e. does not perform 'make install' step.
+ To do this, use -i option or -p <prefix> where <prefix> is target
+ directory.
- --prefix option defines the directory where you want to install
- SALOME after make install procedure.
+ If you want to build only some SALOME modules, just pass them as
+ parameters, e.g.:
- - build and install SALOME:
+ ./build.csh -i KERNEL MED GEOM
- make
- make install
+ The script also provides some other options which specify compiling
+ and installation parameters. You can learn about options by using
+ -h key:
- - build and install SALOME documentation if necessary:
+ ./build.csh -h
- cd doc
- make doc
- make install
+ 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
+ in this case.
- The last step is not necessary for the SALOME of version 1.2d, because
- it is included into main make (and make install) step.
+ Note: for avoiding of collisions it is recommended not to install
+ SALOME binaries packages with Installation Wizard if you plan to build
+ SALOME modules from sources packages or to edit/comment all rows
+ in env_products.csh file concerning binaries packages.
- After you have completed this scenario, SALOME is built and installed
- into /home/salome/SALOME directory.
+ Note: use -d option carefully because in this case the script removes
+ existing (previously installed) SALOME modules.
================================================================================
