Installation of elsAHere follow overall directions to build elsA from the source code or to properly install an already built binary distribution. For a more detailed description refer to chapter 2 "How to install elsA" of the document Development process tutorial.
For your first use of an executable, see the User's Starting Guide.
Please replace the vx.y strings you find below with the release number of your delivery.
Installing PythonThe elsA use requires the Python interpreter. A complete installation of Python release 2.2 or higher is necessary. The Python Web site provides download pages and instructions for installation which is staightforward (see also Development process tutorial chapter 188.8.131.52).
Workspace for installation from sourceYou must first choose a working directory, let us say Some_Work_Directory, with at least 50 MegaBytes available. You must set environment variable ELSAWKSP :
The directory tree containing elsA source code with top directory named Kernel has to be copied in the ELSAWKSP directory. For instance from a Unix tarball :
S-03 $ gunzip elsA-vx.y.src.tar.gz
S-04 $ tar xf elsA-vx.y.src.tar
Build and install
For instance, if it is in /usr/local/bin, you set the E_PPREFIX, E_PPREFIX1 and E_PYVERSION environment variables as follows :
S-07 $ export E_PPREFIX1=/usr/local/
S-08 $ export E_PYVERSION=2.2
S-09 $ export ELSAPROD=hp_r8_mpi
S-09 $ export ELSAPROD=ibm_dbg
S-12 $ make install
S-13 $ rm -rf $ELSAWKSP/Kernel
From binaryBinaries should be extracted and expanded in the same current directory, let us say MyDirectory, where a sub-directory elsA-vx.y/Dist will be created :
B-02 $ gunzip Dist-vx.y.prod.tar.gz
B-03 $ tar xf Dist-vx.y.prod.tar
TestTo use the installed version (either from source or from binary distribution) you have to set environment variables. The first one ELSAHOME will give the directory which contains the sub-directory Dist. You must also specify where the elsA Python files are located with the PYHONPATH variable. You set the ELSAPROD variable, and you may adjust your PATH to use directly the elsA executable with no path indication. If you run a shared executable, you must also set the LD_LIBRARY_PATH variable. Furthermore, if the Python installations used to create elsA executable and to run it are not the same (for instance not on the same computer), you may have to set the PYTHONHOME variable : give the path of the directory containing the sub-directory bin of the Python installation used to run elsA.
T-02 $ export PYTHONPATH=$ELSAHOME/Dist/lib/py
T-03 $ export ELSAPROD=Prod
T-04 $ export PATH=$PATH:$ELSAHOME/Dist/bin/$ELSAPROD
(T-05 $ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ELSAHOME/Dist/bin/$ELSAPROD)
(T-06 $ export PYTHONHOME=binUpDirectory)