Building FlightGear - Debian

From FlightGear wiki
Revision as of 07:31, 15 September 2013 by BotFlightGear (Talk | contribs) (Robot: Automated text replacement (- +

Jump to: navigation, search

HowTo build FlightGear 2.10.0 or bleeding edge development version, hereinafter simply called GIT, on GNU/Linux Debian Stable/Squeeze. Users of Oldstable, Testing/Wheezy or Unstable at least have to change package names (version numbering) accordingly.

The meaning of this article is to be a short, checklist like, overview of the specific steps to compile FlightGear and components on Debian. For more detailed information please refer to the main article Building FlightGear on Linux.

If you don't want to get your hands dirty, have a look at Scripted Compilation on Linux Debian/Ubuntu.

Zeichen 144 icon.png For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the here used commands may cause trouble.

Requirements and Preparations

A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

su -c "apt-get install automake cmake g++ gcc git make subversion"
Additionally install "fluid" if you intend to use fgadmin.


Command for Squeeze, users of other releases are advised to check package versions:

su -c "apt-get install  \
  freeglut3-dev  libboost-dev   libcurl4-openssl-dev  libgtkglext1-dev \
  libjpeg62-dev  libopenal-dev  librsvg2-dev          libsvn-dev \
  libxml2-dev    libxrandr-dev"
If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".
If "libjpeg62-dev" breaks package dependencies, just install one of the other versions' -dev.
Add "libudev-dev" if you need FG's feature -D EVENT_INPUT=ON.
Zeichen 144 icon.png During installation development packages of libraries which are going to be compiled must not be installed. They can safely be re-installed after compilation. Namely here these might be "libplib-dev", "libfltk1.1-dev", "libopenscenegraph-dev" and "simgear-dev".

Build and install

Because we are going to install versions different to the ones in the Debian repositories, it is recommended to install FlightGear in a place independent of the base system, such as /usr/local/FG-2.10.0 or $HOME/FG-2.10.0. This way also has the advantage of easily managing several FlightGear versions, even with different versions of OpenSceneGraph and/or plib, simply by altering the installation prefix. I suggest to make this directory writeable by the user so there is no need to become root for the make -j2 install commands. We'll use $prefix as a placeholder for this directory.
Another placeholder will be $srcdir, it stands for the absolute path to the directory which is supposed to keep the folders of the various source codes. So, in the instructions below, you have to replace these with the local paths or even export them (in every terminal you're using them) for the process:

export prefix=$HOME/FG-2.10.0 && mkdir $prefix
export srcdir=$HOME/src && mkdir $srcdir

Have in mind that the data is a relatively large download (GIT about 5 GB and 2.10.0 650 MB). So, to save some time, it is a good idea to fetch it while building the sources.
For some basic info on git commands for FlightGear users we have a git for dummies section.
To have a build with debugging symbols add -D CMAKE_BUILD_TYPE="RelWithDebInfo" to SimGear's and FlightGear's cmake options.


FLTK only is required for fgadmin, which is content with libfltk-1.1, and fgrun, which minimum is libfltk-1.3.
Wheezy: Just install package "libfltk1.3-dev" if you're planning to use either of them.
Squeeze: For fgadmin just install package "libfltk1.1-dev". To compile fgrun, too, build and install FLTK-1.3 instead:

cd $srcdir
tar xzf fltk-1.3.2-source.tar.gz
cd fltk-1.3.2
./configure --enable-shared --prefix=$prefix 
make -j2 install


2.10.0 and GIT: Latest SVN is required.

cd $srcdir
svn co plib
cd plib
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
./configure --prefix=$prefix
make -j2 install


For 2.10.0 on Wheezy skip that step and install package "libopenscenegraph-dev" instead.
GIT users, especially developers, most likely want to use the latest DeveloperRelease or even bleeding edge code here.
2.10.0 and GIT:

cd $srcdir
svn co OpenSceneGraph
mkdir build-osg; cd build-osg
cmake -D CMAKE_BUILD_TYPE="Release" -DLIB_POSTFIX="" \
      -D CMAKE_INSTALL_PREFIX:PATH="$prefix" $srcdir/OpenSceneGraph
make -j2 install


2.10.0 and GIT:

cd $srcdir
git clone git://

2.10.0 only:

cd simgear
git checkout -b 2.10.0 origin/release/2.10.0

2.10.0 and GIT:

mkdir $srcdir/build-sg; cd $srcdir/build-sg
cmake -D CMAKE_INSTALL_PREFIX:PATH="$prefix" $srcdir/simgear
make -j2 install

FlightGear source

2.10.0 and GIT:

cd $srcdir
git clone git://

2.10.0 only:

cd flightgear
git checkout -b 2.10.0 origin/release/2.10.0

2.10.0 and GIT:

mkdir $srcdir/build-fg; cd $srcdir/build-fg
cmake -D CMAKE_INSTALL_PREFIX:PATH="$prefix" $srcdir/flightgear
make -j2 install

FlightGear data

2.10.0 only: Please have a look at the mirror list for a server close to your location.

cd $prefix
tar xjf FlightGear-data-2.10.0.tar.bz2

GIT only: For slow/unstable internet connections it is recommended to download the fgdata.bundle instead of cloning the data.

cd $prefix
git clone git:// data

Trial run and finishing process

When all the builds are done and the data download has finished it is time for a test run:

export LD_LIBRARY_PATH=$prefix/lib/:$LD_LIBRARY_PATH
$prefix/bin/fgfs --fg-root=$prefix/data
The fgfs binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does. You might want to add this line to your $HOME/.bashrc to have this as a persistent setting (may cause problems, if one has installed more than one version of FlightGear!).
Have in mind, the $prefix and $srcdir variables are available for this session only. For future use of these lines, replace them by the real paths.

To avoid the need to give the path to the fgfs command each time, you might consider to create a symlink at a place that is listed in $PATH:

ln -s $prefix/bin/fgfs $HOME/bin/fgfs

For the future, if you want to start FlightGear from command line have a look at fgfsrc, if you prefer a graphical user interface continue with compiling fgrun.

Optional Software

Zeichen 101 icon.png Some of the below instructions possibly are not up to date. Please feel free to revise them.

Feel free to add the commands to install other FlightGear related projects.


One more Package has to be installed: "libglew1.5-dev"

cd $srcdir
git clone
cd atlas
./configure --prefix=$prefix --with-fgbase=$prefix/data
make -j2 install
cp -R $srcdir/atlas/src/data/* $prefix/data/Atlas


For fgcom install package "libasound2-dev".

cd $srcdir
svn co fgcom
cd fgcom/src
make -j2 install_BIN=$prefix/bin INSTALL_DIR=$prefix/fgcom \
   PLIB_PREFIX=$prefix [OPENAL_PREFIX=$prefix] install

Create an .alsoftrc file as shown in FGCOM Testing.


To build fgrun libfltk1.3 is required, see libfltk above.
2.10.0 and GIT:

cd $srcdir
git clone git://

2.10.0 only:

cd fgrun
git checkout -b 1.7.0 origin/release/1.7.0

2.10.0 and GIT:

mkdir $srcdir/build-fgrun; cd $srcdir/build-fgrun
cmake -D CMAKE_INSTALL_PREFIX:PATH="$prefix" $srcdir/fgrun
make -j2 install

2.10.0 and GIT:

export LD_LIBRARY_PATH=$prefix/lib/:$LD_LIBRARY_PATH


Zeichen 101 icon.png Obsolete for airport creation, use WorldEditor instead. It is still useful for working on ground networks.
To compile TaxiDraw we need to install some more packages:

  • either "libcurl4-gnutls-dev" or "libcurl4-openssl-dev" for curl.h
  • "wx2.8-headers" (at least, maybe even more than just that one. Please report!
su -c "aptitude install [libcurl4-gnutls-dev|libcurl4-openssl-dev]"
cd $srcdir
git clone git://
cd taxidraw
./configure --prefix=$prefix
make -j2 install


Automatic Installation

link If you are familiar with "" script from Brisa you can donwload this script: This script is similar to Brisa's one (only usable for Debian/Mint/Ubuntu). This script installs TerraGear (latest version) and terragear-gui.

How to use it?
sh -j 2 ALL
Need some help?

Look at forum topics :

After success installation you can exectute this command line in the terragear/bin directory in order to display every --help for each binary files:

cd terragear/bin && for i in `ls`; do echo ""; echo "################# "$i" ##############"; ./$i --help; done

Basic Installation

To resolve some of the dependencies of TerraGear the GIT sections of steps plib, OpenSceneGraph and SimGear have to be done first. Additionally some packages and their dependencies have to be installed:

su -c "apt-get install \
  libgdal-dev libtiff4-dev libboost-signals-dev libboost-system-dev libboost-thread-dev"

Squeeze users have to compile the CGAL dependency. On Wheezy just install package "libcgal-dev" instead.

cd $srcdir
tar xjf CGAL-4.0.2.tar.bz2
mkdir $srcdir/build-cgal; cd $srcdir/build-cgal
cmake -D CMAKE_INSTALL_PREFIX:PATH="$prefix" $srcdir/CGAL-4.0.2
make -j2 install

Compile TerraGear:

cd $srcdir
git clone git://
mkdir $srcdir/build-tg; cd $srcdir/build-tg
cmake -D CMAKE_INSTALL_PREFIX:PATH="$prefix" $srcdir/terragear
make -j2 install

WorldEditor (WED)

Because this is the same for all Linux distributions the instructions are not listed here separately. Please refer to our lead WED article.