X-Git-Url: http://git.salome-platform.org/gitweb/?a=blobdiff_plain;f=README;h=fa1a5f1a9cbb43d52a322cdb7f2c0ea04a368e49;hb=b0a22d84b4ffa96c45d700d89c4c43986f0ddfea;hp=094ca893c58510a7fd5b493aeb59899e5f285903;hpb=69677c5f786e30267c956a426c0bba5ddf1d4e1d;p=tools%2Finstall.git diff --git a/README b/README index 094ca89..fa1a5f1 100644 --- a/README +++ b/README @@ -122,13 +122,13 @@ source salome.csh where is KERNEL binaries directory, e.g. - KERNEL_5.1.2 for the 5.1.2 version. + KERNEL_5.1.3 for the 5.1.3 version. 2.2. Launching of SALOME After you set environment you can start SALOME. Go to the KERNEL - module's binaries directory (KERNEL_5.1.2/bin/salome for the version - 5.1.2) by using of 'cd' command and then type: + module's binaries directory (KERNEL_5.1.3/bin/salome for the version + 5.1.3) by using of 'cd' command and then type: runSalome [] @@ -318,7 +318,7 @@ 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_5.1.2 for KERNEL module of SALOME version 5.1.2. + KERNEL_SRC_5.1.3 for KERNEL module of SALOME version 5.1.3. Compilation and installation should be performed according to the dependencies between modules: @@ -389,12 +389,12 @@ - create a configuration script by typing - ../KERNEL_SRC_5.1.2/build_configure + ../KERNEL_SRC_5.1.3/build_configure - run configure script which will check the environment and create Makefile files: - ../KERNEL_SRC_5.1.2/configure --prefix=/home/user/salome/KERNEL-5.1.2 + ../KERNEL_SRC_5.1.3/configure --prefix=/home/user/salome/KERNEL-5.1.3 Note, that --prefix option defines the directory where you want to install KERNEL module after 'make install' procedure. configure script @@ -409,17 +409,17 @@ make install After you have completed this scenario, KERNEL module is built and - installed into /home/user/salome/KERNEL-5.1.2 directory. + installed into /home/user/salome/KERNEL-5.1.3 directory. - modify your environment scripts: * for bash: - export KERNEL_ROOT_DIR=/home/user/salome/KERNEL-5.1.2 + export KERNEL_ROOT_DIR=/home/user/salome/KERNEL-5.1.3 * for csh: - setenv KERNEL_ROOT_DIR /home/user/salome/KERNEL-5.1.2 + setenv KERNEL_ROOT_DIR /home/user/salome/KERNEL-5.1.3 - then repeat this scenario for other modules you want to build taking into account the dependencies between modules (see dependencies table @@ -437,7 +437,7 @@ setenv MODULE_ROOT_DIR /home/user/salome/ - where is a MODULE-5.1.2 (see above). + where is a MODULE-5.1.3 (see above). 4.2. Automatic build procedure: build.csh and build.sh scripts