source salome.csh
where <KERNEL_ROOT_DIR> is KERNEL binaries directory, e.g.
- KERNEL_7.5.0 for the 7.5.0 version.
+ KERNEL_7.5.1 for the 7.5.1 version.
2.2. Launching of SALOME
After you set environment you can start SALOME. Go to the KERNEL
- module's binaries directory (KERNEL_7.5.0/bin/salome for the version
- 7.5.0) by using of 'cd' command and then type:
+ module's binaries directory (KERNEL_7.5.1/bin/salome for the version
+ 7.5.1) by using of 'cd' command and then type:
runSalome [<parameters>]
In this scenario it is supposed that you have installed SALOME
modules sources in the /home/user/salome directory. The name of each module
sources directory depends on the version of the platform, for example,
- KERNEL_SRC_7.5.0 for KERNEL module of SALOME version 7.5.0.
+ KERNEL_SRC_7.5.1 for KERNEL module of SALOME version 7.5.1.
Compilation and installation should be performed according to
the dependencies between modules:
* GHS3DPRLPLUGIN -> KERNEL, GUI, GEOM, SMESH
* BLSURFPLUGIN -> KERNEL, GUI, GEOM, SMESH
* HexoticPLUGIN -> KERNEL, GUI, GEOM, SMESH, BLSURFPLUGIN
+ * HYBRIDPLUGIN -> KERNEL, GUI, GEOM, SMESH
* HEXABLOCKPLUGIN -> KERNEL, GUI, GEOM, SMESH, HEXABLOCK
Sample modules:
compiling them if you do not plan to use NETGEN and/or GHS3D meshing
algorithms and do not want to build samples.
- Note: Meshing plug-ins BLSURFPLUGIN, HexoticPLUGIN, GHS3DPLUGIN and
- GHS3DPRLPLUGIN require commercial license for the Distene
+ Note: Meshing plug-ins BLSURFPLUGIN, HexoticPLUGIN, GHS3DPLUGIN,
+ GHS3DPRLPLUGIN and HYBRIDPLUGIN require commercial license for the Distene
meshers in runtime mode. Moreover, BLSURFPLUGIN requires
blsurf product at the compilation time. Without it, the
BLSURFPLUGIN meshing plugin compilation will fail. Refer
- create a configuration script by typing
- ../KERNEL_SRC_7.5.0/build_configure
+ ../KERNEL_SRC_7.5.1/build_configure
- run configure script which will check the environment and create
Makefile files:
- ../KERNEL_SRC_7.5.0/configure --prefix=/home/user/salome/KERNEL-7.5.0
+ ../KERNEL_SRC_7.5.1/configure --prefix=/home/user/salome/KERNEL-7.5.1
Note, that --prefix option defines the directory where you want to
install KERNEL module after 'make install' procedure. configure script
make install
After you have completed this scenario, KERNEL module is built and
- installed into /home/user/salome/KERNEL-7.5.0 directory.
+ installed into /home/user/salome/KERNEL-7.5.1 directory.
- modify your environment scripts:
* for bash:
- export KERNEL_ROOT_DIR=/home/user/salome/KERNEL-7.5.0
+ export KERNEL_ROOT_DIR=/home/user/salome/KERNEL-7.5.1
* for csh:
- setenv KERNEL_ROOT_DIR /home/user/salome/KERNEL-7.5.0
+ setenv KERNEL_ROOT_DIR /home/user/salome/KERNEL-7.5.1
- then repeat this scenario for other modules you want to build taking
into account the dependencies between modules (see dependencies table
setenv MODULE_ROOT_DIR /home/user/salome/<MODULE_distribution>
- where <MODULE_distribution> is a MODULE-7.5.0 (see above).
+ where <MODULE_distribution> is a MODULE-7.5.1 (see above).
4.2. Automatic build procedure: build.sh script
- run cmake
- cmake -DCMAKE_INSTALL_PREFIX=/home/user/salome/KERNEL-7.5.0 ../KERNEL_SRC_7.5.0
+ cmake -DCMAKE_INSTALL_PREFIX=/home/user/salome/KERNEL-7.5.1 ../KERNEL_SRC_7.5.1
Note, that -DCMAKE_INSTALL_PREFIX option defines the directory where you want to
install KERNEL module after 'make install' procedure. You
make install
After you have completed this scenario, KERNEL module is built and
- installed into /home/user/salome/KERNEL-7.5.0 directory.
+ installed into /home/user/salome/KERNEL-7.5.1 directory.
- modify your environment scripts:
* for bash:
- export KERNEL_ROOT_DIR=/home/user/salome/KERNEL-7.5.0
+ export KERNEL_ROOT_DIR=/home/user/salome/KERNEL-7.5.1
* for csh:
- setenv KERNEL_ROOT_DIR /home/user/salome/KERNEL-7.5.0
+ setenv KERNEL_ROOT_DIR /home/user/salome/KERNEL-7.5.1
================================================================================
