392
edits
Building FlightGear - Devuan: Difference between revisions
Jump to navigation
Jump to search
Update for 2017.3; other plib repo; syntax
(Compile FG 2017.2 on Devuan) |
(Update for 2017.3; other plib repo; syntax) |
||
| Line 1: | Line 1: | ||
HowTo build [[FlightGear]] <u>stable</u> ([[Changelog_2017. | HowTo build [[FlightGear]] <u>stable</u> ([[Changelog_2017.3|2017.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 (<u>Jessie</u>). Users of Testing or Unstable at least have to change package names (version numbering) accordingly.<br /> | ||
Instructions probabaly apply on [https://debian.org/ Debian] GNU/Linux Jessie, too. | Instructions probabaly apply on [https://debian.org/ Debian] GNU/Linux Jessie, 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]]. | <!-- 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 may 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 may cause trouble. | ||
| Line 13: | Line 13: | ||
; Tools | ; Tools | ||
su -c "apt-get install automake cmake g++ gcc git make sed subversion" | su -c "apt-get install automake cmake coreutils g++ gcc git make sed subversion" | ||
| Line 36: | Line 36: | ||
== 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-Stable</code> or <code>$HOME/FG-Stable</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 | 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-Stable</code> or <code>$HOME/FG-Stable</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</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-Stable && mkdir $FG_INSTALL_DIR | export FG_INSTALL_DIR=$HOME/FG-Stable && 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 2.3 GiB (required disk space 4 GiB) / Stable about 1. | 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 [[#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 /> | ||
| Line 51: | Line 51: | ||
=== [[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. | |||
cd $FG_SRC_DIR | cd $FG_SRC_DIR | ||
<nowiki> | <nowiki>git clone https://git.code.sf.net/p/libplib/code libplib.git</nowiki> | ||
cd | cd libplib.git | ||
echo "1.8.6" > version | |||
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h | 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 | |||
make - | cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git | ||
make -j$(nproc) && make install | |||
| Line 68: | Line 70: | ||
<u>Stable</u> only: | <u>Stable</u> only: | ||
cd simgear.git | cd simgear.git | ||
git checkout release/2017. | git checkout release/2017.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 -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git | cmake CFLAGS="--std=c++11" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" \ | ||
make - | $FG_SRC_DIR/simgear.git | ||
make -j$(nproc) && make install | |||
| Line 83: | Line 86: | ||
<u>Stable</u> only: | <u>Stable</u> only: | ||
cd flightgear.git | cd flightgear.git | ||
git checkout release/2017. | git checkout release/2017.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 -D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/fgdata" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git | cmake CFLAGS="--std=c++11" -D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/fgdata" \ | ||
make - | -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git | ||
make -j$(nproc) && make install | |||
| Line 94: | Line 98: | ||
<u>Stable</u> only: | <u>Stable</u> only: | ||
cd $FG_INSTALL_DIR | cd $FG_INSTALL_DIR | ||
<nowiki>wget http://sourceforge.net/projects/flightgear/files/release-2017. | <nowiki>wget http://sourceforge.net/projects/flightgear/files/release-2017.3/FlightGear-2017.3.1-data.tar.bz2/download -O FlightGear-2017.3.1-data.tar.bz2</nowiki> | ||
tar xjf FlightGear-2017. | tar xjf FlightGear-2017.3.1-data.tar.bz2 | ||
<u>next</u> only: | <u>next</u> only: | ||