Building FlightGear - Debian: Difference between revisions
Fahim Dalvi (talk | contribs) No edit summary |
|||
Line 1: | Line 1: | ||
= HowTo build on Debian = | = HowTo build on Debian = | ||
HowTo build FlightGear 2.0.0 or | HowTo build FlightGear 2.0.0 or GIT on GNU/Linux Debian '''Stable''' 5.x (Lenny). | ||
This HowTo may also work with '''Testing'''/'''Unstable''' except that some things are easier because of more up to date packages. So, before fetching something check the version of the available -dev package for it. | This HowTo may also work with '''Testing'''/'''Unstable''' except that some things are easier because of more up to date packages. So, before fetching something check the version of the available -dev package for it. | ||
Line 17: | Line 17: | ||
*mawk (or gawk) | *mawk (or gawk) | ||
*cmake (min. version 2.6.0-5, for Etch available on backports.org!) | *cmake (min. version 2.6.0-5, for Etch available on backports.org!) | ||
* | *git, subversion, wget | ||
<!--*libsvn-dev, for [[Terrasync]]s proper operation.--> | <!--*libsvn-dev, for [[Terrasync]]s proper operation.--> | ||
*freeglut3-dev, libgl1-mesa-dev, libxrandr-dev | *freeglut3-dev, libgl1-mesa-dev, libxrandr-dev | ||
Line 29: | Line 29: | ||
== Build and install == | == Build and install == | ||
Because we are going to install versions different to the ones in the repositries it is recommended to install FG-2.0.0 and/or | Because we are going to install versions different to the ones in the repositries it is recommended to install FG-2.0.0 and/or GIT in a place independent to the base system such as /usr/local/FG-2.0.0, /opt/FG-2.0.0 or in a subdirectory of your $HOME. I suggest to make it writeable by the user that there is no need to become root for the <code>make install</code> commands. I'll use <code>$prefix</code> as a placeholder for this directory. <BR> | ||
Another one will be <code>$srcdir</code>, it stands for the absolute path to the directory which contains the folders of the various source codes. So in the following instructions you have to replace these with the local paths or even <code>export</code> them during the process. | Another one will be <code>$srcdir</code>, it stands for the absolute path to the directory which contains the folders of the various source codes. So in the following instructions you have to replace these with the local paths or even <code>export</code> them during the process. | ||
Follow the instructions to fetch the sources and the data needed by FlightGear and the commands to build/install each source. | Follow the instructions to fetch the sources and the data needed by FlightGear and the commands to build/install each source. | ||
Have in mind that the data is relatively large ( | Have in mind that the data is relatively large (GIT about 3.5 GB and 2.0.0 300 MB) so, to save some time, it is a good idea to fetch it while building the sources. | ||
Line 68: | Line 68: | ||
For FlightGear 2.0.0 one may use the latest (or at least 2.9.6) developer release from http://www.openscenegraph.org/projects/osg/wiki/Downloads/DeveloperReleases and extract it into <code>$srcdir</code>. | For FlightGear 2.0.0 one may use the latest (or at least 2.9.6) developer release from http://www.openscenegraph.org/projects/osg/wiki/Downloads/DeveloperReleases and extract it into <code>$srcdir</code>. | ||
Mostly this is ok for FlightGear | Mostly this is ok for FlightGear GIT as well as it is stable. However, sometimes the release is not fresh enough and one have to get the latest developments via SVN: | ||
cd $srcdir | cd $srcdir | ||
svn co http://www.openscenegraph.org/svn/osg/OpenSceneGraph/trunk OpenSceneGraph | svn co http://www.openscenegraph.org/svn/osg/OpenSceneGraph/trunk OpenSceneGraph | ||
Line 85: | Line 85: | ||
cd SimGear-2.0.0 | cd SimGear-2.0.0 | ||
GIT: | |||
cd $srcdir | cd $srcdir | ||
git clone git://gitorious.org/fg/simgear.git simgear | git clone git://gitorious.org/fg/simgear.git simgear | ||
Line 91: | Line 91: | ||
./autogen.sh | ./autogen.sh | ||
2.0.0 and | 2.0.0 and GIT: | ||
./configure --prefix=$prefix [CPPFLAGS=-I$prefix/include LDFLAGS="-L$prefix/lib -L$prefix/lib64"] | ./configure --prefix=$prefix [CPPFLAGS=-I$prefix/include LDFLAGS="-L$prefix/lib -L$prefix/lib64"] | ||
make install | make install | ||
Line 102: | Line 102: | ||
cd FlightGear-2.0.0 | cd FlightGear-2.0.0 | ||
GIT: | |||
cd $srcdir | cd $srcdir | ||
git clone git://gitorious.org/fg/flightgear.git flightgear | git clone git://gitorious.org/fg/flightgear.git flightgear | ||
Line 108: | Line 108: | ||
./autogen.sh | ./autogen.sh | ||
2.0.0 and | 2.0.0 and GIT: | ||
./configure --prefix=$prefix [CPPFLAGS=-I$prefix/include/ LDFLAGS="-L$prefix/lib -L$prefix/lib64"] | ./configure --prefix=$prefix [CPPFLAGS=-I$prefix/include/ LDFLAGS="-L$prefix/lib -L$prefix/lib64"] | ||
make install | make install | ||
Line 163: | Line 163: | ||
<!--== Keeping the | <!--== Keeping the GIT version up to date == | ||
...to be continued. ;-) | ...to be continued. ;-) |
Revision as of 18:29, 7 August 2010
HowTo build on Debian
HowTo build FlightGear 2.0.0 or GIT on GNU/Linux Debian Stable 5.x (Lenny).
This HowTo may also work with Testing/Unstable except that some things are easier because of more up to date packages. So, before fetching something check the version of the available -dev package for it.
It even *should* work with Etch, but I am not certain about some dependencies. Reports are welcome.
If you don't want to make your hands dirty, have a look at Scripted_Compilation_on_Linux_Debian/Ubuntu.
Requirements and Preparations
You need an OpenGL capable graphics including a proper installed driver.
Also a bunch of packages (and some of their dependencies) are required:
- gcc, g++, make, automake1.9, pkg-config
- mawk (or gawk)
- cmake (min. version 2.6.0-5, for Etch available on backports.org!)
- git, subversion, wget
- freeglut3-dev, libgl1-mesa-dev, libxrandr-dev
- libxi-dev, libxmu-dev, libxext-dev
- libopenal-dev (see libopenal), libalut-dev
- libjpeg62-dev, libtiff4-dev, libpng12-dev
- libboost1.37-dev (Not available for Lenny atm, see Boost Library below.)
During installation packages simgear-dev and openscenegraph-dev *must not* be installed. They can safely be re-installed after compilation.
Build and install
Because we are going to install versions different to the ones in the repositries it is recommended to install FG-2.0.0 and/or GIT in a place independent to the base system such as /usr/local/FG-2.0.0, /opt/FG-2.0.0 or in a subdirectory of your $HOME. I suggest to make it writeable by the user that there is no need to become root for the make install
commands. I'll use $prefix
as a placeholder for this directory.
Another one will be $srcdir
, it stands for the absolute path to the directory which contains the folders of the various source codes. So in the following instructions you have to replace these with the local paths or even export
them during the process.
Follow the instructions to fetch the sources and the data needed by FlightGear and the commands to build/install each source.
Have in mind that the data is relatively large (GIT about 3.5 GB and 2.0.0 300 MB) so, to save some time, it is a good idea to fetch it while building the sources.
libopenal
The libopenal-dev package in Lenny/Etch is too old for fgcom. For FlightGear it does work but not all features (like Doppler) are available, so installing an up to date version is recommended anyway.
cd $srcdir wget http://kcat.strangesoft.net/openal-releases/openal-soft-1.11.753.tar.bz2 tar xjf openal-soft-1.11.753.tar.bz2 cd openal-soft-1.11.753/build cmake -D CMAKE_INSTALL_PREFIX:PATH="$prefix" .. make install
plib
Latest SVN is recommended, yet package plib1.8.5-dev for Testing/Unstable does work as well.
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 install
Boost Library
Version 1.37 is needed. At least for Lenny/Etch this means getting the sources because this is not available atm on backports.org. Testing/Unstable users may have more luck and a package is available, libboost-1.37-dev or newer.
To build SimGear, FlightGear, fgrun and fgcom some boostlib header files are required, no need to compile and install it. If you have installed a libboost1.37-dev (or higher) package on your system you don't have to bother at all with it. If not, you have to tell each ./configure where the header files are. To do so, add the option CPPFLAGS=-I$prefix/include
to the SimGear, FlightGear and fgrun ./configure
commands. We copy the header files to $prefix/include because fgcom will need them there.
Get the newest version tar ball from http://sourceforge.net/projects/boost/files/boost/, extract it into $srcdir
then:
cp -R $srcdir/boost-[version]/boost/ $prefix/include/
OpenSceneGraph
For FlightGear 2.0.0 one may use the latest (or at least 2.9.6) developer release from http://www.openscenegraph.org/projects/osg/wiki/Downloads/DeveloperReleases and extract it into $srcdir
.
Mostly this is ok for FlightGear GIT as well as it is stable. However, sometimes the release is not fresh enough and one have to get the latest developments via SVN:
cd $srcdir svn co http://www.openscenegraph.org/svn/osg/OpenSceneGraph/trunk OpenSceneGraph
cmake demands a build directory separate to its source directory. So mkdir
one and cd
into it.
cmake -D CMAKE_BUILD_TYPE="Release" -D CMAKE_CXX_FLAGS="-O3" -D CMAKE_C_FLAGS="-O3" \ -D CMAKE_INSTALL_PREFIX:PATH="$prefix" $srcdir/OpenSceneGraph[-version] make install
SimGear
2.0.0:
cd $srcdir wget http://mirrors.ibiblio.org/pub/mirrors/simgear/ftp/Source/SimGear-2.0.0.tar.gz tar xzf SimGear-2.0.0.tar.gz cd SimGear-2.0.0
GIT:
cd $srcdir git clone git://gitorious.org/fg/simgear.git simgear cd simgear ./autogen.sh
2.0.0 and GIT:
./configure --prefix=$prefix [CPPFLAGS=-I$prefix/include LDFLAGS="-L$prefix/lib -L$prefix/lib64"] make install
FlightGear source
2.0.0:
cd $srcdir wget http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Source/FlightGear-2.0.0.tar.gz tar xzf FlightGear-2.0.0.tar.gz cd FlightGear-2.0.0
GIT:
cd $srcdir git clone git://gitorious.org/fg/flightgear.git flightgear cd flightgear ./autogen.sh
2.0.0 and GIT:
./configure --prefix=$prefix [CPPFLAGS=-I$prefix/include/ LDFLAGS="-L$prefix/lib -L$prefix/lib64"] make install
FlightGear data
2.0.0:
cd $prefix wget http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Shared/FlightGear-data-2.0.0.tar.bz2 tar xjf FlightGear-data-2.0.0.tar.bz2
GIT:
cd $prefix git clone git://gitorious.org/fg/fgdata.git data
Or to Fetch A bundle that can be Downloaded in parts :
cd $prefix wget http://peter-server.homelinux.net/fgdata/fgdata/fgdata.bundle
or
cd $prefix wget http://flightgear.mxchange.org/pub/fgfs/fgdata.bundle
the MD5 checksum is
2996221BD2B8AB7740F332F49396CF56
Trial run
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
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 compiling fgrun. Have in mind that fgfs need to find our self compiled libraries and therefore we have to tell the linker (ld) where to find them. That is what the first line here does.
Optional Software
fgrun
To build fgrun two more package is required:
- libfltk1.1-dev fluid
cd $srcdir svn co http://fgrun.svn.sourceforge.net/svnroot/fgrun/trunk fgrun cd fgrun/fgrun/ ./autogen.sh ./configure --prefix=$prefix [CPPFLAGS=-I$prefix/include/] make install
fgcom
For fgcom unfortunately there is one more dependency which cannot be solved with packages on Lenny/Etch, see libopenal.
cd $srcdir svn co https://appfgcom.svn.sourceforge.net/svnroot/fgcom/trunk fgcom cd fgcom/src make INSTALL_BIN=$prefix/bin INSTALL_DIR=$prefix/fgcom \ PLIB_PREFIX=$prefix OPENAL_PREFIX=$prefix install
|