4. How to build SALOME modules from sources
4.1. General procedure
- 4.2. Automatic build procedure: build.csh script
+ 4.2. Automatic build procedure: build.sh script
4.3. Build SALOME using cmake
================================================================================
where <MODULE_distribution> is a MODULE-7.3.0 (see above).
- 4.2. Automatic build procedure: build.csh and build.sh scripts
+ 4.2. Automatic build procedure: build.sh script
- SALOME Installation Wizard includes two scripts which can be used
- for automatic building of SALOME modules from sources packages:
- build.csh and build.sh. The scripts are installed into the top-level
- installation directory (the same directory where env_products.[c]sh
- files are generated).
-
- The build.csh and buils.sh scripts implement the same functionality
- and support the same set of options, but for different shells.
- Use build.csh script for csh and build.sh for bash.
- The description below refers to both scripts.
+ SALOME Installation Wizard includes build.sh script which can be used
+ for automatic building of SALOME modules from sources packages.
+ This script is copied into the top-level installation directory
+ (the same directory where env_products.[c]sh files are generated).
To use the script just install SALOME sources packages with the
Installation Wizard, then cd to the SALOME installation directory
and type:
- ./build.csh
+ ./build.sh
- By default, build.csh builds and installs all SALOME
+ By default, build.sh builds and installs all SALOME
modules. All modules are installed to the INSTALL subfolder
of the current directory. If you need to change the installation
directory, you can use -p <prefix> option where <prefix> is the
If you want to build only some subset of SALOME modules,
just pass them as parameters, e.g.:
- ./build.csh -p /home/user/salome KERNEL MED GEOM
+ ./build.sh -p /home/user/salome KERNEL MED GEOM
The script also provides other options which specify compiling and
installation parameters. You can learn about these options by using
-h key:
- ./build.csh -h
-
- When you run build.csh for the first time it is not necessary to pass
- -b or -c parameters. The script detects if build procedure has not yet
- been performed and in this case runs build_configure, configure scripts
- automatically.
+ ./build.sh -h
- Note: to avoid collisions it is recommended not to install
+ Note: to avoid collisions it is recommended to avoid installation of
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.
+ SALOME modules from sources packages; if you still install binary
+ packages of SALOME module, you can manually edit env_products.[c]sh
+ scripts by commenting all rows concerning environment of SALOME
+ binaries packages.
- Note: use -d option carefully because in this case the script removes
+ Note: use -d option of the build.sh script carefully because
+ when this option is specified to the script, it can remove
the existing (previously installed) SALOME modules.
- Note: build.(c)sh scripts do not modify the environment files
- (env_products.csh, etc). You should do it by yourself.
-
- 4.3. Build SALOME using cmake
+ Note: build.sh script does not modify the environment files
+ (env_products.[c]sh, env_build.[c]sh). You should do it by yourself.
- Some (but not all) SALOME modules can be built using
- cmake. If you want to learn what modules can be built with
- cmake, just check the root source directory and look for
- CMakeLists.txt file or build_cmake script.
+ 4.3. Build SALOME modules manually
- This paragraph describes the steps that should be done in
- order to build SALOME modules using cmake.
+ The build procedure of all SALOME modules is implemented with
+ CMake. This paragraph describes the steps that can be done in
+ order to build SALOME modules manually.
For example, to build KERNEL module:
or
source ./env_products.sh
- - generate CMakeLists.txt files:
-
- cd KERNEL_SRC_7.3.0
- ./build_cmake
- cd ..
-
- Note, that this step is not required for PARAVIS module,
- since it is already supplied with the CMakeLists.txt
- files. For other modules, build_cmake script generates
- CMakeLists.txt files from the Makefile.am files.
-
- create build directory for the KERNEL module:
mkdir KERNEL_build
