Building FlightGear - Debian: Difference between revisions

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

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.

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

You need an OpenGL capable graphics card including a proper installed driver supporting direct rendering.<br />

During installation packages ''simgear-dev'' and ''openscenegraph-dev'' '''must not''' be installed. They can safely be re-installed after compilation.

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 />

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.

  export prefix=[path to install to]

  export srcdir=[path to sources]

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.

=== plib ===

=== 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!

  svn co http://www.openscenegraph.org/svn/osg/OpenSceneGraph/tags/OpenSceneGraph-2.9.10 OpenSceneGraph

  cmake -D CMAKE_BUILD_TYPE="Release" \

=== SimGear ===

<u>2.4.0 and GIT:</u>

<u>2.4.0 only:</u>

  git checkout -b 2.4.0 origin/release/2.4.0

<u>GIT only:</u>

  mkdir sg-build && cd sg-build

<u>2.4.0 and GIT:</u>

<u>2.4.0 only:</u>

  git checkout -b 2.4.0 origin/release/2.4.0

<u>GIT only:</u>

  mkdir fg-build && cd fg-build

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

  wget http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Shared/FlightGear-data-2.4.0.tar.bz2

  tar xjf FlightGear-data-2.4.0.tar.bz2

== Trial run ==

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.

=== Atlas ===