Building FlightGear - Debian: Difference between revisions

no edit summary
m (update to 2016.2)
No edit summary
Line 2: Line 2:
<!-- {{note|So far the author wasn't able to compile a working FlightGear 3.4 on Jessie. Therefore this article will not receive an update until 3.6 is released. Compile and run GIT/next on Jessie works as decribed below, just skip the libboost part.}} -->
<!-- {{note|So far the author wasn't able to compile a working FlightGear 3.4 on Jessie. Therefore this article will not receive an update until 3.6 is released. Compile and run GIT/next on Jessie works as decribed below, just skip the libboost part.}} -->


HowTo build [[FlightGear]] stable (<u>[[Changelog_2016.2|2016.2]]</u>) or bleeding edge development version, hereinafter simply called <u>[[FlightGear_Git#Repositories_and_branches | next]]</u>, on [http://www.debian.org/ Debian] GNU/Linux Stable (<u>Jessie</u>). Users of Testing or Unstable at least have to change package names (version numbering) accordingly.<br />
HowTo build [[FlightGear]] stable (<u>[[Changelog_2016.4|2016.4]]</u>) or bleeding edge development version, hereinafter simply called <u>[[FlightGear_Git#Repositories_and_branches | next]]</u>, on [http://www.debian.org/ Debian] GNU/Linux Stable (<u>Jessie</u>). Users of Testing or Unstable at least have to change package names (version numbering) accordingly.<br />
Instructions also apply on [http://devuan.org/ Devuan] GNU/Linux Jessie (Beta).
Instructions also apply on [http://devuan.org/ Devuan] GNU/Linux Jessie (Beta).


Line 23: Line 23:
   freeglut3-dev  libboost-dev      libcurl4-openssl-dev  libdbus-1-dev \
   freeglut3-dev  libboost-dev      libcurl4-openssl-dev  libdbus-1-dev \
   libfltk1.3-dev  libgtkglext1-dev  libjpeg62-turbo-dev  libopenal-dev \
   libfltk1.3-dev  libgtkglext1-dev  libjpeg62-turbo-dev  libopenal-dev \
   libopenscenegraph-dev   librsvg2-dev    libxml2-dev"
   libopenscenegraph-dev             libqt5opengl5-dev    librsvg2-dev \
   libxml2-dev     qt5-default"
      
      
: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".
: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".
: If "libjpeg62-turbo-dev" breaks package dependencies, just install one of the other versions' -dev.
: If "libjpeg62-turbo-dev" breaks package dependencies, just install one of the other versions' -dev.
: Add "libudev-dev" if you need FG's feature <code>-D EVENT_INPUT=ON</code>.
: Add "libudev-dev" if you need FG's feature <code>-D EVENT_INPUT=ON</code>.
: Add "qt5-default" and "libqt5opengl5-dev" if you intend to use/test FG's internal, yet experimental, [[Qt5 Launcher]].


: [[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 these are "libplib-dev" and "simgear-dev". <!--For <u>Wheezy</u> additionally "libboost-dev", "libopenthreads-dev" and "libopenscenegraph-dev".-->
: [[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 these are "libplib-dev" and "simgear-dev". <!--For <u>Wheezy</u> additionally "libboost-dev", "libopenthreads-dev" and "libopenscenegraph-dev".-->
Line 39: Line 39:


== Build and install ==
== 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-2016.2</code> or <code>$HOME/FG-2016.2</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 && make 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 />
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-2016.4</code> or <code>$HOME/FG-2016.4</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 && make 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:
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-2016.2 && mkdir $FG_INSTALL_DIR
  export FG_INSTALL_DIR=$HOME/FG-2016.4 && mkdir $FG_INSTALL_DIR
  export FG_SRC_DIR=$HOME/src && mkdir $FG_SRC_DIR
  export FG_SRC_DIR=$HOME/src && mkdir $FG_SRC_DIR


Have in mind that the data is a relatively large download (GIT about 1.5 GiB (required disk space 3.1 GiB) / 2016.2 about 1.3 GiB). So, to save some time, it is a good idea to [[#FlightGear data|fetch]] it while building the sources. <br />
Have in mind that the data is a relatively large download (GIT about 2.3 GiB (required disk space 4 GiB) / 2016.4 about 1.6 GiB). 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 />
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 />


For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.
For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.


[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix instructions for <u>2016.2</u> and <u>next</u>! Not even for fgdata, mixing versions will almost certainly break the installation.
[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix instructions for <u>2016.4</u> and <u>next</u>! Not even for fgdata, mixing versions will almost certainly break the installation.




Line 55: Line 55:
=== libboost ===
=== libboost ===
<u>Debian 7.x/Wheezy</u> only! <br />
<u>Debian 7.x/Wheezy</u> only! <br />
<u>2016.2</u> and <u>next</u>: <br />
<u>2016.4</u> and <u>next</u>: <br />
Unfortunately version 1.52 or newer is recommended while Wheezy ships with 1.49:
Unfortunately version 1.52 or newer is recommended while Wheezy ships with 1.49:
  cd $FG_SRC_DIR
  cd $FG_SRC_DIR
Line 71: Line 71:


=== [[plib]] ===
=== [[plib]] ===
<u>2016.2</u> and <u>next</u>: <br />
<u>2016.4</u> and <u>next</u>: <br />
Latest SVN is [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html required].
Latest SVN is [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html required].
  cd $FG_SRC_DIR
  cd $FG_SRC_DIR
Line 99: Line 99:


=== [[SimGear]] ===
=== [[SimGear]] ===
<u>2016.2</u> and <u>next</u>:
<u>2016.4</u> and <u>next</u>:
  cd $FG_SRC_DIR
  cd $FG_SRC_DIR
  <nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>
  <nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>


<u>2016.2</u> only:
<u>2016.4</u> only:
  cd simgear.git
  cd simgear.git
  git checkout release/2016.2
  git checkout release/2016.4


<u>2016.2</u> and <u>next</u>:
<u>2016.4</u> and <u>next</u>:
  mkdir $FG_SRC_DIR/build-sg; cd $FG_SRC_DIR/build-sg
  mkdir $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
  cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
  cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
  make -j2 && make install
  make -j2 && make install
Line 114: Line 114:


=== FlightGear source ===
=== FlightGear source ===
<u>2016.2</u> and <u>next</u>:
<u>2016.4</u> and <u>next</u>:
  cd $FG_SRC_DIR
  cd $FG_SRC_DIR
  <nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>
  <nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>


<u>2016.2</u> only:
<u>2016.4</u> only:
  cd flightgear.git
  cd flightgear.git
  git checkout release/2016.2
  git checkout release/2016.4


<u>2016.2</u> and <u>next</u>:
<u>2016.4</u> and <u>next</u>:
  mkdir $FG_SRC_DIR/build-fg; cd $FG_SRC_DIR/build-fg
  mkdir $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
  cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
  cmake -D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/fgdata" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
  make -j2 && make install
  make -j2 && make install




=== FlightGear data ===
=== FlightGear data ===
<u>2016.2</u> only:  
<u>2016.4</u> only:  
  cd $FG_INSTALL_DIR
  cd $FG_INSTALL_DIR
  <nowiki>wget http://sourceforge.net/projects/flightgear/files/release-2016.2/FlightGear-2016.2.1-data.tar.bz2/download -O FlightGear-2016.2.1-data.tar.bz2</nowiki>
  <nowiki>wget http://sourceforge.net/projects/flightgear/files/release-2016.4/FlightGear-2016.4.2-data.tar.bz2/download -O FlightGear-2016.4.2-data.tar.bz2</nowiki>
  tar xjf FlightGear-2016.2.1-data.tar.bz2
  tar xjf FlightGear-2016.4.2-data.tar.bz2


<u>next</u> only:
<u>next</u> only:
Line 142: Line 142:
When all the builds are done and the data download has finished it is time for a test run:
When all the builds are done and the data download has finished it is time for a test run:
  export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
  export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
  $FG_INSTALL_DIR/bin/fgfs --fg-root=$FG_INSTALL_DIR/fgdata
  $FG_INSTALL_DIR/bin/fgfs --launcher
: 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!).
: 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>$FG_INSTALL_DIR</code> and <code>$FG_SRC_DIR</code> variables are available for this session only. For future use of these lines, replace them by the real paths.
: Have in mind, the <code>$FG_INSTALL_DIR</code> and <code>$FG_SRC_DIR</code> variables are available for this session only. For future use of these lines, replace them by the real paths.
Line 153: Line 153:


== Optional Software ==
== 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.
[[File:Zeichen_101_icon.png|21px]] Some of the below instructions are not up to date. Please feel free to revise them.


Feel free to add the commands to install other FlightGear related projects.
Feel free to add the commands to install other FlightGear related projects.
392

edits