Building FlightGear - Debian: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
(cosmetics and typos)
(Redirected to Building_FlightGear_-_Devuan until someone takes over here.)
 
(42 intermediate revisions by 7 users not shown)
Line 1: Line 1:
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/<u>Squeeze</u>. Users of Oldstable, Testing/<u>Wheezy</u> or Unstable at least have to change package names (version numbering) accordingly.
#REDIRECT[[Building_FlightGear_-_Devuan]]
 
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 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.
 
 
== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:
 
; Tools
su -c "apt-get install automake cmake g++ gcc git make subversion unzip"
: Additionally install "fluid" if you intend to use [[FlightGear_Admin_Wizard|fgadmin]].
 
 
; Dependencies
Command for <u>Squeeze</u>, users of other releases are advised to check package versions:
su -c "apt-get install  \
  freeglut3-dev  libboost-dev  libcurl4-openssl-dev  libgtkglext1-dev \
  libjpeg8-dev  libopenal-dev  librsvg2-dev          libsvn-dev \
  libxml2-dev    libxrandr-dev"
: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".
: 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" and "simgear-dev".
<!--
osg: libxml2-dev libcurl4-openssl-dev libgtkglext1-dev libopenal-dev libpng12-dev librsvg2-dev libtiff4-dev
sg: libalut-dev libboost1.42-dev libsvn-dev
fg: freeglut3-dev (libfltk1.1-dev (für fgadmin) fluid) (libudev-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-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, 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>$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 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 prefix=$HOME/FG-2.10.0 && mkdir $prefix
export srcdir=$HOME/src && mkdir $srcdir
 
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. <br />
For some basic info on git commands for FlightGear users we have a [[Git#For dummies|git for dummies]] section. <br />
To have a build with debugging symbols add <code>-D CMAKE_BUILD_TYPE="RelWithDebInfo"</code> to SimGear's and FlightGear's cmake options.
 
 
=== libfltk ===
[http://www.fltk.org/ FLTK] only is required for [[fgadmin]], which is content with libfltk-1.1, and fgrun, which minimum is libfltk-1.3. <br />
<u>Wheezy</u>: Just install package "libfltk1.3-dev" if you're planning to use either of them. <br />
<u>Squeeze</u>: For fgadmin just install package "libfltk1.1-dev". To compile fgrun, too, build and install FLTK-1.3 instead:
cd $srcdir
wget http://ftp.easysw.com/pub/fltk/1.3.2/fltk-1.3.2-source.tar.gz
tar xzf fltk-1.3.2-source.tar.gz
cd fltk-1.3.2
./configure --enable-shared --prefix=$prefix
make -j2 install
 
 
=== [[plib]] ===
<u>2.10.0</u> and <u>GIT</u>:
Latest SVN is [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html required].
cd $srcdir
svn co https://plib.svn.sourceforge.net/svnroot/plib/trunk plib
cd plib
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
./autogen.sh
./configure --prefix=$prefix
make -j2 install
 
 
=== [[OpenSceneGraph]] ===
For <u>2.10.0</u> on <u>Wheezy</u> skip that step and install package "libopenscenegraph-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 />
<u>2.10.0</u> and <u>GIT</u>:
cd $srcdir
svn co http://www.openscenegraph.org/svn/osg/OpenSceneGraph/tags/OpenSceneGraph-3.1.1 OpenSceneGraph
mkdir build-osg; cd build-osg
cmake -D CMAKE_BUILD_TYPE="Release" -DLIB_POSTFIX="" \
      -D CMAKE_INSTALL_PREFIX:PATH="$prefix" $srcdir/OpenSceneGraph
make -j2 install
 
 
=== [[SimGear]] ===
<u>2.10.0</u> and <u>GIT</u>:
cd $srcdir
git clone git://mapserver.flightgear.org/simgear
 
<u>2.10.0</u> only:
cd simgear
git checkout -b 2.10.0 origin/release/2.10.0
 
<u>2.10.0</u> and <u>GIT</u>:
mkdir $srcdir/build-sg; cd $srcdir/build-sg
cmake -D CMAKE_INSTALL_PREFIX:PATH="$prefix" $srcdir/simgear
make -j2 install
 
 
=== FlightGear source ===
<u>2.10.0</u> and <u>GIT</u>:
cd $srcdir
git clone git://mapserver.flightgear.org/flightgear
 
<u>2.10.0</u> only:
cd flightgear
git checkout -b 2.10.0 origin/release/2.10.0
 
<u>2.10.0</u> and <u>GIT</u>:
mkdir $srcdir/build-fg; cd $srcdir/build-fg
cmake -D CMAKE_INSTALL_PREFIX:PATH="$prefix" $srcdir/flightgear
make -j2 install
 
 
=== FlightGear data ===
<u>2.10.0</u> only: Please have a look at the [http://www.flightgear.org/download/mirror/ mirror list] for a server close to your location.
cd $prefix
wget http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Shared/FlightGear-data-2.10.0.tar.bz2
tar xjf FlightGear-data-2.10.0.tar.bz2
 
<u>GIT</u> only:
For slow/unstable internet connections it is recommended to download the [[Git#fgdata.bundle|fgdata.bundle]] instead of cloning the data.<br />
cd $prefix
git clone git://mapserver.flightgear.org/fgdata data
 
 
== Trial run and finishing process ==
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/data
: 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 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
 
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!]]-->.
 
 
{{WIP|Revise due to update to FG 2.10}}
 
== Optional Software ==
[[File:Zeichen_101_icon.png|21px]] Some of the below instructions possibly are not up to date. Please feel free to revise them.
 
Feel free to add the commands to install other FlightGear related projects.
 
=== [[Atlas]] ===
One more Package has to be installed: "libglew1.5-dev"
cd $srcdir
git clone http://mapserver.flightgear.org/git/atlas
cd atlas
./autogen.sh
./configure --prefix=$prefix --with-fgbase=$prefix/data
make -j2 install
cp -R $srcdir/atlas/src/data/* $prefix/data/Atlas
<!--If it does not compile, go back some commits. Before invoking the <code>autogen.sh</code> command do:
git reset --hard 5a27c351a8c03c7fa47cba0b4af7f4e23e4c31b0-->
 
$prefix/bin/Atlas
 
 
=== fgcom ===
For [[fgcom]] install package "libasound2-dev".
cd $srcdir
<!--git clone http://mapserver.flightgear.org/git/fgcom -->
svn co https://appfgcom.svn.sourceforge.net/svnroot/fgcom/trunk fgcom
cd fgcom/src
make -j2 install_BIN=$prefix/bin INSTALL_DIR=$prefix/fgcom \
    PLIB_PREFIX=$prefix [OPENAL_PREFIX=$prefix] install
Create an .alsoftrc file as shown in [[FGCOM_Testing#Special_for_Linux_.28.alsoftrc.29|FGCOM Testing]].
 
 
=== fgrun ===
To build [[fgrun]] libfltk1.3 is required, see [[#libfltk|libfltk above]]. <br />
<u>2.10.0</u> and <u>GIT</u>:
cd $srcdir
git clone git://gitorious.org/fg/fgrun.git
 
<u>2.10.0</u> only:
cd fgrun
git checkout -b 1.7.0 origin/release/1.7.0
 
<u>2.10.0</u> and <u>GIT</u>:
mkdir $srcdir/fgrun-build; cd $srcdir/fgrun-build
cmake -D CMAKE_INSTALL_PREFIX:PATH="$prefix" $srcdir/fgrun
make -j2 install
 
<u>2.10.0</u> and <u>GIT</u>:
export LD_LIBRARY_PATH=$prefix/lib/:$LD_LIBRARY_PATH
$prefix/bin/fgrun
 
 
=== TaxiDraw ===
[[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:
* either "libcurl4-gnutls-dev" or "libcurl4-openssl-dev" for curl.h
* "wx2.8-headers" (at least, maybe even more than just that one. Please [http://wiki.flightgear.org/index.php?title=Talk:Building_FlightGear_-_Debian&action=edit&redlink=1 report]!
su -c "aptitude install [libcurl4-gnutls-dev|libcurl4-openssl-dev]"
cd $srcdir
git clone git://mapserver.flightgear.org/taxidraw
cd taxidraw
./autogen.sh
./configure --prefix=$prefix
make -j2 install
 
 
=== [[TerraGear]] ===
==== 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.
 
; ''How to use it?''
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 ;) )
 
; ''Need some help?''
Look at forum topics : http://www.flightgear.org/forums/viewtopic.php?f=20&t=14849
 
After success installation you can exectute this command line in the terragear/bin directory in order to display every --help for each binary files:
cd terragear/bin && for i in `ls`; do echo ""; echo "################# "$i" ##############"; ./$i --help; done
 
==== Basic Installation ====
To resolve some of the dependencies of [[TerraGear]] the GIT sections of steps [[#plib|plib]], [[#OpenSceneGraph|OpenSceneGraph]] and [[#SimGear|SimGear]] have to be done first. Additionally some packages and their dependencies have to be installed:
* libgdal1-dev, gdal-bin
* libproj-dev, libogdi3.2-dev (probably even more, please [http://wiki.flightgear.org/index.php?title=Talk:Building_FlightGear_-_Debian&action=edit&redlink=1 report]!)
<u>Wheezy</u>: As of June 2nd there is a bug ([http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617240 #617240]) in package libmysqlclient16 which causes compilation to fail. If it is not fixed by the time you're building TerraGear, upgrade to the version from Sid.
 
cd $srcdir
git clone git://mapserver.flightgear.org/terragear-cs
 
Two of the dependencies have to be installed manually (See [http://mapserver.flightgear.org/git/?p=terragear-cs;a=blob;f=README.gpc;h=226e185b1ce1d1578006b48bb426e35848cce93b;hb=HEAD README.gpc] and [http://mapserver.flightgear.org/git/?p=terragear-cs;a=blob;f=README.newmat;h=95570b6b279d3d00bd7664cd4f00d6c4802aed1b;hb=HEAD README.newmat] for details.):
 
# gpc install
mkdir $srcdir/gpc232 && cd $srcdir/gpc232
wget ftp://ftp.cs.man.ac.uk/pub/toby/gpc/gpc232-release.zip
unzip gpc232-release.zip
sed s/DBL_EPSILON/0.000001/ -i gpc.h
grep -A 18 '# Unix/Linux makefile' $srcdir/terragear-cs/README.gpc > Makefile
sed "s|/usr/local/lib|$prefix/lib|" -i Makefile
sed "s|/usr/local/include|$prefix/include|" -i Makefile
make -j2 install
# newmat install
mkdir $srcdir/newmat11 && cd $srcdir/newmat11
wget http://www.robertnz.net/ftp/newmat11.tar.gz
tar xzfv newmat11.tar.gz
make -f nm_gnu.mak
cp libnewmat.a $prefix/lib
mkdir $prefix/include/newmat
cp *.h $prefix/include/newmat
 
Finally TerraGear itself (See [http://mapserver.flightgear.org/git/?p=terragear-cs;a=blob;f=README;h=7dae654283ca0b1447aeb3aa398287219f4b57df;hb=HEAD README] for details.):
cd $srcdir/terragear-cs
./autogen.sh
./configure --prefix=$prefix
sed s/-O2// -i src/Lib/TriangleJRS/Makefile
make -j2 install
 
 
=== WorldEditor (WED) ===
Because this is the same for all Linux distributions the instructions are not listed here separately. Please refer to our [[WorldEditor#Linux|lead WED article]].
 
 
{{Building}}
 
[[de:FlightGear bauen - Debian]]

Latest revision as of 14:45, 28 May 2017

Redirect to:

Retrieved from "https://wiki.flightgear.org/w/index.php?title=Building_FlightGear_-_Debian&oldid=107956"