Hi fellow wiki editors!

To help newly registered users get more familiar with the wiki (and maybe older users too) there is now a {{Welcome to the wiki}} template. Have a look at it and feel free to add it to new users discussion pages (and perhaps your own).

I have tried to keep the template short, but meaningful. /Johan G

Building FlightGear with osgEarth Integration

From FlightGear wiki
Revision as of 15:45, 31 January 2015 by Hooray (Talk | contribs)

Jump to: navigation, search
This article is a stub. You can help the wiki by expanding it.
Note  This article contains outdated instructions still referring to the 2.12 integration branches. Meanwhile, those branches have been updated for 3.x - and developers are exploring the possibility to get this committed into mainline for the upcoming release.

These should be the public links to the flightgear / osgEarth repositories (note that latest development is found in OsgEarthNext branch)

Use this version of osgEarth:

Cquote1.png This is yet another auto-builder for Flightgear and for the time being specific to Windows 64bit ONLY. It is particularly geared toward building FG with the latest incarnation of the osgEarth integration. The simple minded script attempts to download all needed and hopefully manages conflicts with your user/system environment variables properly. Also, a minimal sized fgdata is downloaded as a starting point.

It is a work in progress and will be refined over time. Hopefully Linux and Mac versions will follow. It is proves to work well, I plan to update the wiki.

[Special thanks to Alant for doing early testing]

— poweroftwo (Wed Jun 25). auto-builder for Flightgear / osgEarth build.
(powered by Instant-Cquotes)


Cquote1.png Someone able to build from source should still be able to get osgEarth working without too much effort - on Windows there should even be some kind of "overlay" (set of patch files) - I am not sure if those have recently been updated for 3.2 though.
— Hooray (Tue Dec 30). Re: 3.2 .
(powered by Instant-Cquotes)
Cquote1.png you do need osgEarth support for that, which is not included in any of the standard releases so far - which is why you need to follow the instructions from the osgEarth thread - however, osgEarth in 3.2 is a completely different matter, because this may very well involve building FlightGear from source - all of this is fairly well documented via a number of different wiki articles. However, it is a fairly technical and tedious process, certainly for people new to compiling software. In other words, osgEarth support in FlightGear in its current form hasn't yet been included in any official release, which means that it must be considered an experimental feature, which is primarily supported by the community, through a number of wiki articles, forum threads/postings and instructions on getting it to work.
— Hooray (Tue Dec 30). Re: 3.2 .
(powered by Instant-Cquotes)
Cquote1.png I believe that the OsgEarthNext branch can be built in Linux but seems to require some gyrations to accomplish the setup. see above conversations.

The fgmindata is simply a minimal set of fgdata necessary to run Flightgear, particularly with the osgEarth build without having to download all of the fgdata repository. It contains only a handful of aircraft. I would not recommend dumping the contents on top of an existing fgdata data set unless you are careful about the merging. There are probably only about a dozen or so files that need to be added/merged to the existing fgdata set. If you have the fgdata git repository cloned already, you might consider adding a remote pointing to the fgdata-osgearth repository. That would allow you to cleanly manage as a separate branch.

— poweroftwo (Fri Dec 26). Re: Initial FlightGear / .
(powered by Instant-Cquotes)


  • You already have working branches of SG/FG and FGData, you only need to add the simperative branches as remote tracking branches
  • $SG_SRC, $FG_SRC and $FG_ROOT must be clean checkouts, commit/stash any unsaved work and check out next/master first.

Building the osgEarth plugin

  • clone the repository:
    git clone -v -b 2.12-OsgEarthIntegration git@gitorious.org:fg/flightgear-osgearth.git flightgear
  • create a separate build directory
  • configure via CMake, set -DCMAKE_INSTALL_PREFIX matching your OSG/SG/FG installation path (not needed if you installed OSG/SG system-wide)
  • run "make install" (to run a parallel build, pass -j x, where is x the number of cores available/to be used)
  • next, build SimGear


Switch into your cloned SimGear repository, make sure that it is in a clean state (commit/stash any changes, switch to next)

## add a new remote alias 
git remote add simperative  git@gitorious.org:fg/simgear-osgearth.git

## fetch all branches
git fetch simperative

## check out a remote tracking branch named topics/osgearth
git checkout --track -b topics/osgearth simperative/2.12-OsgEarthIntegration
  • run make -j4 install
  • switch to your FG_SRC directory


Switch into your cloned FlightGear repository, make sure that it is in a clean state (commit/stash any changes, switch to next)

git remote add simperative  git@gitorious.org:fg/flightgear-osgearth.git
git fetch simperative 
git checkout --track -b topics/osgearth simperative/2.12-OsgEarthIntegration 


git remote add simperative git@gitorious.org:fg/fgdata-osgearth.git
git fetch simperative
git checkout --track -b topics/osgearth simperative/2.12-OsgEarthIntegration