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


Jump to: navigation, search

Building FlightGear - Debian

536 bytes added, 11:39, 4 February 2015
Update to 3.4.0-rc1
<!-- {{WIP|Article is being updated for the 3.2 4 release. Atm. building <u>3.24</u> will result in release candidate 3.24.0-RC2RC1.}} <!-- die RC1es nicht vergessen! -->
HowTo build [[FlightGear]] stable/<u>[[Changelog_3.24|3.24]]</u> or bleeding edge development version, hereinafter simply called <u>[[GIT]]</u>, on [http://www.debian.org/ Debian] GNU/Linux Stable/(<u>Wheezy</u>). Users of Testing 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_-_Linux | Building FlightGear on Linux]].
: Add "libudev-dev" if you need FG's feature <code>-D EVENT_INPUT=ON</code>.
: [[File:Zeichen_144_icon.png|21px]] 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", "libopenthreads-dev" and "simgear-dev".
osg: libxml2-dev libcurl4-openssl-dev libgtkglext1-dev libopenal-dev libpng12-dev librsvg2-dev libtiff4-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 <code>/usr/local/FG-3.24</code> or <code>$HOME/FG-3.24</code>. 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 <code>make -j2 install</code> commands. We'll use <code>$FG_INSTALL_DIR</code> as a [http://www.cmiss.org/cmgui/wiki/SettingEnvironmentVariablesInBash placeholder] for this directory. <br />
Another placeholder will be <code>$FG_SRC_DIR</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 instructions below, you have to replace these with the local paths or even <code>export</code> them (in every terminal you're using them) for the process:
export FG_INSTALL_DIR=$HOME/FG-3.24-rc1 RC1 && 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 8 GiB (required disk space 18 GiB) and growing / 3.2 4 about 1.2 1 GB). So, to save some time, it is a good idea to [[#FlightGear data|fetch]] it while building the sources. <br />
For some basic info on git commands for FlightGear users we have a [[Git_for_Laymen#How_do_I_use_the_git_repository_to_update_Flightgear_stuff.3F|git for laymen]] section. <br />
=== [[plib]] ===
<u>3.24</u> and <u>GIT</u>:<br />
Latest SVN is [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html required].
./configure --prefix=$FG_INSTALL_DIR
make -j2 install
=== libboost ===
<u>3.4</u> and <u>GIT</u>: <br />
Unfortunately version 1.52 or newer is recommended while Wheezy ships with 1.49:
<nowiki>wget -O boost_1_52_0.tar.bz2 http://sourceforge.net/projects/boost/files/boost/1.52.0/boost_1_52_0.tar.bz2/download</nowiki>
tar xjf boost_1_52_0.tar.bz2
cp -R boost_1_52_0/boost $FG_INSTALL_DIR/include/
=== [[OpenSceneGraph]] ===
<u>3.24</u>'s optimum version is OSG 3.2.01. <br /><u>GIT</u> users, especially developers, may want to use the latest [http://www.openscenegraph.org/index.php/download-section/developer-releases DeveloperRelease] or even bleeding edge code here instead. Note: FG 3.2.0 proved to be unstable with OSG 3.2.1!<br />
<u>3.24</u> and <u>GIT</u>:
<nowiki>svn co http://svn.openscenegraph.org/osg/OpenSceneGraph/tags/OpenSceneGraph-3.2.01</nowiki>
mkdir build-osg; cd build-osg
make -j2 install
=== [[SimGear]] ===
<u>3.24</u> and <u>GIT</u>:
<nowiki>git clone git://mapserver.flightgear.org/simgear simgear.git</nowiki>
<u>3.24</u> only:
cd simgear.git
git checkout origin/release/3.24.0
<u>3.24</u> and <u>GIT</u>:
mkdir $FG_SRC_DIR/build-sg; cd $FG_SRC_DIR/build-sg
make -j2 install
=== FlightGear source ===
<u>3.24</u> and <u>GIT</u>:
<nowiki>git clone git://mapserver.flightgear.org/flightgear flightgear.git</nowiki>
<u>3.24</u> only:
cd flightgear.git
git checkout origin/release/3.24.0
<u>3.24</u> and <u>GIT</u>:
mkdir $FG_SRC_DIR/build-fg; cd $FG_SRC_DIR/build-fg
make -j2 install
=== FlightGear data ===
<u>3.24</u> only: Please have a look at the [http://www.flightgear.org/download/mirror/ mirror list] for a server close to your location.
<nowiki>wget ftp://ftp.snt.utwente.nl/pub/software/flightgear/ftp/Shared/FlightGear-data-3.24.0-rc1RC1.tar.bz2</nowiki> tar xjf FlightGear-data-3.24.0-rc1RC1.tar.bz2
<u>GIT</u> only:
=== [[fgrun]] ===
Package "fluid" has to be installed. <br />
<u>3.24</u> and <u>GIT</u>:
<nowiki>git clone git://gitorious.org/fg/fgrun.git fgrun.git</nowiki>
<u>3.24</u> only:
cd fgrun.git
git checkout origin/release/3.24.0
<u>3.24</u> and <u>GIT</u>:
mkdir $FG_SRC_DIR/build-fgrun; cd $FG_SRC_DIR/build-fgrun

Navigation menu