From: nadir <nadir>
Date: Thu, 8 Jun 2006 12:20:49 +0000 (+0000)
Subject: Committing of a more precise README file in the Med Memory V3_2_0.
X-Git-Tag: V3_2_0~1
X-Git-Url: http://git.salome-platform.org/gitweb/?a=commitdiff_plain;h=879fcc970cdf67b07acfdfbfca585b6e6e3a189f;p=modules%2Fmed.git

Committing of a more precise README file in the Med Memory V3_2_0.
---

diff --git a/README b/README
index 975c66396..1e366e41b 100644
--- a/README
+++ b/README
@@ -50,42 +50,110 @@ Server/Client configuration.
 II : MedMemory building and installation :
 =========================================
 
-It's very simple :
+Assuming that the rather straightforward
+
+path_to_your_MedMemory_installation_directory,
+
+path_to_your_MedMemory_building_directory,
+
+path_to_your_MedMemory_sources_directory,
+
+path_to_your_MedFile_installation_directory,
+
+path_to_your_HDF5_installation_directory,
+
+directories are setted; the user/installer may use the following commands to
+build the Med Memory installation as a Salome component :
+
+In the directory path_to_your_MedMemory_building_directory;
+
+path_to_your_MedMemory_sources_directory/build_configure
+
+path_to_your_MedMemory_sources_directory/configure --prefix=path_to_your_MedMemory_installation_directory
 
-./configure --prefix=path_to_your_installation_directory
 make
+
 make install
 
-eventually if the user or the installer needs to build an installation of Med
-Memory as a stand alone package, he may use the configure option
---without-kernel. By default the full debug options are set:
+Eventually if the user/installer needs to build an installation of Med
+Memory as a stand alone package, he/she may use always in the
+path_to_your_MedMemory_building_directory, the following commands :
+
+path_to_your_MedMemory_sources_directory/build_configure --without-kernel
+
+path_to_your_MedMemory_sources_directory/configure --prefix=path_to_your_MedMemory_installation_directory
+
+make
+
+make install
+
+Remark :  If the installer gets the sources archives from the NEPAL web site
+--------  (CEA, EDF, OCC, ie hammi web site) the user may only use the
+          following commands :
+
+          path_to_your_MedMemory_sources_directory/configure --prefix=path_to_your_MedMemory_installation_directory
+
+          make
+
+          make install
+
+
+By default the full debug options are set:
       - compilation using -g option
       - Med Memory debugging information history using -D_DEBUG_ option.
 
-The user may get all configure option with :
-  ./configure --help
+The user/installer may
+
+get all configure option with :
+
+path_to_your_MedMemory_sources_directory/configure --help
+
+set optimization option :
+
+path_to_your_MedMemory_sources_directory/configure --enable-production --disable-debug (use compiler flags -O)
+
+In order to avoid most of the problem the user/installer should first
+check the $HDF5HOME and the $MED2HOME environment variables. In csh:
 
-The user may set optimization option :
-  ./configure --enable-production --disable-debug (use compiler flags -O)
+setenv HDF5HOME path_to_your_HDF5_installation_directory
 
-In order to avoid most of the problem the user or the installer should first
-check the HDF5HOME and the MED2HOME environment variables. This version of
-Med Memory with Med File V2.2.2, V2.2.3, as well as V2.3.0 but with the
-version of HDF5 V1.6.3. In the installation of Med File you should take care
-of the $HDF5HOME environement variable. This warning is especially intended
-to the user of The Med Memory in stand alone (without the SALOME KERNEL
-component).
+setenv MED2HOME path_to_your_MedFile_installation_directory
+
+This version of Med Memory has been tested with Med File V2.2.2, V2.2.3, as
+well as V2.3.0 but with the version of HDF5 V1.6.3. Thus, in the installation
+process of Med File the user/installer should take care of the $HDF5HOME
+environement variable. This warning is especially intended to the user of the
+Med Memory in its stand alone vesion (ie without the SALOME KERNEL component).
 
 III : MedMemory testing :
 =========================
 
-After installation of the Med Memory; the user may find a large set of test
-files in Med File V2.1, V2.2, GIBI format.
+After installation of the Med Memory; the user/installer may find a large set
+of Med File V2.1, V2.2, GIBI test files in the directory :
+
+path_to_your_MedMemory_installation_directory/share/salome/resources/
+
+For user/installer of the Med Meory as a Salome component, sourcing the usual
+Salome environement and using the usual runSalome command, all needed
+environement variables (such as $MED_ROOT_DIR, $LD_LIBRARY_PATH and
+$PYTHONPATH) are well setted.
+
+But for the user/installer of the Med Memory as a stand alone version should
+set his/her environement. Assuming that $HDF5HOME $MED2HOME are setted
+properly, in csh :
+
+setenv MED_ROOT_DIR path_to_your_MedMemory_installation_directory
+
+setenv PATH ${MED2HOME}/bin:${HDF5HOME}/bin:$PATH
+
+setenv LD_LIBRARY_PATH ${MED_ROOT_DIR}/lib/salome:${MED2HOME}/lib:${HDF5HOME}/lib:$LD_LIBRARY_PATH
+
+setenv PYTHONPATH ${MED_ROOT_DIR}/bin/salome:${MED_ROOT_DIR}/lib/salome:${MED_ROOT_DIR}/lib/python${PYTHON_VERSION}/site-packages/salome:
 
 To check the Med Memory installation, in the directory
-path_to_your_installation_directory/bin/salome you may find a set of python
-scripts and test executable. To ckeck the deep layers (C++, Python) of the Med
-Memory, the installer may run:
+path_to_your_MedMemory_installation_directory/bin/salome you may find a set of
+python scripts and test executable. To ckeck the deep layers (C++, Python) of
+the Med Memory, the installer may run:
 
 - testMedMemGeneral.py,
 - medMeshing_test.py