Compilation on Linux
Each time Stellarium is released, the sourcecode is released in Sourceforge's packaging system. Building sourcecode that is released in this way should give you a working copy of Stellarium which is functionally identical to the binaries for that release.
It is also possible to get the "in development" sourcecode using Subversion. This may contain new features which have been implemented since the last release of Stellarium, so it's often more fun. Warning: Subversion versions of the Stellarium sourcecode are work in progress, and as such may produce an unstable program, may not work at all, or may not even compile.
If you're new to the command line, you might also find this page interesting.
First make sure all build dependencies are installed on your system.
We now use CMake instead of automake/autoconf. A common problem is that you don't have a recent enough version of CMake. Make sure you have the version specified in the build dependencies page (the error which is seen if you have an old version of CMake is something to do with curl).
If you have both QT version 4 development tools and QT version 3 development tools installed on your system, make sure the commands for moc, uic and so on point at the QT4 versions. Ubuntu/Debian users might want to use this script to swap between them.
Extract the tarball containing the source code. Open a terminal and cd to the directory where you wish to build Stellarium. Save the tarball to that directory and do this command in a terminal (if you prefer, you might use arK or some other graphical archive tool):
$ tar zxf stellarium-0.10.0.tgz
You should now have a directory stellarium-0.10.0 with the source code in it.
- In a terminal and change into the source directory:
- Make the build directory and change into it
mkdir -p builds/unix cd builds/unix
- Configure the build using CMake:
By default this will configure Stellarium to be installed in the /usr/local area. If you want another location, use this option to cmake:
cmake -DCMAKE_INSTALL_PREFIX=/opt/mylocation ../..
- Run make
- Install the program (as root if necessary)
That's it. You should now have Stellarium built and installed. Build takes a few minutes on a P4 1.7Ghz/512 Mb.
Enabling Sound Support
Stellarium's sound support is a compile time option. To use sound in Stellarium you need to have a version of QT which supports the Phonon audio system. You also need a recent version of CMake.
Sound support is controlled by the CMake option ENABLE_SOUND. You can change this setting using ccmake, by editing the CMakeCache.txt file, or by supplying the -DENABLE_SOUND=1 option when youo first run CMake.
Subversion (development) version
First, make sure you have all the Build Dependencies installed.
Getting the sourcecode
Execute these commands:
svn co https://stellarium.svn.sourceforge.net/svnroot/stellarium/trunk/stellarium stellarium
This will create the directory stellarium which contains the source code.
Building the source
- Change into the stellarium directory which was created by the svn command above
- Make a builds/unix directory and change into it:
mkdir -p builds/unix cd builds/unix
By default this will configure Stellarium to be installed in the /usr/local/ area. If this is OK, run CMake like this:
or, if you would prefer to specify an alternative installation prefix, select it like this
cmake -DCMAKE_INSTALL_PREFIX=/opt/mylocation/ ../..
- Now build using make:
- To run Stellarium from the source tree, change back to the root of the source tree, and call the binary like this:
cd ../.. builds/unix/src/stellarium
- If you want to install the program, from the builds/unix directory enter this command (as root if necessary):
If you have previously build the SVN code, but want to see what changes have been made since you did that, just cd into the stellarium directory and use the command:
This will download just the changes which were made since you last retrieved files from the repository. Often, all that will be required is to build from the make stage, but if there are new files you will need to build from the CMake stage.
Current Build Issues
Note that the development code is a work in progress, and as such, please don't expect it to build straight off the bat. Often it will be fine, but sometimes the build will be broken.