Checkout the repositories


For production systems only use the official releases from SeisComP 1, gempa GmbH 2 or compile from the corresponding release tags in this repository.

The SeisComP software collection is distributed among several repositories. For more information about compilation and build configuration head over to Github 3.

To checkout all repositories to build a complete SeisComP distribution the following script can be used:


if [ $# -eq 0 ]
    echo "$0 <target-directory>"
    exit 1


echo "Cloning base repository into $1"
git clone $repo_path/seiscomp.git $1

echo "Cloning base components"
cd $1/src/base
git clone $repo_path/seedlink.git
git clone $repo_path/common.git
git clone $repo_path/main.git
git clone $repo_path/extras.git

echo "Cloning external base components"
git clone $repo_path/contrib-gns.git
git clone $repo_path/contrib-ipgp.git
git clone $repo_path/contrib-sed.git

echo "Done"

cd ../../

echo "If you want to use 'mu', call 'mu register --recursive'"
echo "To initialize the build, run 'make'."

Compiling SeisComP from source code

To build from source you will need to clone from one or more repositories (see above).

Before building, install all the dependencies, as described below in Dependencies.

The easiest way to compile SeisComP is to use the Makefile file provided which creates a build directory inside the source tree.

Perform the following steps:

  • Clone all required repositories (see above)

  • Run make

  • Configure the build

  • Press ‘c’ as long as ‘g’ appears

  • Press ‘g’ to generate the Makefiles

  • Enter the build directory and run make install

By default all files are installed under $HOME/seiscomp. This location can be changed with cmake or with its front end ccmake.

Basically the build directory can live anywhere. The following steps create a build directory, configure the build and start it:

$ mkdir sc-build
$ cd sc-build
$ ccmake /path/to/sc-src
# Configure with ccmake
$ make install


To compile the sources the following development packages are required (Debian/Ubuntu package names):

  • g++

  • git

  • cmake + cmake-gui

  • libboost

  • libxml2-dev

  • flex

  • libfl-dev

  • libssl-dev

  • crypto-dev

  • python-dev (optional)

  • python-numpy (optional)

  • libqt4-dev (optional)

  • qtbase5-dev (optional)

  • libmysqlclient-dev (optional)

  • libpq-dev (optional)

  • libsqlite3-dev (optional)

  • ncurses-dev (optional)

The Python development libraries are required if Python wrappers should be compiled which is the default configuration. The development files must match the used Python interpreter of the system. If the system uses Python3 then Python3 development files must be present in exactly the same version as the used Python3 interpreter. The same holds for Python2.

Python-numpy is required if Numpy support is enable which is also the default configuration.