How to install OpenTURNS with a development version
This guide is only for developers or advanced users who want to use a development version.
Download
To use a development version, you must have Subversion to retrieve a version.
To learn more about the use of version control system (svn) you can refer to the version control system page
If you know what you are doing, you can checkout the development's trunk.
svn checkout https://svn.openturns.org/openturns/trunk openturns-trunk
We ensure that the trunk is quite stable though not fully debugged. So it should compile and pass the checks without efforts. That's all, so don't ask for bug correction on the trunk.
In particular, we do not encourage anyone to pick up a development version and distribute it in any way.
Also, you can pick up a tagged version. (i.e. 0.15) :
svn checkout https://svn.openturns.org/openturns/tags/openturns-0.15
Dependencies
To build your OpenTURNS platform, you need some additional libraries, headers (development files) and tools. Of course, you can use your favorite package-manager to download and install these requirements.
- binutils
- automake (>=1.10)
- autoconf (tested with 2.60, 2.61)
- libtool (tested with 1.5.22 and 2.2)
- gcc (>= 3.3.6 except 4.0.x series, tested with 4.1.2)
- gfortran (>= 3.3.6 except 4.0.x series, tested with 3.4.6)
- python (2.4.x)
- R (>= 2.0)
- libxml2 (>= 2.6.27)
- SWIG (>= 1.3.35)
- lapack
- flex (>= 2.5.33)
- bison
These are the package names on each distribution
| package | Debian/Ubuntu | Mandriva | OpenSUSE | Fedora | Red Hat |
| latex | texlive-latex | texlive-latex | tetex-latex | tex(latex) | tetex-latex |
| c++ | gcc | gcc-c++ | gcc-c++ | gcc-c++ | gcc-c++ |
| fortran | gfortran | gcc-gfortran | gcc-gfortran | gcc-fortran | gcc-gfortran |
| R | r-base-core | R-base | R-base | R-core | R-core |
| R (development) | r-base-dev | R-base | R-base | R-devel | R-devel |
| xml | libxml2 | libxml2 | libxml2 | libxml2 | libxml2 |
| xml (development) | libxml2-dev | libxml2-devel | libxml2-devel | libxml2-devel | libxml2-devel |
| lapack | liblapack3gf | lib(64)lapack3 | lapack | lapack | lapack |
| lapack (development) | liblapack-dev | lapack-devel | lapack | lapack-devel | lapack-devel blas-devel |
| python | python | python | python-base | python | python |
| python (development) | python-dev | python-devel | python-devel | python-devel | python-devel |
| python qt | python-qt4 | python-qt4 | python-qt4 | !PyQt4 | |
| rpy2 | python-rpy2 | python-rpy2 | rpy | ||
| tbb | libtbb2 | tbb | tbb | tbb | tbb |
| tbb (development) | libtbb-dev | tbb-devel | tbb-devel | tbb-devel | tbb-devel |
Generic instructions
Pre installation
To allow OpenTURNS to communicate with R, you need to install the provided R package named rotRPackage:
# R CMD INSTALL utils/rotRPackage_1.4.4.tar.gz
Then you should be able to load it in R.
R --vanilla <<<'library(rotRPackage)'
As you can see with dependencies, OpenTURNS project use autotools and gcc suite to configure and build the sources.
Configure
./bootstrap mkdir build cd build ../configure --prefix=$PWD/install --disable-static
Or, faster, using CMake:
mkdir build cd build cmake .. -DCMAKE_INSTALL_PREFIX=$PWD/install
Build & install
make make check make install make installcheck
Try it !
- Set the python path
export PYTHONPATH=$PWD/install/lib/python2.6/site-packages
- Launch python interpreter
python -c "import openturns as ot; u=ot.Normal(); print u"
Python 2.6.2 (r262:71600, Aug 21 2009, 12:23:57) [GCC 4.4.1 20090818 (Red Hat 4.4.1-6)] on linux2 Type "help", "copyright", "credits" or "license" for more information. Welcome to OpenTURNS version 0.15 class=NumericalPoint name=Unnamed dimension=1 values=[0.608202]