FlightGear wiki

Building FlightGear - Debian: Difference between revisions

Page Discussion

Building FlightGear - Debian (view source)

Revision as of 03:53, 22 February 2013

402 bytes added ,  22 February 2013
Update mostly completed
m (Marked as WIP)
(Update mostly completed)
Line 1: Line 1:
{{WIP|Revise due to update to FG 2.10}}
{{WIP|Revise due to update to FG 2.10}}


HowTo build [[FlightGear]] <u>[[Changelog_2.8.0|2.8.0]]</u> or bleeding edge development version, hereinafter simply called <u>[[GIT]]</u>, on GNU/Linux [http://www.debian.org/ Debian] '''Stable''' 6.x (Squeeze) and '''Testing''' (Wheezy).
HowTo build [[FlightGear]] <u>[[Changelog_2.10.0|2.10.0]]</u> or bleeding edge development version, hereinafter simply called <u>[[GIT]]</u>, 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]].
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]].


[[File:Zeichen_144_icon.png|21px]] For beginners with compiling who want to build version 2.10.x it is highly recommended to follow this guide step by step.  
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]].
[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to the commands may cause trouble.




Line 25: Line 25:
   libgtkglext1-dev libopenal-dev libpng12-dev librsvg2-dev libsvn-dev \
   libgtkglext1-dev libopenal-dev libpng12-dev librsvg2-dev libsvn-dev \
   libtiff4-dev libxml2-dev"
   libtiff4-dev libxml2-dev"
: If you prefer you might replace libcurl4-openssl-dev by libcurl4-gnutls-dev.
: libfltk1.1-dev: needed for fgadmin only.
: libfltk1.1-dev: needed for fgadmin only.
: Add libudev-dev if you need FG's feature <code>-DEVENT_INPUT=ON</code>.
: Add libudev-dev if you need FG's feature <code>-D EVENT_INPUT=ON</code>.
: [[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.
: [[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.
: 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
osg: libxml2-dev libcurl4-gnutls-dev/libcurl4-openssl-dev libgtkglext1-dev libopenal-dev libpng12-dev librsvg2-dev libtiff4-dev
Line 37: Line 37:


== Build and install ==
== 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 <code>/usr/local/FG-2.8.0</code> or <code>$HOME/FG-2.8.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 -j2 install</code> commands. We'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 Debian repositories, it is recommended to install FlightGear in a place independent of the base system, such as <code>/usr/local/FG-2.10.0</code> or <code>$HOME/FG-2.10.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 -j2 install</code> commands. We'll use <code>$prefix</code> as a placeholder for this directory. <br />
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:
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 (in every terminal you're using them) during the process:
  export prefix=$HOME/FG-2.8.0 && mkdir $prefix
  export prefix=$HOME/FG-2.10.0 && mkdir $prefix
  export srcdir=$HOME/src && mkdir $srcdir
  export srcdir=$HOME/src && mkdir $srcdir


To have a build with debugging symbols add <code>-D CMAKE_BUILD_TYPE="RelWithDebInfo"</code> to SimGear's and FlightGear's cmake options.
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 [[#FlightGear data|fetch]] it while building the sources.


Have in mind that the data is a relatively large download (GIT about 5 GB and 2.8.0 650 MB). So, to save some time, it is a good idea to [[#FlightGear data|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.
To have a build with debugging symbols add <code>-D CMAKE_BUILD_TYPE="RelWithDebInfo"</code> to SimGear's and FlightGear's cmake options.




Line 61: Line 61:


=== [[plib]] ===
=== [[plib]] ===
<u>2.8.0 and GIT:</u>
<u>2.10.0 and GIT:</u>
Latest SVN is [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html required].
Latest SVN is [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html required].
  cd $srcdir
  cd $srcdir
Line 70: Line 70:
  ./configure --prefix=$prefix
  ./configure --prefix=$prefix
  make -j2 install
  make -j2 install
<!--If it does not compile, go back some revisions. Before invoking the <code>sed</code> command do:
svn update -r2166 -->




=== [[OpenSceneGraph]] ===
=== [[OpenSceneGraph]] ===
<u>Squeeze</u> 3.0.1
For <u>2.10.0</u> at least version 3.0.1 is recommended. Users of <u>Wheezy</u> can skip that step and install package openscenegraph-dev instead. <br />
 
<u>GIT</u> users, especially developers, most likely want to use the latest [http://www.openscenegraph.org/projects/osg/wiki/Downloads/DeveloperReleases DeveloperRelease] or even bleeding edge code here. <br />
For <u>2.8.0</u> at least version 3.0.1 is recommended. <u>GIT</u> users, especially developers, may want to use the latest release or even bleeding edge code here instead. <br />
<u>2.10.0 and GIT:</u>
<u>2.8.0 and GIT:</u>
  cd $srcdir
  cd $srcdir
  svn co http://www.openscenegraph.org/svn/osg/OpenSceneGraph/tags/OpenSceneGraph-3.0.1 OpenSceneGraph
  svn co http://www.openscenegraph.org/svn/osg/OpenSceneGraph/tags/OpenSceneGraph-3.1.1 OpenSceneGraph
  mkdir osg-build && cd osg-build
  mkdir osg-build && cd osg-build
  cmake -D CMAKE_BUILD_TYPE="Release" -DLIB_POSTFIX="" \
  cmake -D CMAKE_BUILD_TYPE="Release" -DLIB_POSTFIX="" \
Line 88: Line 85:


=== [[SimGear]] ===
=== [[SimGear]] ===
<u>2.8.0 and GIT:</u>
<u>2.10.0 and GIT:</u>
  cd $srcdir
  cd $srcdir
  git clone git://mapserver.flightgear.org/simgear
  git clone git://mapserver.flightgear.org/simgear


<u>2.8.0 only:</u>
<u>2.10.0 only:</u>
  cd simgear
  cd simgear
  git checkout -b 2.8.0 origin/release/2.8.0
  git checkout -b 2.10.0 origin/release/2.10.0


<u>2.8.0 and GIT:</u>
<u>2.10.0 and GIT:</u>
  mkdir $srcdir/sg-build && cd $srcdir/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
Line 103: Line 100:


=== FlightGear source ===
=== FlightGear source ===
<u>2.8.0 and GIT:</u>
<u>2.10.0 and GIT:</u>
  cd $srcdir
  cd $srcdir
  git clone git://mapserver.flightgear.org/flightgear
  git clone git://mapserver.flightgear.org/flightgear


<u>2.8.0 only:</u>
<u>2.10.0 only:</u>
  cd flightgear
  cd flightgear
  git checkout -b 2.8.0 origin/release/2.8.0
  git checkout -b 2.10.0 origin/release/2.10.0


<u>2.8.0 and GIT:</u>
<u>2.10.0 and GIT:</u>
  mkdir $srcdir/fg-build && cd $srcdir/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
Line 118: Line 115:


=== FlightGear data ===
=== FlightGear data ===
<u>2.8.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.10.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.8.0.tar.bz2
  wget http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Shared/FlightGear-data-2.10.0.tar.bz2
  tar xjf FlightGear-data-2.8.0.tar.bz2
  tar xjf FlightGear-data-2.10.0.tar.bz2


<u>GIT only:</u>
<u>GIT only:</u>
Line 133: Line 130:
  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 (may cause problems, if one has installed more than one version of FlightGear!).
: The <code>fgfs</code> 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 <code>$HOME/.bashrc</code> to have this as a persistent setting (may cause problems, if one has installed more than one version of FlightGear!).
: Have in mind, the <code>$prefix</code> and <code>$srcdir</code> 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 <code>fgfs</code> command in the second line, you might consider to create a symlink to a place that is listed in $PATH:
To avoid the need to give the path to the <code>fgfs</code> 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
  ln -s $prefix/bin/fgfs $HOME/bin/fgfs


Line 145: Line 143:


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]] ===
Line 184: Line 181:
To build [[fgrun]] one more package is required:
To build [[fgrun]] one more package is required:
* libfltk1.1-dev
* libfltk1.1-dev
<u>2.8.0 only:</u>
<u>2.10.0 only:</u>
  cd $srcdir
  cd $srcdir
  wget --trust-server-names http://sourceforge.net/projects/fgrun/files/fgrun/1.6.2/fgrun-1.6.2.tar.bz2/download
  wget --trust-server-names http://sourceforge.net/projects/fgrun/files/fgrun/1.6.2/fgrun-1.6.2.tar.bz2/download
Line 199: Line 196:
  make -j2 install
  make -j2 install


<u>2.8.0 and GIT:</u>
<u>2.10.0 and GIT:</u>
  export LD_LIBRARY_PATH=$prefix/lib/:$LD_LIBRARY_PATH
  export LD_LIBRARY_PATH=$prefix/lib/:$LD_LIBRARY_PATH
  $prefix/bin/fgrun
  $prefix/bin/fgrun
Line 205: Line 202:


=== TaxiDraw ===
=== TaxiDraw ===
[[File:Zeichen_101_icon.png|21px]] Obsolete! Use [[#WorldEditor|WorldEditor]] instead.<br />
[[File:Zeichen_101_icon.png|21px]] Obsolete for airport creation, use [[WorldEditor]] instead. It is still useful for working on [[Interactive_traffic#Ground_networks|ground networks]]. <br />
To compile [[Taxidraw|TaxiDraw]] we need to install some more packages:
To compile [[Taxidraw|TaxiDraw]] we need to install some more packages:
* either libcurl4-gnutls-dev or libcurl4-openssl-dev for curl.h
* either libcurl4-gnutls-dev or libcurl4-openssl-dev for curl.h
Line 219: Line 216:


=== TerraGear ===
=== TerraGear ===
==== Automatic Installation ====
==== Automatic Installation ====
If you are familiar with "download_and_compile.sh" script from Brisa you can donwload this script: http://clemaez.fr/flightgear/terragear_download_and_compile.sh
This script is similar to Brisa's one (only usable for Debian/Ubuntu/Mint...). This script installs TerraGear (latest version) and terragear-gui.


If you are familiar with "download_and_compile.sh" script from Brisa you can donwload this script : http://clemaez.fr/flightgear/terragear_download_and_compile.sh
; ''How to use it?''
This script is similar to Brisa script (only usable for Debian/Ubuntu/Mint...). Thi script install TerraGear (last version) en terragear-gui.
 
;''How to use it?''
  sh terragear_download_and_compile.sh -j 2 ALL
  sh terragear_download_and_compile.sh -j 2 ALL


-j 2 option is for Dual Core, you can tune it as you want. (personnaly I have Quad Core and I use -j 12 but I need to accept to don't use my aircraft during compilation ;) )
-j 2 option is for Dual Core, you can tune it as you want. (personnaly I have Quad Core and I use -j 12 but I need to accept to don't use my aircraft during compilation ;) )


;''Need some help?''
; ''Need some help?''
Look at forum topics : http://www.flightgear.org/forums/viewtopic.php?f=20&t=14849
Look at forum topics : http://www.flightgear.org/forums/viewtopic.php?f=20&t=14849


Flughund
392

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/58159"