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

Changes

Jump to: navigation, search

Building FlightGear - Debian

497 bytes added, 16:45, 5 February 2011
m
Reworked the topology of the topics and did some minor corrections.
HowTo build FlightGear 2.2.0 or bleeding edge development version, hereinafter simply called ''GIT'', on GNU/Linux Debian '''Stable''' 6.x (Squeeze) and '''Testing'''/'''Unstable''' (Wheezy).
Even on Debian '''Oldstable''' 5.x (Lenny) this guide will work for both, 2.2.0 and GIT. At least until one or more dependencies of the GIT version are changing or beening beeing added.
If you don't want to make your hands dirty, have a look at [[Scripted_Compilation_on_Linux_Debian/Ubuntu]].
*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.
=== libopenal Dependencies ===In some aspects FlightGear'''s development relies closely on plib and OpenSceneGraph. Therefore the GIT users are encouraged to update them regularly. Not each time one rebuilds FlightGear but from time to time. ==== libopenal ====<u>Lenny only!''' </u> 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
==== plib ====
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
==== OpenSceneGraph ====
<u>2.2.0 only:</u>
cd $srcdir
== Note = FlightGear and Components ===From this point forward when providing the "LDFLAGS" string, you should use the path specific to your installation. For 32-bit installations this will probably be the path ending in /lib. In a 64-bit installation, this '''may''' be the path ending in /lib64, but doesn't have to beFlighGear relies very closely on its data and SimGear. You must verify this for your build, because you do not have Therefore it is necessary to include both paths in the following compilationsupdate them at one time.
From this point forward when providing the <code>LDFLAGS</code> string, you should use the path specific to your installation. For 32-bit installations this will probably be the path ending in /lib. In a 64-bit installation, this '''may''' be the path ending in /lib64, but doesn't have to be. You must verify this for your build, because you do not have to include both paths in the following compilations.
==== SimGear ====
<u>2.2.0 and GIT:</u>
cd $srcdir
==== FlightGear source ====
<u>2.2.0 and GIT:</u>
cd $srcdir
==== FlightGear data ====
<u>2.2.0 only:</u>
At the time of writing, 2.2.0 is not yet released, there is no tar archive for the data available. Test pilots for this release are advised to use the ''release/2.2.0'' branch from git. The following URL for wget will be updated, if it is not working, as soon as 2.2.0 is released.
=== Trial 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
$prefix/bin/fgfs --fg-root=$prefix/fgdata
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.
== Optional Software ==
Feel free to add the commands to install other FlightGear related projects.
 
=== fgrun ===
To build [[fgrun]] two one more package is required:
*libfltk1.1-dev
380
edits

Navigation menu