We maintain Siril binaries in many operating systems, but in general only for the official releases, like the last one: 0.9.9. If your operating system has no binary version, you will have to build it from source yourself.

The script explains what it will do and then pauses before it does it.

Installation of Siril

Copy the following line in the terminal :

brew install siril

Updates

When a new version of Siril is available, copy this line to the terminal:

brew upgrade siril

and download the new .app file.

Enjoy!!

Installation from source

Installation from source is recommended if you want the latest features, if the past release is getting old or if you want to participate in improving Siril. Many users are reporting tweaks they would like, and we often implement them rapidly, so that would be one way to benefit from them. The other way is to use the Ubuntu PPA repository, which is updated with intermediate versions more often.

The sources are stored on a git repository, you can download them with this command the first time:

And update it the following times by typing git pull in the base directory.

Below is a list of dependencies. Siril relies on the autotools compilation configuration system and once the source has been downloaded and the prerequisites have been installed, the general way to build it is as such:

./autogen.sh
make
make install

possibly with superuser privileges.

You may want to pass specific options to the compiler, for example like that if you want optimisation and installation in /opt instead of the default /usr/local:

CFLAGS='-mtune=native -O2' ./autogen.sh --prefix=/opt

To launch Siril, the command name is siril.

Dependencies

Siril depends on a number of libraries, most of which should be available in your operating system if it is recent enough. The names of the packages specific to operating systems are listed in each section below. Mandatory dependencies are:

Note: even if Siril 0.9.9 can run in console, it is still always linked against the graphical libraries. So you still need GTK and X11 or wayland client to compile and run it.

Optional dependencies are:

libraw, libtiff, libjpeg, libpng for RAW, TIFF, JPE, PNG and images import and export. The libraries are detected at compilation-time.

FFMS2 for film native support as image sequences. It also allows frames to be extracted from many kinds of film, for other purposes than astronomy. Versions < 2.20 have an annoying bug. It is recommanded to install the last version.

Build dependencies

To install from source, you will have to install the base development packages:

autoconf, automake, libtool, intltool, pkg-tools, make, gcc, g++

You'll probably want git or subversion too, to download the latest version on the source repository. The compilers gcc and g++ from this list can be replaced by clang and clang++ (we use them for development), probably others as well.

Installing on Debian

For a desktop system, the next stable is probably the better choice, called Debian testing, currently version 10 with codename Buster. Otherwise, Siril should still work with Debian 8 Jessie and 9 Stretch. You may want to build a .deb package instead of using a non-packaged version, in that case see this help. In particular, to install dependencies, you can use the command:

Note that libtiff5 is incompatible with OpenCV in debian 7, in that case you need to install libtiff4 instead. And in debian 8, libjpeg8-dev has been replaced by libjpeg62-turbo-dev, which is also installed by libtiff5-dev.

Installing on Ubuntu & Linux Mint

A list of dependencies has been reported, for building the executable from source. Use the following command to install all of them:

The only package not available as binary is ffms2, for film files handling, you will need to compile it from source.

Compilation and the software are working fine with the default clang (cc) compiler. As clang 3.8 appeared in FreeBSD 10 with OpenMP support (clang38 in pkg), Siril can be compiled with it using the following configure command:

It is also possible to install gcc 4.8 or gcc 5 in FreeBSD. Make sure to link with the OS official compiler however, cc or c++ and not gcc or g++, otherwise the generated binary will be incorrect. That's also why the -lgomp is required to link it: