From: vsr Date: Mon, 15 Jun 2009 13:49:20 +0000 (+0000) Subject: Rollback products: qt -> 4.4.3, sip -> 4.7.7, PyQt -> 4.4.3, qwt -> 5.1.1, QScintilla... X-Git-Tag: V5_1_2~7 X-Git-Url: http://git.salome-platform.org/gitweb/?a=commitdiff_plain;h=ad913471074c68cd69b3effbcbc40fc0f946e226;p=tools%2Finstall.git Rollback products: qt -> 4.4.3, sip -> 4.7.7, PyQt -> 4.4.3, qwt -> 5.1.1, QScintilla -> 2.3 --- diff --git a/README b/README index d6254fc..0b3dd51 100644 --- a/README +++ b/README @@ -154,7 +154,7 @@ - + @@ -293,7 +293,7 @@ import salome_test When running, the script loads different modules (Geometry, Mesh, Med, - Post-Pro and Supervisor) and tests various functionalities of these + Post-Pro) and tests various functionalities of these modules. You can watch the script execution progress in the embedded python console window. @@ -316,7 +316,7 @@ products, required for the platform and SALOME modules sources. Then follow the scenario described below. In this scenario it is supposed that you have installed SALOME - modules sources in the /home/salome directory. The name of each module + 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. @@ -331,15 +331,15 @@ * MED -> KERNEL, GUI * SMESH -> KERNEL, GUI, GEOM, MED * VISU -> KERNEL, GUI, MED - * SUPERV -> KERNEL, GUI + * YACS -> KERNEL, GUI SMESH plugins: - * NETGENPLUGIN -> KERNEL, GUI, SMESH - * GHS3DPLUGIN -> KERNEL, GUI, SMESH - * GHS3DPRLPLUGIN -> KERNEL, GUI, SMESH - * HexoticPLUGIN -> KERNEL, GUI, SMESH - * BLSURFPLUGIN -> KERNEL, GUI, SMESH + * NETGENPLUGIN -> KERNEL, GUI, MED, GEOM, SMESH + * GHS3DPLUGIN -> KERNEL, GUI, MED, GEOM, SMESH + * GHS3DPRLPLUGIN -> KERNEL, GUI, MED, GEOM, SMESH + * HexoticPLUGIN -> KERNEL, GUI, MED, GEOM, SMESH + * BLSURFPLUGIN -> KERNEL, GUI, MED, GEOM, SMESH Sample modules: @@ -347,15 +347,23 @@ * PYCALCULATOR -> KERNEL, MED * CALCULATOR -> KERNEL, MED * HELLO -> KERNEL, GUI - * PYHELLO -> KERNEL + * PYHELLO -> KERNEL, GUI * LIGHT -> KERNEL, GUI + * PYLIGHT -> KERNEL, GUI * RANDOMIZER -> KERNEL, GUI - * SIERPINSKY -> KERNEL, GUI, VISU, RANDOMIZER + * SIERPINSKY -> KERNEL, GUI, MED, VISU, RANDOMIZER Note: SMESH plugins and sample modules are optional. You may skip 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 and + GHS3DPRLPLUGIN 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 + to http://www.distene.com/ for more details. + In general, each module (except for KERNEL and GUI, of course) is optional for SALOME. If you do not need a certain module, just do not compile or install it. But remember that some modules require others @@ -363,9 +371,9 @@ To build KERNEL module: - - go to installation root directory (/home/salome in this example): + - go to installation root directory (/home/user/salome in this example): - cd /home/salome + cd /home/user/salome - to set environment variables use bash or csh script, depending on your shell: @@ -386,7 +394,7 @@ - run configure script which will check the environment and create Makefile files: - ../KERNEL_SRC_5.1.2/configure --prefix=/home/salome/KERNEL_install + ../KERNEL_SRC_5.1.2/configure --prefix=/home/user/salome/KERNEL-5.1.2 Note, that --prefix option defines the directory where you want to install KERNEL module after 'make install' procedure. configure script @@ -395,29 +403,23 @@ You can learn more about the configure of any modules by using --help (-h) parameter. - - build and (optionally) install KERNEL module: + - 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. + installed into /home/user/salome/KERNEL-5.1.2 directory. - modify your environment scripts: * 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). + export KERNEL_ROOT_DIR=/home/user/salome/KERNEL-5.1.2 * for csh: - setenv KERNEL_ROOT_DIR /home/salome/KERNEL_install - or - setenv KERNEL_ROOT_DIR /home/salome/KERNEL_build - (if make install step was not performed). + setenv KERNEL_ROOT_DIR /home/user/salome/KERNEL-5.1.2 - then repeat this scenario for other modules you want to build taking into account the dependencies between modules (see dependencies table @@ -429,13 +431,13 @@ * for bash: - export MODULE_ROOT_DIR=/home/salome/ + export MODULE_ROOT_DIR=/home/user/salome/ * for csh: - setenv MODULE_ROOT_DIR /home/salome/ + setenv MODULE_ROOT_DIR /home/user/salome/ - where is a MODULE_build or MODULE_install (see above). + where is a MODULE-5.1.2 (see above). 4.2. Automatic build procedure: build.csh and build.sh scripts