Difference between revisions of "Building FlightGear - Debian"

From FlightGear wiki
Jump to navigation Jump to search
m (Add libglew-dev as dependency)
Line 22: Line 22:
  su -c "apt-get install  \
  su -c "apt-get install  \
   freeglut3-dev  libboost-dev      libcurl4-openssl-dev  libdbus-1-dev \
   freeglut3-dev  libboost-dev      libcurl4-openssl-dev  libdbus-1-dev \
   libfltk1.3-dev  libgtkglext1-dev libjpeg62-turbo-dev   libopenal-dev \
   libfltk1.3-dev  libglew-dev      libgtkglext1-dev     libjpeg62-turbo-dev \
  libopenscenegraph-dev             libqt5opengl5-dev     librsvg2-dev \
  libopenal-dev   libopenscenegraph-dev                   libqt5opengl5-dev \
   libxml2-dev     qt5-default"
  librsvg2-dev    libxml2-dev       qt5-default"
: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".
: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".

Revision as of 15:38, 12 February 2017

HowTo build FlightGear stable (2016.4) or bleeding edge development version, hereinafter simply called next, on Debian GNU/Linux Stable (Jessie). Users of Testing or Unstable at least have to change package names (version numbering) accordingly.
Instructions also apply on Devuan GNU/Linux Jessie (Beta).

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 sed subversion"

su -c "apt-get install  \
  freeglut3-dev   libboost-dev      libcurl4-openssl-dev  libdbus-1-dev \
  libfltk1.3-dev  libglew-dev       libgtkglext1-dev      libjpeg62-turbo-dev \
  libopenal-dev   libopenscenegraph-dev                   libqt5opengl5-dev \
  librsvg2-dev    libxml2-dev       qt5-default"
If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".
If "libjpeg62-turbo-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 these are "libplib-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-2016.4 or $HOME/FG-2016.4. 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 && make install commands. We'll use $FG_INSTALL_DIR as a placeholder for this directory.
Another placeholder will be $FG_SRC_DIR, 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 FG_INSTALL_DIR=$HOME/FG-2016.4 && mkdir $FG_INSTALL_DIR
export FG_SRC_DIR=$HOME/src && mkdir $FG_SRC_DIR

Have in mind that the data is a relatively large download (GIT about 2.3 GiB (required disk space 4 GiB) / 2016.4 about 1.6 GiB). 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 laymen section.

For more/advanced cmake options and SimGear's and FlightGear's optional features see the cmake article.

Zeichen 144 icon.png Do not mix instructions for 2016.4 and next! Not even for fgdata, mixing versions will almost certainly break the installation.


2016.4 and next:
Latest SVN is required.

svn co https://svn.code.sf.net/p/plib/code/trunk plib.svn
cd plib.svn
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
./configure --prefix=$FG_INSTALL_DIR
make -j2 && make install


2016.4 and next:

git clone git://git.code.sf.net/p/flightgear/simgear simgear.git

2016.4 only:

cd simgear.git
git checkout release/2016.4

2016.4 and next:

mkdir $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
make -j2 && make install

FlightGear source

2016.4 and next:

git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git

2016.4 only:

cd flightgear.git
git checkout release/2016.4

2016.4 and next:

mkdir $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
make -j2 && make install

FlightGear data

2016.4 only:

wget http://sourceforge.net/projects/flightgear/files/release-2016.4/FlightGear-2016.4.2-data.tar.bz2/download -O FlightGear-2016.4.2-data.tar.bz2
tar xjf FlightGear-2016.4.2-data.tar.bz2

next only:

git clone git://git.code.sf.net/p/flightgear/fgdata fgdata

Trial run and finishing process

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

$FG_INSTALL_DIR/bin/fgfs --launcher
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 $FG_INSTALL_DIR and $FG_SRC_DIR 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 $FG_INSTALL_DIR/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 or check out another launcher.

Optional Software

Zeichen 101 icon.png Some of the below instructions 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"

git clone http://mapserver.flightgear.org/git/atlas
cd atlas
./configure --prefix=$FG_INSTALL_DIR --with-fgbase=$FG_INSTALL_DIR/data
make -j2 && make install
cp -R $FG_SRC_DIR/atlas/src/data/* $FG_INSTALL_DIR/data/Atlas

fgcom 3.0

There is nothing to compile because FGCom 3.0 is compiled with FlightGear.

If you can't compile FlightGear you can download a pre-built binary at http://fgcom.flightgear.org/download

fgcom (FG 2.12 and former)

For fgcom install package "libasound2-dev".

git clone http://mapserver.flightgear.org/git/fgcom fgcom.git
cd fgcom.git
git checkout -b next origin/next
mkdir $FG_SRC_DIR/build-fgcom; cd $FG_SRC_DIR/build-fgcom
make -j2 && make install

Create an .alsoftrc file as shown in FGCOM Testing.


Package "fluid" has to be installed.
2016.1 and next:

git clone git://git.code.sf.net/p/flightgear/fgrun fgrun.git

2016.1 only:

cd fgrun.git
git checkout release/2016.1

2016.1 and next:

mkdir $FG_SRC_DIR/build-fgrun; cd $FG_SRC_DIR/build-fgrun
make -j2 && make install

Execute it:



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 packag "wx2.8-headers" (at least, maybe even more than just that one. Please report!

git clone git://mapserver.flightgear.org/taxidraw
cd taxidraw
./configure --prefix=$FG_INSTALL_DIR
make -j2 && make install


Automatic Installation

link If you are familiar with "download_and_compile.sh" script from Brisa you can donwload this script: http://clement.delhamaide.free.fr/download_and_compile_tg.sh 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 terragear_download_and_compile.sh -j 2 ALL
Need some help?

Look at forum topics: http://forum.flightgear.org/viewtopic.php?f=20&t=14849

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 next 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.

wget https://gforge.inria.fr/frs/download.php/31174/CGAL-4.0.2.tar.bz2
tar xjf CGAL-4.0.2.tar.bz2
mkdir $FG_SRC_DIR/build-cgal; cd $FG_SRC_DIR/build-cgal
make -j2 && make install

Compile TerraGear:

git clone git://git.code.sf.net/p/flightgear/terragear terragear.git
cd terragear.git
git checkout scenery/ws2.0
mkdir $FG_SRC_DIR/build-tg; cd $FG_SRC_DIR/build-tg
make -j2 && make 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.