146
edits
Building FlightGear - Debian: Difference between revisions
Jump to navigation
Jump to search
no edit summary
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. ;-) | ||