406
edits
Building FlightGear - Devuan: Difference between revisions
Jump to navigation
Jump to search
m
FG-OSG branch selection and fixed a broken link.
m (OSG branch and libc-ares-dev) |
m (FG-OSG branch selection and fixed a broken link.) |
||
| Line 24: | Line 24: | ||
== Build and install == | == Build and install == | ||
Some things require customisation. We'll use [ | Some things require customisation. We'll use [https://wiki.debian.org/EnvironmentVariables environment variables] for them: <br /> | ||
: '''FG_VERSION''' – The version of FlightGear to build and install. This is either <code>next</code> (for the bleeding edge development branch) or a release number in the form <code>release/ | : '''FG_VERSION''' – The version of FlightGear to build and install. This is either <code>next</code> (for the bleeding edge development branch) or a release number in the form <code>release/2024.1</code>. For a list of valid releases see [https://sourceforge.net/p/flightgear/flightgear/ref/next/branches/ here]. <br /> | ||
: '''FG_SRC_DIR''' – The absolute path to the directory which is supposed to hold the source codes. In case your user belongs to the group ''staff'', <code>/usr/local/src/</code> would be an appropriate location. But any location is fine, too, e.g. <code>$HOME/src/</code>. In any case the user has to have write access there.<br /> | : '''FG_SRC_DIR''' – The absolute path to the directory which is supposed to hold the source codes. In case your user belongs to the group ''staff'', <code>/usr/local/src/</code> would be an appropriate location. But any location is fine, too, e.g. <code>$HOME/src/</code>. In any case the user has to have write access there.<br /> | ||
: '''FG_INSTALL_DIR''' – The absolute path to where FlightGear is going to be installed. Again, <code>/usr/local/</code> is appropriate, if your user belongs to ''staff''. But any location where the user has write access is ok, e.g. <code>$HOME/FlightGear/</code>. <br /> | : '''FG_INSTALL_DIR''' – The absolute path to where FlightGear is going to be installed. Again, <code>/usr/local/</code> is appropriate, if your user belongs to ''staff''. But any location where the user has write access is ok, e.g. <code>$HOME/FlightGear/</code>. <br /> | ||
# Examples, adapt to your own needs: | # Examples, adapt to your own needs: | ||
export FG_VERSION=release/2024.1 | export FG_VERSION=release/2024.1 #OR# export FG_VERSION=next | ||
export FG_SRC_DIR=$HOME/src/ | export FG_SRC_DIR=$HOME/src/ | ||
export FG_INSTALL_DIR=$HOME/FlightGear/ | export FG_INSTALL_DIR=$HOME/FlightGear/ | ||
| Line 59: | Line 59: | ||
=== [[OpenSceneGraph]] === | === [[OpenSceneGraph]] === | ||
To compile FlightGear release version branch <code>release/2024-build</code> is required, for FlightGear next branch <code>fgfs-osg-36-2</code>. | |||
export FG_OSG_VERSION=release/2024-build #OR# export FG_OSG_VERSION=fgfs-osg-36-2 | |||
cd $FG_SRC_DIR | cd $FG_SRC_DIR | ||
<nowiki>git clone https://gitlab.com/flightgear/openscenegraph.git FG-OpenSceneGraph.git</nowiki> | <nowiki>git clone https://gitlab.com/flightgear/openscenegraph.git FG-OpenSceneGraph.git</nowiki> | ||
cd FG-OpenSceneGraph.git | cd FG-OpenSceneGraph.git | ||
git checkout | git checkout $FG_OSG_VERSION | ||
mkdir -p $FG_SRC_DIR/build-osg && cd $FG_SRC_DIR/build-osg | mkdir -p $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/FG-OpenSceneGraph.git | cmake -D LIB_POSTFIX="" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/FG-OpenSceneGraph.git | ||