392
edits
m (minor update/corrections) |
(some updates for FG-2.0.0) |
||
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!) | ||
*cvs, subversion, | *cvs, 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 30: | Line 30: | ||
== 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 CVS 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> | 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 CVS 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 one have to replace these by the local paths. | 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 one have to replace these by the local paths or even <code>export</code> them during the process. | ||
Subsequent the instructions to fetch the sources and the data needed by | Subsequent 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 huge (CVS about 2 GB and 2.0.0 | Have in mind that the data is relatively huge (CVS about 2 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 === | === libopenal === | ||
The libopenal-dev package in Lenny/Etch is too old for fgcom. For | The libopenal-dev package in Lenny/Etch is too old for [[fgcom]]. For FlightGear it does work but not all features (like Doppler) are avaiable, so installing an up to date version is recommended anyway. | ||
cd $srcdir | cd $srcdir | ||
wget http:// | wget http://kcat.strangesoft.net/openal-releases/openal-soft-1.11.753.tar.bz2 | ||
tar xjf openal-soft- | tar xjf openal-soft-1.11.753.tar.bz2 | ||
cd openal-soft- | cd openal-soft-1.11.753/build | ||
cmake -D CMAKE_INSTALL_PREFIX:PATH="$prefix" .. | cmake -D CMAKE_INSTALL_PREFIX:PATH="$prefix" .. | ||
make install | make install | ||
Line 48: | Line 48: | ||
=== plib === | === plib === | ||
Latest SVN is [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended], yet package plib1.8.5-dev for Testing/Unstable does work as well. | |||
cd $srcdir | 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 | ./configure --prefix=$prefix | ||
make install | make install | ||
Line 82: | Line 83: | ||
2.0.0: | 2.0.0: | ||
cd $srcdir | cd $srcdir | ||
wget | wget http://mirrors.ibiblio.org/pub/mirrors/simgear/ftp/Source/SimGear-2.0.0.tar.gz | ||
tar ... | tar xzf SimGear-2.0.0.tar.gz | ||
cd .. | cd SimGear-2.0.0 | ||
CVS: | CVS: | ||
Line 94: | Line 95: | ||
cvs -d :pserver:cvsguest@cvs.simgear.org:/var/cvs/SimGear-0.3 co source | cvs -d :pserver:cvsguest@cvs.simgear.org:/var/cvs/SimGear-0.3 co source | ||
cd source | cd source | ||
./autogen.sh | |||
2.0.0 and CVS: | 2.0.0 and CVS: | ||
./configure --prefix=$prefix [CPPFLAGS=-I$prefix/include] | ./configure --prefix=$prefix [CPPFLAGS=-I$prefix/include] | ||
make install | make install | ||
Line 104: | Line 105: | ||
2.0.0: | 2.0.0: | ||
cd $srcdir | cd $srcdir | ||
wget http:// | wget http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Source/FlightGear-2.0.0.tar.gz | ||
tar | tar xzf FlightGear-2.0.0.tar.gz | ||
cd .. | cd FlightGear-2.0.0 | ||
CVS: | CVS: | ||
Line 116: | Line 117: | ||
cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 co source | cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 co source | ||
cd source | cd source | ||
./autogen.sh | |||
2.0.0 and CVS: | 2.0.0 and CVS: | ||
./configure --prefix=$prefix [CPPFLAGS=-I$prefix/include/] | ./configure --prefix=$prefix [CPPFLAGS=-I$prefix/include/] | ||
make install | make install | ||
Line 125: | Line 126: | ||
=== FlightGear data === | === FlightGear data === | ||
2.0.0: | 2.0.0: | ||
cd $prefix | cd $prefix | ||
wget http:// | wget http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Shared/FlightGear-data-2.0.0.tar.bz2 | ||
tar xjf ... | tar xjf FlightGear-data-2.0.0.tar.bz2 | ||
CVS: | CVS: | ||
cd $prefix | cd $prefix | ||
cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 co data | cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 co data | ||
Line 136: | Line 138: | ||
When all the builds are done and the data download has finished it is time for a test 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 | export LD_LIBRARY_PATH=$prefix/lib/:$LD_LIBRARY_PATH | ||
$prefix/bin/fgfs --fg-root=$prefix | $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 [[#fgrun|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. | 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 [[#fgrun|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. | ||
Line 150: | Line 152: | ||
svn co http://fgrun.svn.sourceforge.net/svnroot/fgrun/trunk fgrun | svn co http://fgrun.svn.sourceforge.net/svnroot/fgrun/trunk fgrun | ||
cd fgrun | cd fgrun | ||
./autogen.sh | ./autogen.sh | ||
./configure --prefix=$prefix [CPPFLAGS=-I$prefix/include/] | ./configure --prefix=$prefix [CPPFLAGS=-I$prefix/include/] | ||
Line 157: | Line 158: | ||
=== fgcom === | === fgcom === | ||
For [[ | For [[fgcom]] unfortunately there is one more dependency which cannot be solved with packages on Lenny/Etch, see [[#libopenal|libopenal]]. | ||
cd $srcdir | cd $srcdir | ||
svn co https://appfgcom.svn.sourceforge.net/svnroot/fgcom/trunk fgcom | svn co https://appfgcom.svn.sourceforge.net/svnroot/fgcom/trunk fgcom | ||
cd fgcom/src | cd fgcom/src | ||
make INSTALL_BIN=$prefix/bin INSTALL_DIR=$prefix/fgcom \ | make INSTALL_BIN=$prefix/bin INSTALL_DIR=$prefix/fgcom \ | ||
PLIB_PREFIX=$prefix OPENAL_PREFIX=$prefix install | PLIB_PREFIX=$prefix OPENAL_PREFIX=$prefix install | ||
== Keeping the CVS version up to date == | <!--== Keeping the CVS version up to date == | ||
...to be continued. ;-) | ...to be continued. ;-) | ||
--> | |||
edits