Building FlightGear - Linux

926 bytes added, 17 January
Add CentOS
{{Main article|Building Flightgear}}
This section describes how to build [[FlightGear]] on Linux system.
Compiling FlightGear is not a task for novice users. Thus, if you're a beginner (we all were once) on a platform which binaries are available for, we recommend postponing this task and just starting with the binary distribution to get you flying.
openSUSE also provides binary packages of the latest development version, which are continuously updated.
Follow [ this link] to select your openSUSE version and install, or manually add ''games:FlightGear:Unstable'' to your ''YaST Software Repositories''.
For Ubuntu, there is a PPA that provides the latest development version of FlightGear and SimGear and a recent version of FlightGear data. See [ this page] for more info. To add the PPA, run <tt>sudo apt-add-repository ppa:saiarcot895/flightgear-edge</tt>.
Or if you develop on Ubuntu or Debian, consider trying the script described in [[Scripted Compilation on Linux Debian/Ubuntu]].
== Distro-specific instructions ==
=== Debian/Ubuntu ===
* You can use the [[Scripted Compilation on Linux Debian/Ubuntu]] script to have Flightgear compiled in one shot under both Ubuntu and Debian systems.
* Debian users who prefer to build it without script may look at [[Building Flightgear - Debian]].
* Hints for [[Ubuntu]] users.
=== Gentoo ===
* Gentoo users can also use overlays to build FlightGear without much hassle: [[Building Flightgear - Gentoo]].
=== CentOS ===
CentOS users can follow these instructions to build FlightGear on [[Building Flightgear - CentOS | CentOS 8]].
== Requirements ==
{{Note|as of 12/2017, people may have to build using at least OSG 3.4 due to some compilation issues -for details, refer to [[Howto:Building FlightGear without HiDPI support]]}}
Edit 12/9/15 - These instructions are out of date! Do not use for compiling.
Before you can compile FlightGear, you need to have the following installed on your computer:
'''C++ compiler'''
These are: c++, cpp, gcc, g++ found under the <code>/usr/bin </code> directory. You will also need to have the tools '''autoconf''' and '''automake1.9''' installed.
More specifically, your system needs the support for hardware accelerated graphics. You can check for this by running the following in a [[command line]]:
<syntaxhighlight lang="bash">$ glxinfo | grep direct</syntaxhighlight>
Note: To run the above command, you need to have the tool '''mesa-utils''' installed.
direct rendering: No
Don't panic yet. This may just mean some required libraries for hardware accelerated graphic are missing. Go ahead and try installing '''plib 1.8.5 ''' and its dependencies first. If you still get the above message, then you will need to do some googling and troubleshoot yourself.
== Dependencies ==
 FlightGear is dependent on quite a few number of libraries. You do not need to compile all of them yourself, but you will at least need to have their development version installed. For example, the development version for package <tt>plib1.8.5 </tt> is <tt>plib1.8.5</tt>'''-dev'''.
The dependency is summarized in the following tree. Please note that each library has its own dependencies, and most of these are not shown here.
* <tt>FlightGear</tt>** [ <tt>OpenAL</tt>]** <tt>SimGear</tt>*** [ <tt>PLIB</tt>]. Since march March 2008, you will need version 1.8.5 - your distro probably supplies 1.8.4 still.**** For versions pre march/March 2008: (Free)<tt>GLUT </tt> or <tt>SDL </tt> (We recommend the use of <tt>SDL </tt> over <tt>Free/GLUT</tt>, [ however since march March 2008, <tt>FreeGLUT </tt> as well as <tt>SDL </tt> are both considered depreciateddeprecated], please only use <code>--enable-osgviewer </code> during configuration instead]) *** <tt>[[ OpenSceneGraph ]] </tt> (The latest development release or svn trunk check link for FlightGear/Git and the latest preceding OSG release for a FlightGear releasecompatible versions)
*** You also need the development files for several basic libraries to build the software, among them the following (the package names are for Debian and derivatives(?)):
**** <tt>libfreetype6-dev</tt>**** <tt>libjpeg62-dev</tt>**** <tt>libungif4-dev</tt>**** <tt>libtiff4-dev</tt>**** <tt>libpng12-dev</tt>**** <tt>libxmu-dev</tt>**** <tt>libxi-dev</tt>**** <tt>zlib1g-dev</tt>**** <tt>libglut3-dev</tt>
If you attack the above dependencies in the order listed below, you should be good:
1. Glut. # <tt>glut</tt> Most distributions include glut packages, although you may have to hunt for them. Make sure you install both the <tt>glut </tt> and <tt>glut-devel </tt> packages, otherwise FlightGear may be able to compile but won't run correctly. 2. Zlib. # <tt>zlib</tt> Most distributions install the basic <tt>zlib </tt> libraries by default, but not the development portions. If you don't have <tt>zlib.h</tt>, you probably need to install the <tt>zlib-devel </tt> package for your distribution.  3. Plib - portability # <tt>plib</tt> Portability libraries and scene graph.  4. # <tt>[[ OpenSceneGraph ]]</tt>  5. SimGear - # <tt>simgear</tt> Simulation support libraries. If you are building FlightGear from Git, you need the Git version of SimGear. If you have strange build errors, one of the first things to check is that you have an up-to-date version of SimGear built and installed. ==== APT-GET List ====This is a list of all the apt-get commands I had to do while compiling FG, SG, and OSG on a mostly clean Ubuntu 64 system. It is a list of all the libraries you and your computer needs to compile FG, SG, OSG, and PLib. All you have to do is copy the full command, paste it in Terminal, enter your password, and it will download all the packages for you, and install them too. The full command is at the bottom, and I hope someone finds it useful :) sub-dependencies (dependencies of the dependencies) are not included as they are installed automatically by apt-get. If anyone sees something missing, please add it. git - to get SG and FG <br>subversion - to get OSG <br>build-essential - to build (includes GCC, and other build tools) <br>cmake - OSG Uses this <br>ccmake-curses-gui -- OSG Uses this <br>libpng-dev - to enable FG to use PNG textures<br>libfreetype6-dev - fonts<br>libjpeg-dev<br>libungif4-dev<br>libtiff-dev<br>libxmu-dev<br>libxi-dev<br>libglut3-dev<br>libalut-dev - sound<br>libboost-dev - makes coding for some developers easier<br>automake - needed by ./ files<br>autoconf - needed by ./ files<br>libfltk1.1-dev - You will need this if you will be using FGRun<br>-----------<pre>sudo apt-get install git subversion build-essential cmake libpng-dev libfreetype6-devlibjpeg-dev libungif4-dev libtiff-dev libxmu-dev libxi-dev libglut3-dev libalut-devlibboost-dev automake autoconf libfltk1.1-dev</pre>-----------Total size is about 230 MB, depending on what you already have from other applications. This list might seem a bit short, but the sub-dependencies all add up :) The dependencies will be listed by apt-get when you use the command.
== Compiling ==
Assuming you are root, do:
cd /usr/local/src
<bsyntaxhighlight lang="bash">Note:# cd /usr/local/src</bsyntaxhighlight>  '''Note:''' When tracking a fast changing software like FlightGear/Git it is highly advisable to install it in a separate directory. That way one can also easily build and reinstall without being root, which greatly reduces the risk of messing up one's system.
To install in a directory of your choice add the <tt>--prefix</tt> argument to configure. E.g. <tt>./configure --prefix=$HOME/FlightGear</tt>. I would recommend installing all of OSG, plib, SimGear and FlightGear with the same prefix.
Clone the SimGear git repository and set it up to track the 'next' branch.
git clone git://
<syntaxhighlight lang="bash">$ git clone git:// simgear</syntaxhighlight> or if the git port is firewalled on you network, use the http transport <syntaxhighlight lang="bash">$ git clone simgear</syntaxhighlight> By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with <code>git pull</code>.
'''Step 2:'''
Next, go into the directory and make preparations for the compilation:
cd simgear
<syntaxhighlight lang="bash">$ cd simgear$ cmake .</syntaxhighlight> '''Note''' that if you don't want to install <tt>simgear </tt> globally on the system but in a specific directory, you can do so by adding <code>--prefixDCMAKE_INSTALL_PREFIX=/path/to/your/fgInstallation </code> to the .<code>cmake</configure code> command
'''Step 3:'''
Compile and install SimGear by doing:
make; make install
<syntaxhighlight lang="bash">
$ make; make install
''Note:'' with <tt>gcc </tt> 4.2 or later,on some platforms, you can get compiling errors about <tt>alc.h </tt> like:
'<anonymous>' has incomplete type
Clone the FlightGear git repository and set it up to track the 'next' branch.
<syntaxhighlight lang="bash">$ git clone git://</syntaxhighlight>
By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with git pull.
Next, go into the folder and make preparations for the compilation:
<syntaxhighlight lang="bash">$ cd flightgear $ ./ $ ./configure</syntaxhighlight>
Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command.
If you didn't install OSG globally or in the same prefix as SimGear and FlightGear, you have to pass the OSG directory to the configure-command like this:
<syntaxhighlight lang="bash">$ ./configure --prefix=/path/to/fgInstallation --with-osg=/path/to/osg/installation --enable-osgviewer</syntaxhighlight> 
In this case you have to tell your system where to find the OSG libraries before you can run flightgear:
<syntaxhighlight lang="bash">$ export LD_LIBRARY_PATH=/path/to/osgInstallation/lib:$LD_LIBRARY_PATH</syntaxhighlight>
'''Step 3:'''
Now you can compile and install Flightgear by:
<syntaxhighlight lang="bash">$ make; make install</syntaxhighlight>
'''Step 4:'''
Clone the data directory:
<syntaxhighlight lang="bash">$ git clone git://</syntaxhighlight>
The data directory is large (almost 2.5GB) so it will take considerable time to download.
There mirror of fgdata that might be faster to download from:
<syntaxhighlight lang="bash">$ git clone git://</syntaxhighlight>
The mirror is synchronized with the master so either will do.
And install it in (or as) /usr/local/share/FlightGear
mv fgdata /usr/local/share/FlightGear
<syntaxhighlight lang== Ubuntu and Debian users =="bash">If you wish you can use the [[Scripted_Compilation_on_Linux_Debian$ mv fgdata /Ubuntu]] script to have Flightgear compiled in one shot under both Ubuntu and Debian systems.usr/local/share/flightgear Debian users who prefer to build it without script may look at [[Building_Flightgear_-_Debian]].Gentoo users can also use overlays to build FlightGear without much hassle : [[Building_Flightgear_-_Gentoo]].</syntaxhighlight>
== External links ==
=== Instructions ===
* [[ MSYS ]]* [[ MinGW/cross-compiler ]]* [[ CodeBlocks IDE ]]* [[ OpenSUSE 10.1 10.2 ]]
* [ MSVC7 *.Net]
* [ MSVC8 aka Visual 2005]
* [ Mac OS X]
== Important note for GIT users ==
As of latest development in GIT, only cmake is now required for building both SimGear and FlightGear. So if you build GIT (for what any reason) please don't try to use as it is removed from repository.
For detailed instructions, see page [[Building_using_CMake|Building using cmake]].
[[fr:Compiler FlightGear sous GNU/Linux]]