NOT UP TO DATE AND INCOMPLETE DOCUMENT BUT CAN BE HELPFUL
You'll find here generic instructions for installing the SALOME platform.
First of all, you have to check (or install if needed) the dependant software programs on your system. These programs are:
If the dependencies are installed on your system, then you have to set your shell environment to get access to the software components (cf. Preparing the shell environment).
The next step is to install the KERNEL (cf. Installing the KERNEL component):
$ mkdir <kernel_build> $ mkdir <kernel_install> $ cd <kernel_src> $ ./build_configure $ cd <kernel_build> $ <kernel_src>/configure --prefix=<kernel_install> $ make $ make install
Then, the SALOME components GEOM, MED, VISU, ... can be installed with a similar procedure (cf. Installing the SALOME components).
Eventually, the platform can be run by executing the shell script runSalome (cf. Runtime). Here, somme additionnal variables have to be set to describe the SALOME runtime configuration (<COMPONENT>_ROOT_DIR, OMNIORB_CONFIG)
The following provides you with specific instructions for each step.
SALOME is compiled and tested on differents platforms with native packages:
If you have another platform, we suggest the following configuration for building process:
The SALOME platform relies on a set of third-party softwares. The current version depends on the following list (versions given here are from Debian Sarge, except OpenCascade, VTK and MED, which are not Debian packages):
And, in order to build the documentation:
Additionnal software may be installed for optional features:
In the following, we assume that all the third-party softwares are installed in the same root directory, named <salomeroot>/prerequis. Then, your file system should probably look like:
<salomeroot>/prerequis/Python-2.2.2 <salomeroot>/prerequis/omniORB-3.0.5 <salomeroot>/prerequis/qt-x11-free-3.0.5 ...
Some variables have to be set to get access to third-party software components (include files, executable, library, ...) during building process and runtime.
The shell file prerequis.sh, embedded in the KERNEL source package, provides a template for setting those variables. In this example, all the softwares are supposed to be installed in the same root directory, named here INSTALLROOT.
Copy the prerequis.sh in a working directory and adjust the settings to your own configuration. To get the shell prepared, just execute the following command in the building shell:
$ source prerequis.sh
(we assume here a ksh or bash mode)
We use here the notation <kernel_src> to specify the source directory of the KERNEL component. The shell environment is supposed to have been set (cf. Preparing the shell environment).
Installing the KERNEL from a source package needs three directories:
The installing process is:
STEP 1: preparing directories
create the <kernel_build> and the <kernel_install> directories:
$ mkdir <kernel_build> $ mkdir <kernel_install>
STEP 2: build configure script
go to <kernel_src> directory and generate the "configure" script:
$ cd <kernel_src> $ ./build_configure
If it doesn't work, check your system automake tools as specified in section System configuration.
STEP 3: configure the building process go to the build directory and execute the configuration process:
$ cd <kernel_build> $ <kernel_src>/configure --prefix=<kernel_install>
Note that <kernel_install> must be an absolute path.
When the configure process is complete, check the status of third-party softwares detection. You should have a status like:
--------------------------------------------- Summary --------------------------------------------- Configure cc : yes boost : yes lex_yacc : yes python : yes swig : yes threads : yes OpenGL : yes qt : yes vtk : yes hdf5 : yes med2 : yes omniORB : yes occ : yes sip : yes pyqt : yes qwt : yes doxygen : yes graphviz : no openpbs : no lsf : no Default ORB : omniORB ----------------------------------------------
If a software get a status "no", then it's not "seen" in the system:
In this example, the software programs graphviz, openpbs and lsf are not installed (optional for most usages).
STEP 4 : Building the binary files
Execute make in the <kernel_build> directory:
STEP 5: Installing binary files, scripts and documentation
Execute install target in the <kernel_build> directory:
$ make install
Installing a component <COMPONENT> is done by following the same instructions as given for the KERNEL, replacing KERNEL by <COMPONENT> (build_configure, configure, make, make install).
You just have to be aware of the dependencies between components:
For example, installing the component SMESH needs the previous installation of the KERNEL component, and then the GEOM and MED components.
The building process uses the variables <COMPONENT>_ROOT_DIR to localize the dependant components. The variables must be set to the install path directory of the components <COMPONENT> (ex: KERNEL_ROOT_DIR=<kernel_install>).
In the above example, the three variables KERNEL_ROOT_DIR, GEOM_ROOT_DIR and MED_ROOT_DIR have to be set before configuring the building process of the SMESH component (STEP 3).
See Salome Application Concept to define your own configuration of SALOME and run it on one or several computers. This is the recommended way of configuration.
The following explains the general principles.
To run the SALOME platform, the procedure is:
$ source prerequis.sh
$ export KERNEL_ROOT_DIR=<kernel_install> $ export MED_ROOT_DIR=<med_install> $ ...
$ export OMNIORB_CONFIG=$HOME/.omniORB.cfg
For convenience or customization, we suggest the following organisation:
$ cp <kernel_src>/prerequis.sh <rundir>/. $ cp <kernel_install>/bin/salome/runSalome <rundir>/.
$ source envSalome.sh
$ source <salomeroot>/prerequis.sh $ source <salomeroot>/envSalome.sh $ ./runSalome