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

Difference between revisions of "Building FlightGear - Devuan"

From FlightGear wiki
Jump to: navigation, search
(update for 2018.2)
(Update for 2018.3.2 (OSG v3.4.1))
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
HowTo build [[FlightGear]] <u>Stable</u> ([[Changelog_2018.2|2018.2]]) or bleeding edge development version, hereinafter simply called <u>[[FlightGear_Git#Repositories_and_branches | Next]]</u>, on [https://devuan.org/ Devuan] GNU/Linux Stable (Ascii). Users of Testing or Unstable at least have to change package names (version numbering) accordingly.<br />
+
HowTo build [[FlightGear]] <u>Stable</u> ([[Changelog_2018.3|2018.3]]) or bleeding edge development version, hereinafter simply called <u>[[FlightGear_Git#Repositories_and_branches | Next]]</u>, on [https://devuan.org/ Devuan] GNU/Linux Stable (ASCII). Users of Testing or Unstable at least have to change package names (version numbering) accordingly.<br />
 
Instructions probably apply on [https://debian.org/ Debian] GNU/Linux Stretch, too.
 
Instructions probably apply on [https://debian.org/ Debian] GNU/Linux Stretch, too.
  
 
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 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 most of the here used commands will cause trouble.
 
[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the here used commands will cause trouble.
Line 18: Line 16:
 
; Dependencies
 
; Dependencies
 
  su -c "apt-get install  \
 
  su -c "apt-get install  \
   freeglut3-dev       libboost-dev  libcurl4-openssl-dev  libdbus-1-dev \
+
   freeglut3-dev         libopenscenegraph-dev  qml-module-qtquick-window2 \
   libfreetype6-dev    libglew-dev   libopenal-dev libopenscenegraph-dev \
+
  libboost-dev          libqt5opengl5-dev      qt5-default \
   libqt5opengl5-dev   libxi-dev     libxmu-dev             pkg-config \
+
  libcurl4-openssl-dev  libqt5svg5-dev          qtbase5-private-dev \
   qml-module-qtquick2                qml-module-qtquick-window2 \
+
   libdbus-1-dev         libxi-dev               qtdeclarative5-private-dev \
   qt5-default        qtbase5-private-dev     qtdeclarative5-private-dev"
+
   libfreetype6-dev       libxmu-dev             qttools5-dev \
 +
   libglew-dev            pkg-config \
 +
   libopenal-dev         qml-module-qtquick2"
  
 
: 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".
  
: [[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".
+
: [[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", "libopenscenegraph-3.4-dev", "libopenscenegraph-dev" and "simgear-dev".
  
  
Line 45: Line 45:
 
=== [[plib]] ===
 
=== [[plib]] ===
 
<u>Stable</u> and <u>Next</u>: <br />
 
<u>Stable</u> and <u>Next</u>: <br />
While just installing package "libplib-dev" should work, it's  [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source.
+
While just installing package "libplib-dev" should work, it's  [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source. In this case "libplib-dev" ''must not'' be installed!
 
  cd $FG_SRC_DIR
 
  cd $FG_SRC_DIR
 
  <nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
 
  <nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
Line 54: Line 54:
 
  mkdir $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
 
  mkdir $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
 
  cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
 
  cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
 +
make -j$(nproc) && make install
 +
 +
 +
=== [[OpenSceneGraph]] ===
 +
<u>Stable</u> and <u>Next</u>: <br />
 +
Recommended version is 3.4.1 while the Devuan/Debian repo provides only 3.4.0. Plus, at this time, SimGear does not compile against 3.4.0 so we have to compile it ourselfes.
 +
 +
cd $FG_SRC_DIR
 +
<nowiki>git clone --branch OpenSceneGraph-3.4.1 git://github.com/openscenegraph/OpenSceneGraph.git OpenSceneGraph.git</nowiki>
 +
mkdir $FG_SRC_DIR/build-osg && cd $FG_SRC_DIR/build-osg
 +
cmake -D LIB_POSTFIX="" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/OpenSceneGraph.git
 
  make -j$(nproc) && make install
 
  make -j$(nproc) && make install
  
Line 64: Line 75:
 
<u>Stable</u> only:
 
<u>Stable</u> only:
 
  cd simgear.git
 
  cd simgear.git
  git checkout release/2018.2
+
  git checkout release/2018.3
  
 
<u>Stable</u> and <u>Next</u>:
 
<u>Stable</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 CFLAGS="--std=c++11" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" \
+
  cmake CFLAGS="--std=c++11" -D CMAKE_BUILD_TYPE=Release \
      $FG_SRC_DIR/simgear.git
+
      -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
 
  make -j$(nproc) && make install
 
  make -j$(nproc) && make install
  
Line 80: Line 91:
 
<u>Stable</u> only:
 
<u>Stable</u> only:
 
  cd flightgear.git
 
  cd flightgear.git
  git checkout release/2018.2
+
  git checkout release/2018.3
  
 
<u>Stable</u> and <u>Next</u>:
 
<u>Stable</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 CFLAGS="--std=c++11" -D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" \
+
  cmake CFLAGS="--std=c++11" -D CMAKE_BUILD_TYPE=Release \
 +
      -D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" \
 
       -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
 
       -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
 
  make -j$(nproc) && make install
 
  make -j$(nproc) && make install
Line 96: Line 108:
 
<u>Stable</u> only:
 
<u>Stable</u> only:
 
  cd fgdata
 
  cd fgdata
  git checkout release/2018.2
+
  git checkout release/2018.3
  
  

Latest revision as of 08:41, 5 February 2019

HowTo build FlightGear Stable (2018.3) or bleeding edge development version, hereinafter simply called Next, on Devuan GNU/Linux Stable (ASCII). Users of Testing or Unstable at least have to change package names (version numbering) accordingly.
Instructions probably apply on Debian GNU/Linux Stretch, too.

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

Zeichen 144 icon.png For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the here used commands will 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 cmake g++ gcc git make sed"


Dependencies
su -c "apt-get install  \
  freeglut3-dev          libopenscenegraph-dev   qml-module-qtquick-window2 \
  libboost-dev           libqt5opengl5-dev       qt5-default \
  libcurl4-openssl-dev   libqt5svg5-dev          qtbase5-private-dev \
  libdbus-1-dev          libxi-dev               qtdeclarative5-private-dev \
  libfreetype6-dev       libxmu-dev              qttools5-dev \
  libglew-dev            pkg-config \
  libopenal-dev          qml-module-qtquick2"
If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".
Zeichen 144 icon.png 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", "libopenscenegraph-3.4-dev", "libopenscenegraph-dev" and "simgear-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 /usr/local/FG-Stable or $HOME/FG-Stable. 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 make commands. We'll use $FG_INSTALL_DIR as a placeholder for this directory.
Another placeholder will be $FG_SRC_DIR, 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 export them (in every terminal you're using them) for the process:

export FG_INSTALL_DIR=$HOME/FG-Stable && 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 2.3 GiB (required disk space 4 GiB) / Stable about 1.5 GiB). So, to save some time, it is a good idea to fetch it while building the sources.
For some basic info on git commands for FlightGear users we have a git for laymen section.

For more/advanced cmake options and SimGear's and FlightGear's optional features see the cmake article.

Zeichen 144 icon.png Do not mix instructions for Stable and Next! Not even for fgdata, mixing versions will almost certainly break the installation.


plib

Stable and Next:
While just installing package "libplib-dev" should work, it's recommended to build it from source. In this case "libplib-dev" must not be installed!

cd $FG_SRC_DIR
git clone git://git.code.sf.net/p/libplib/code libplib.git
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc) && make install


OpenSceneGraph

Stable and Next:
Recommended version is 3.4.1 while the Devuan/Debian repo provides only 3.4.0. Plus, at this time, SimGear does not compile against 3.4.0 so we have to compile it ourselfes.

cd $FG_SRC_DIR
git clone --branch OpenSceneGraph-3.4.1 git://github.com/openscenegraph/OpenSceneGraph.git OpenSceneGraph.git
mkdir $FG_SRC_DIR/build-osg && cd $FG_SRC_DIR/build-osg
cmake -D LIB_POSTFIX="" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/OpenSceneGraph.git
make -j$(nproc) && make install


SimGear

Stable and Next:

cd $FG_SRC_DIR
git clone git://git.code.sf.net/p/flightgear/simgear simgear.git

Stable only:

cd simgear.git
git checkout release/2018.3

Stable and Next:

mkdir $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
cmake CFLAGS="--std=c++11" -D CMAKE_BUILD_TYPE=Release \
      -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j$(nproc) && make install


FlightGear source

Stable and Next:

cd $FG_SRC_DIR
git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git

Stable only:

cd flightgear.git
git checkout release/2018.3

Stable and Next:

mkdir $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
cmake CFLAGS="--std=c++11" -D CMAKE_BUILD_TYPE=Release \
      -D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" \
      -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc) && make install


FlightGear data

Stable and Next:

mkdir -p $FG_INSTALL_DIR/share && cd $FG_INSTALL_DIR/share
git clone git://git.code.sf.net/p/flightgear/fgdata fgdata

Stable only:

cd fgdata
git checkout release/2018.3


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=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
The fgfs 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 $HOME/.bashrc to have this as a persistent setting (may cause problems, if one has installed more than one version of FlightGear!).
Have in mind, the $FG_INSTALL_DIR and $FG_SRC_DIR 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 fgfs command each time, you might consider to create a symlink at a place that is listed in $PATH:

ln -s $FG_INSTALL_DIR/bin/fgfs $HOME/bin/fgfs