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.

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.12.3) :

# svn checkout https://svn.openturns.org/openturns/tags/openturns-0.12.3 openturns-0.12.3

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)
• g77/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)
• boost
• lapack
• Qt (3.3.x)
• flex (>= 2.5.33)
• bison

Specific instructions

If you have one of theses distributions, you can follow the associated specific How-To :

• GNU/Debian 4.0 (Etch);
• Ubuntu/Kubuntu 7.04 (Feisty);
• Fedora 12 (Constantine);

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

As you can see with dependencies, OpenTURNS project use autotools and gcc suite to configure and build the sources.

Configure

./bootstrap
./configure

Note: On the one hand, swig is needed to install a development version. On the other hand, the configure script does not raise any errors if swig is not detected or if its version is obsolete (because swig is not needed to install a user version). That means that an error at the compilation time of a development version may occur, even if the configure script did not fail. In that particular case, you should check the detection of a compatible version of swig (you can use the '--with-swig' option to tell the configure script where a compatible version of swig is located).

Build & install

make
make check
make install
make installcheck

Note

To learn more about the use of version control system (svn) you can refer to the version control system page