Table Of Contents

Previous topic

About

Next topic

User Documentation

Download

GammaLib can be obtained in form of releases or directly from the git development repository. Prefer a release if you intend using GammaLib for production (and publications). Clone the code from git if you need the most recent code that implements new features and corrects known bugs.

Releases

The latest GammaLib release is gammalib-1.3.0 (7 Juin 2017).

To download an older release, click on the corresponding release number: 1.2.0 1.1.0 1.0.1 1.0.0 0.11.0 0.10.0 0.9.1 0.9.0 0.8.1 0.8.0 0.7.0 0.6.2 0.6.1 0.5.0 0.4.2 0.4.11 0.4.10 0.4.9 0.4.7

Development release

The current GammaLib development release is gammalib-1.4.0.dev1. This release reflects the status of the current devel branch of the GammaLib git repository.

Git repository

To clone the gammalib source code, type

$ git clone https://cta-gitlab.irap.omp.eu/gammalib/gammalib.git

This will create a gammalib directory under the current working directory that will contain the gammalib source code. In case that the cloning does not work you may try adding

$ export GIT_SSL_NO_VERIFY=true

or

$ git config --global http.sslverify "false"

before retrieving the code. Before you will be able to compile the code you need to generate the configuration file using the autogen.sh script. Also make sure that you’re actually on the devel branch of the git repository. GammaLib can be compiled and configured using the following command sequence (the code will be installed into the /usr/local/gamma directory):

$ cd gammalib
$ git checkout devel
$ ./autogen.sh
$ ./configure
$ make
$ make check
$ sudo make install
$ export GAMMALIB=/usr/local/gamma
$ source $GAMMALIB/bin/gammalib-init.sh

Please read the Installation section if you need more information on how to install GammaLib.

Note

You need swig on your system to build the Python wrappers when you get the code from Git. Python wrappers are not stored in the Git repository but are built using swig from interface files located in the pyext folder. However, you do not need swig when fetching a release as the Python wrappers are bundled with the release tarballs.