You are here: Home / Getting PIPS

Getting PIPS

This is the starting point of the documentation. It describes the various way of getting PIPS up and running on your system.

Currently there are several ways of getting PIPS. In all cases you should note that the source code is not bullet-proof and large (approx 500,000 lines of C code plus other languages).

Install from Subversion (SVN)

As a continuously evolving framework, PIPS does not have point releases, thus the preferred way of installing an up-to-date version is to use the PIPS Subversion (SVN) repository.

Standard method (Recommended)

A shell script, setup_pips.sh, can take care of checking out the code from SVN and building PIPS.

Please refer to the detailed instructions.

Autotools method

Another shell script, get-pips4u.sh, does the same job but is based on autotools.

Note: this is currently the preferred method for platforms such as FreeBSD or MacOS X. It of course works very well with Linux platforms.

You can check if your system is supported by pips-autotool on http://ridee.enstb.org:8010/waterfall

Please refer to the detailed instructions.

The Par4All way of life

Since Par4All is an environment that also packages PIPS among other components, the Par4All installation methods also install PIPS.

Have a look to the Par4All site for more information.

Binary Debian Packages

Unofficial binary packages for Debian GNU/Linux unstable for amd64 and i386 are built on a regular basis.

They are based on svn snapshots, NOT releases. They can be used it to install PIPS in your environment, or simply as a convenient means of getting the build dependencies.

Please check http://ridee.enstb.org/debian/info.html for more information.

Document Actions