Hi fellow wiki editors!

To help newly registered users get more familiar with the wiki (and maybe older users too) there is now a {{Welcome to the wiki}} template. Have a look at it and feel free to add it to new users discussion pages (and perhaps your own).

I have tried to keep the template short, but meaningful. /Johan G

Difference between revisions of "Building FlightGear - Debian"

From FlightGear wiki
Jump to: navigation, search
m
(1st review for FG 2.6.0)
Line 1: Line 1:
HowTo build FlightGear 2.4.0 or bleeding edge development version, hereinafter simply called ''GIT'', on GNU/Linux Debian '''Stable''' 6.x (Squeeze) and '''Testing''' (Wheezy).
+
[[File:Zeichen_101_icon.png|42px]] Article is under construction though only minor details are missing, it should work in ''most'' cases.
  
Even on Debian '''Oldstable''' 5.x (Lenny) this guide will work for both 2.4.0 and GIT. At least until the dependencies of the GIT version change.
+
[[User:Flughund|Flughund]] 21:02, 28 February 2012 (EST)
 +
----
  
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_-_Linux | Building FlightGear on Linux]].
+
 
 +
HowTo build FlightGear [[Changelog_2.6.0|2.6.0]] or bleeding edge development version, hereinafter simply called ''[[GIT]]'', on GNU/Linux [http://www.debian.org/ Debian] '''Stable''' 6.x (Squeeze) and '''Testing''' (Wheezy).
 +
 
 +
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_-_Linux | Building FlightGear on Linux]].
  
 
If you don't want to get your hands dirty, have a look at [[Scripted Compilation on Linux Debian/Ubuntu]].
 
If you don't want to get your hands dirty, have a look at [[Scripted Compilation on Linux Debian/Ubuntu]].
Line 9: Line 13:
  
 
== Requirements and Preparations ==
 
== Requirements and Preparations ==
You need an OpenGL capable graphics card including a proper installed driver supporting direct rendering.<br />
+
You need an [[OpenGL]] capable graphics card including a proper installed driver supporting direct rendering.<br />
 
Also a bunch of packages (as well as some of their dependencies) are required to compile FlightGear:
 
Also a bunch of packages (as well as some of their dependencies) are required to compile FlightGear:
* gcc, g++, make, automake, pkg-config
 
* mawk (or gawk)
 
* cmake (min. version 2.6.0-5)
 
* git, subversion, wget
 
* libgl1-mesa-dev, libxrandr-dev
 
* libxi-dev, libxmu-dev, libxext-dev
 
* libopenal-dev (for Lenny see [[#libopenal|libopenal]]), libalut-dev
 
* libjpeg62-dev, libtiff4-dev, libpng12-dev
 
* libboost1.37-dev (min 1.37, 1.40 available for Lenny on backports.debian.org)
 
  
During installation packages ''simgear-dev'' and ''openscenegraph-dev'' '''must not''' be installed. They can safely be re-installed after compilation.
+
; Tools
 +
su -c "apt-get install automake bzip2 cmake g++ gcc git make subversion tar"
 +
: cmake: At least version 2.6.0-5 required!
 +
 
 +
; Libs
 +
su -c "apt-get install libc6-dev libgl1-mesa-dev freeglut3-dev libalut-dev \
 +
    libboost1.42-dev libsvn-dev libxml2-dev libcurl4-openssl-dev libgtkglext1-dev \
 +
    libopenal-dev libpng12-dev librsvg2-dev libtiff4-dev libfltk1.1-dev"
 +
: If you prefer you might replace libcurl4-openssl-dev by libcurl4-gnutls-dev.
 +
<!--
 +
osg: libxml2-dev libcurl4-gnutls-dev/libcurl4-openssl-dev libgtkglext1-dev libopenal-dev libpng12-dev librsvg2-dev libtiff4-dev
 +
sg: libalut-dev libboost1.42-dev libsvn-dev
 +
fg: freeglut3-dev (libfltk1.1-dev, option für fgadmin; udev?)
 +
-->
 +
 
 +
: [[File:Zeichen_144_icon.png|21px]]During installation packages ''simgear-dev'' and ''openscenegraph-dev'' must not be installed. They can safely be re-installed after compilation.
  
  
 
== Build and install ==
 
== Build and install ==
Because we are going to install versions different to the ones in the repositories I recommend to install FG-2.4.0 and/or GIT in a place independent of the base system such as /usr/local/FG-2.4.0, /opt/FG-2.4.0 or in a subdirectory of your $HOME. I suggest to make it writeable by the user so there is no need to become root for the <code>make install</code> commands. I'll use <code>$prefix</code> as a placeholder for this directory. <br />
+
Because we are going to install versions different to the ones in the repositories, it is recommended to install FlightGear in a place independent of the base system, such as <code>/usr/local/FG-2.6.0</code> or <code>$HOME/FG-2.6.0</code>. This way also has the advantage of easily managing several FlightGear versions, even with different versions of OpenSceneGraph and/or plib. I suggest to make this directory writeable by the user so there is no need to become root for the <code>make install</code> commands. We'll use <code>$prefix</code> as a placeholder for this directory. <br />
Another one will be <code>$srcdir</code>, it stands for the absolute path to the directory which is supposed to keep the folders of the various source codes. So, in the following instructions, you have to replace these with the local paths or even <code>export</code> them during the process.
+
Another placeholder will be <code>$srcdir</code>, it stands for the absolute path to the directory which is supposed to keep the folders of the various source codes. So, in the following instructions, you have to replace these with the local paths or even <code>export</code> them during the process:
  export prefix=[path to install to]
+
  export prefix=$HOME/FG-2.6.0; mkdir $prefix
  export srcdir=[path to sources]
+
  export srcdir=$HOME/src; mkdir $srcdir
  
Have in mind that the data is a relatively large download (GIT about 3.5 GB and 2.4.0 410 MB). So, to save some time, it is a good idea to fetch it while building the sources.
+
Have in mind that the data is a relatively large download (GIT about 4.4 GB and 2.6.0 540 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|git for dummies]] section.
 
For some basic info on git commands for FlightGear users we have a [[Git#For dummies|git for dummies]] section.
Line 45: Line 55:
  
  
=== plib ===
+
=== [[plib]] ===
 +
<u>2.6.0 and GIT:</u>
 
Latest SVN is [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended], yet package plib1.8.5-dev for Squeeze does work as well.
 
Latest SVN is [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended], yet package plib1.8.5-dev for Squeeze does work as well.
 
  cd $srcdir
 
  cd $srcdir
Line 56: Line 67:
  
  
=== OpenSceneGraph ===
+
=== [[OpenSceneGraph]] ===
<u>GIT</u> users, especially developers, may want to use the latest release or even bleeding edge code here. Have in mind that, at the time of the FlightGear 2.4.0 release, there are some issues with newer versions than 2.9.10!
+
<u>GIT</u> users, especially developers, may want to use the latest release or even bleeding edge code here instead. <br />
 +
<u>2.6.0 and GIT:</u>
 
  cd $srcdir
 
  cd $srcdir
  svn co http://www.openscenegraph.org/svn/osg/OpenSceneGraph/tags/OpenSceneGraph-2.9.10 OpenSceneGraph
+
  svn co http://www.openscenegraph.org/svn/osg/OpenSceneGraph/tags/OpenSceneGraph-3.0.1 OpenSceneGraph
sed 's|SET(LIB_POSTFIX "64" CACHE|SET(LIB_POSTFIX "" CACHE|' -i OpenSceneGraph/CMakeLists.txt
+
 
  mkdir osg-build && cd osg-build
 
  mkdir osg-build && cd osg-build
  cmake -D CMAKE_BUILD_TYPE="Release" \
+
  cmake -D CMAKE_BUILD_TYPE="Release" -DLIB_POSTFIX="" \
 
       -D CMAKE_INSTALL_PREFIX:PATH="$prefix" $srcdir/OpenSceneGraph
 
       -D CMAKE_INSTALL_PREFIX:PATH="$prefix" $srcdir/OpenSceneGraph
 
  make install
 
  make install
  
  
=== SimGear ===
+
=== [[SimGear]] ===
<u>2.4.0 and GIT:</u>
+
<u>2.6.0 and GIT:</u>
 
  cd $srcdir
 
  cd $srcdir
 
  git clone git://mapserver.flightgear.org/simgear
 
  git clone git://mapserver.flightgear.org/simgear
  
<u>2.4.0 only:</u>
+
<u>2.6.0 only:</u>
 
  cd simgear
 
  cd simgear
  git checkout -b 2.4.0 origin/release/2.4.0
+
  git checkout -b 2.6.0 origin/release/2.6.0
./autogen.sh
+
./configure --prefix=$prefix
+
make install
+
  
<u>GIT only:</u>
+
<u>2.6.0 and GIT:</u>
  mkdir sg-build && cd sg-build
+
  mkdir $srcdir/sg-build && cd $srcdir/sg-build
 
  cmake -D CMAKE_INSTALL_PREFIX:PATH="$prefix" $srcdir/simgear
 
  cmake -D CMAKE_INSTALL_PREFIX:PATH="$prefix" $srcdir/simgear
 
  make install
 
  make install
Line 86: Line 94:
  
 
=== FlightGear source ===
 
=== FlightGear source ===
<u>2.4.0 and GIT:</u>
+
<u>2.6.0 and GIT:</u>
 
  cd $srcdir
 
  cd $srcdir
 
  git clone git://mapserver.flightgear.org/flightgear
 
  git clone git://mapserver.flightgear.org/flightgear
  
<u>2.4.0 only:</u>
+
<u>2.6.0 only:</u>
 
  cd flightgear
 
  cd flightgear
  git checkout -b 2.4.0 origin/release/2.4.0
+
  git checkout -b 2.6.0 origin/release/2.6.0
./autogen.sh
+
./configure --prefix=$prefix
+
make install
+
  
<u>GIT only:</u>
+
<u>2.6.0 and GIT:</u>
  mkdir fg-build && cd fg-build
+
  mkdir $srcdir/fg-build && cd $srcdir/fg-build
 
  cmake -D CMAKE_INSTALL_PREFIX:PATH="$prefix" $srcdir/flightgear
 
  cmake -D CMAKE_INSTALL_PREFIX:PATH="$prefix" $srcdir/flightgear
 
  make install
 
  make install
Line 104: Line 109:
  
 
=== FlightGear data ===
 
=== FlightGear data ===
<u>2.4.0 only:</u> Please have a look at the [http://flightgear.org/mirrors.html mirror list] for a server close to your location.
+
<u>2.6.0 only:</u> Please have a look at the [http://flightgear.org/mirrors.html mirror list] for a server close to your location.
 
  cd $prefix
 
  cd $prefix
  wget http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Shared/FlightGear-data-2.4.0.tar.bz2
+
  wget http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Shared/FlightGear-data-2.6.0.tar.bz2
  tar xjf FlightGear-data-2.4.0.tar.bz2
+
  tar xjf FlightGear-data-2.6.0.tar.bz2
  
 
<u>GIT only:</u>
 
<u>GIT only:</u>
 
For slow/unstable internet connections it is recommended to download the [[Git#fgdata.bundle|fgdata.bundle]] instead of cloning the data.<br />
 
For slow/unstable internet connections it is recommended to download the [[Git#fgdata.bundle|fgdata.bundle]] instead of cloning the data.<br />
FlightGear's primary git server on gitorious is known to have trouble cloning the data, the mapserver's mirror usually has no problems:
 
 
  cd $prefix
 
  cd $prefix
 
  git clone git://mapserver.flightgear.org/fgdata data
 
  git clone git://mapserver.flightgear.org/fgdata data
  
  
== Trial run ==
+
== Trial run and finishing process ==
 
When all the builds are done and the data download has finished it is time for a test run:
 
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
 
  export LD_LIBRARY_PATH=$prefix/lib/:$LD_LIBRARY_PATH
 
  $prefix/bin/fgfs --fg-root=$prefix/data
 
  $prefix/bin/fgfs --fg-root=$prefix/data
 +
Have in mind that <code>fgfs</code> need to find our self compiled libraries 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 <code>$HOME/.bashrc</code> to have this as a persistent setting.
  
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 [[#fgrun|compiling fgrun]] or check [[FGo!]]. Have in mind that <code>fgfs</code> need to find our self compiled libraries and therefore we have to tell the linker (ld) where to find them. That is what the first line here does.
+
To avoid the need to give the path to the <code>fgfs</code> command in the second line, you might consider to create a symlink to place that is listed in $PATH:
 +
ln -s $HOME/FG-2.6.0/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 [[#fgrun|compiling fgrun]] or check [[FGo!]].  
  
  
 
== Optional Software ==
 
== Optional Software ==
 +
[[File:Zeichen_101_icon.png|21px]] Many of the below instructions are most likely not up to date. Please feel free to revise them.
 +
 
Feel free to add the commands to install other FlightGear related projects.
 
Feel free to add the commands to install other FlightGear related projects.
  
=== Atlas ===
+
=== [[Atlas]] ===
 
  cd $srcdir
 
  cd $srcdir
 
  cvs -d:pserver:anonymous@atlas.cvs.sourceforge.net:/cvsroot/atlas login
 
  cvs -d:pserver:anonymous@atlas.cvs.sourceforge.net:/cvsroot/atlas login

Revision as of 22:02, 28 February 2012

Zeichen 101 icon.png Article is under construction though only minor details are missing, it should work in most cases.

Flughund 21:02, 28 February 2012 (EST)



HowTo build FlightGear 2.6.0 or bleeding edge development version, hereinafter simply called GIT, on GNU/Linux Debian Stable 6.x (Squeeze) and Testing (Wheezy).

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.


Requirements and Preparations

You need an OpenGL capable graphics card including a proper installed driver supporting direct rendering.
Also a bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

Tools
su -c "apt-get install automake bzip2 cmake g++ gcc git make subversion tar"
cmake: At least version 2.6.0-5 required!
Libs
su -c "apt-get install libc6-dev libgl1-mesa-dev freeglut3-dev libalut-dev \
   libboost1.42-dev libsvn-dev libxml2-dev libcurl4-openssl-dev libgtkglext1-dev \
   libopenal-dev libpng12-dev librsvg2-dev libtiff4-dev libfltk1.1-dev"
If you prefer you might replace libcurl4-openssl-dev by libcurl4-gnutls-dev.
Zeichen 144 icon.pngDuring installation packages simgear-dev and openscenegraph-dev must not be installed. They can safely be re-installed after compilation.


Build and install

Because we are going to install versions different to the ones in the repositories, it is recommended to install FlightGear in a place independent of the base system, such as /usr/local/FG-2.6.0 or $HOME/FG-2.6.0. This way also has the advantage of easily managing several FlightGear versions, even with different versions of OpenSceneGraph and/or plib. I suggest to make this directory writeable by the user so there is no need to become root for the make 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 following instructions, you have to replace these with the local paths or even export them during the process:

export prefix=$HOME/FG-2.6.0; mkdir $prefix
export srcdir=$HOME/src; mkdir $srcdir

Have in mind that the data is a relatively large download (GIT about 4.4 GB and 2.6.0 540 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.


libopenal

Lenny only! The libopenal-dev package in Lenny is too old for fgcom. For FlightGear it does work but not all features (like doppler) are available, so installing an up to date version is recommended anyway.

cd $srcdir
wget http://kcat.strangesoft.net/openal-releases/openal-soft-1.11.753.tar.bz2
tar xjf openal-soft-1.11.753.tar.bz2
cd openal-soft-1.11.753/build
cmake  -D CMAKE_INSTALL_PREFIX:PATH="$prefix" ..
make install


plib

2.6.0 and GIT: Latest SVN is recommended, yet package plib1.8.5-dev for Squeeze does work as well.

cd $srcdir
svn co https://plib.svn.sourceforge.net/svnroot/plib/trunk plib
cd plib
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
./autogen.sh
./configure --prefix=$prefix
make install


OpenSceneGraph

GIT users, especially developers, may want to use the latest release or even bleeding edge code here instead.
2.6.0 and GIT:

cd $srcdir
svn co http://www.openscenegraph.org/svn/osg/OpenSceneGraph/tags/OpenSceneGraph-3.0.1 OpenSceneGraph
mkdir osg-build && cd osg-build
cmake -D CMAKE_BUILD_TYPE="Release" -DLIB_POSTFIX="" \
      -D CMAKE_INSTALL_PREFIX:PATH="$prefix" $srcdir/OpenSceneGraph
make install


SimGear

2.6.0 and GIT:

cd $srcdir
git clone git://mapserver.flightgear.org/simgear

2.6.0 only:

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

2.6.0 and GIT:

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


FlightGear source

2.6.0 and GIT:

cd $srcdir
git clone git://mapserver.flightgear.org/flightgear

2.6.0 only:

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

2.6.0 and GIT:

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


FlightGear data

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

cd $prefix
wget http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Shared/FlightGear-data-2.6.0.tar.bz2
tar xjf FlightGear-data-2.6.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://mapserver.flightgear.org/fgdata 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

Have in mind that fgfs need to find our self compiled libraries 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.

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

ln -s $HOME/FG-2.6.0/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 FGo!.


Optional Software

Zeichen 101 icon.png Many of the below instructions are most likely not up to date. Please feel free to revise them.

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

Atlas

cd $srcdir
cvs -d:pserver:anonymous@atlas.cvs.sourceforge.net:/cvsroot/atlas login
#CVS passwd: [Enter]
cvs -z3 -d:pserver:anonymous@atlas.cvs.sourceforge.net:/cvsroot/atlas co Atlas
cd Atlas
./autogen.sh
./configure --prefix=$prefix
make install


fgcom

For fgcom unfortunately there is one more dependency which cannot be solved with packages on Lenny, see libopenal.

cd $srcdir
svn co https://appfgcom.svn.sourceforge.net/svnroot/fgcom/trunk fgcom
cd fgcom/src
make INSTALL_BIN=$prefix/bin INSTALL_DIR=$prefix/fgcom \
   PLIB_PREFIX=$prefix [OPENAL_PREFIX=$prefix] install


fgrun

To build fgrun one more package is required:

  • libfltk1.1-dev
cd $srcdir
svn co http://fgrun.svn.sourceforge.net/svnroot/fgrun/trunk fgrun
cd fgrun/fgrun/
./autogen.sh
./configure --prefix=$prefix
make install


TaxiDraw

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://mapserver.flightgear.org/taxidraw
cd taxidraw
./autogen.sh
./configure --prefix=$prefix
make install


TerraGear

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:

  • libgdal1-dev, gdal-bin
  • libproj-dev, libogdi3.2-dev (probably even more, please report!)

Wheezy: As of June 2nd there is a bug (#617240) in package libmysqlclient16 which causes compilation to fail. If it is not fixed by the time you're building TerraGear, upgrade to the version from Sid.

cd $srcdir
git clone git://mapserver.flightgear.org/terragear-cs

Two of the dependencies have to be installed manually (See README.gpc and README.newmat for details.):

# gpc install
mkdir $srcdir/gpc232 && cd $srcdir/gpc232
wget ftp://ftp.cs.man.ac.uk/pub/toby/gpc/gpc232-release.zip
unzip gpc232-release.zip
sed s/DBL_EPSILON/0.000001/ -i gpc.h
grep -A 18 '# Unix/Linux makefile' $srcdir/terragear-cs/README.gpc > Makefile
sed "s|/usr/local/lib|$prefix/lib|" -i Makefile
sed "s|/usr/local/include|$prefix/include|" -i Makefile
make install

# newmat install
mkdir $srcdir/newmat11 && cd $srcdir/newmat11
wget http://www.robertnz.net/ftp/newmat11.tar.gz
tar xzfv newmat11.tar.gz
make -f nm_gnu.mak
cp libnewmat.a $prefix/lib
mkdir $prefix/include/newmat
cp *.h $prefix/include/newmat

Finally TerraGear itself (See README for details.):

cd $srcdir/terragear-cs
./autogen.sh
./configure --prefix=$prefix
sed s/-O2// -i src/Lib/TriangleJRS/Makefile
make install