Building FlightGear - Debian: Difference between revisions

Jump to navigation Jump to search
m
reviewed by native speaker :-)
m (added link to download mirror list)
m (reviewed by native speaker :-))
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).
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 one or more dependencies of the GIT version are changing or beeing added.
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]].
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 make 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]].




== Requirements and Preparations ==
== Requirements and Preparations ==
You need an OpenGL capable graphics 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 (and some of their dependencies) are required:
* gcc, g++, make, automake, pkg-config
* gcc, g++, make, automake, pkg-config
* mawk (or gawk)
* mawk (or gawk)
* cmake (min. version 2.6.0-5)
* cmake (min. version 2.6.0-5)
* git, subversion, wget
* git, subversion, wget
* freeglut3-dev, libgl1-mesa-dev, libxrandr-dev
* (freeglut3-dev,) libgl1-mesa-dev, libxrandr-dev
* libxi-dev, libxmu-dev, libxext-dev
* libxi-dev, libxmu-dev, libxext-dev
* libopenal-dev (for Lenny see [[#libopenal|libopenal]]), libalut-dev
* libopenal-dev (for Lenny see [[#libopenal|libopenal]]), libalut-dev
Line 26: Line 25:


== 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 FG-2.4.0 and/or GIT in a place independent to 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 that 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 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.
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 prefix=[path to install to]
Line 79: Line 78:
<u>2.4.0 and GIT:</u>
<u>2.4.0 and GIT:</u>
  ./autogen.sh
  ./autogen.sh
  ./configure --prefix=$prefix <!--CPPFLAGS=-I$prefix/include/-->
  ./configure --prefix=$prefix
  make install
  make install


Line 140: Line 139:
  cd fgcom/src
  cd fgcom/src
  make INSTALL_BIN=$prefix/bin INSTALL_DIR=$prefix/fgcom \
  make INSTALL_BIN=$prefix/bin INSTALL_DIR=$prefix/fgcom \
     PLIB_PREFIX=$prefix OPENAL_PREFIX=$prefix install
     PLIB_PREFIX=$prefix [OPENAL_PREFIX=$prefix] install




392

edits

Navigation menu