Building FlightGear with osgEarth Integration: Difference between revisions
(Switched to {{gitorious source}} to fix all of the broken instructions, and to abstract the Gitorious URLs.) |
(+quote) |
||
Line 31: | Line 31: | ||
== Objective == | == Objective == | ||
{{FGCquote| | |||
people definitely need to understand what they are doing, I would not suggest to actually try this unless people really understand how to patch/build different versions of SG/FG - people blindly following instructions by copying & pasting shell commands into a terminal window is begging for trouble - as matter of fact, that is why I always encourage folks to set up dedicated "fgfs" accounts to be on the safe side. | |||
|{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=300144#p300144 | |||
|title = <nowiki> Re: OSGEarth integrate in Linux Ubuntu </nowiki> | |||
|author = <nowiki> Hooray </nowiki> | |||
|date = Nov 29th, 2016 | |||
|added = Nov 29th, 2016 | |||
|script_version = 0.39 | |||
}} | |||
}} | |||
{{FGCquote | {{FGCquote |
Revision as of 16:50, 1 December 2016
This article is a stub. You can help the wiki by expanding it. |
The FlightGear forum has a subforum related to: OsgEarth support in FlightGear |
Objective
Background
3.4 is required, based on looking at this: https://gitlab.com/poweroftwo/flightgear-osgearth/commits/OsgEarth-FG3.4-Kdis
However, most SG/FG related changes that would conflict with a merge are relatively trivial, i.e. could be resolved by manual edits pretty easily - I don't think that there's lots of scenery related code that got updated recently, i.e. anything affecting the osgEarth patch - simply because FG/osgEarth overrides much of the standard scenery engine anyway. I *assume* that merge conflicts should be relatively straightforward to fix up - but it would make sense to look at the latest release branch in that case. But even that, people would still need to build the whole shebang— Hooray (Feb 20th, 2016). Re: 3.2 osgearth or other integrated real time satellite dat.
(powered by Instant-Cquotes) |
Status
It is what it is, and being what it is (a set of external patches), it has a certain barrier to entry, and learning curve, associated with it.
Basically, people wanting to use this, will need to know how to build FlightGear from source, how to use git and how to apply patches. People with a working build environment should have no problems getting this to work - the main caveat being currently that some recent sg/fg developments would not be integrated yet. But otherwise, all the documentation that you can find on the wiki about building FlightGear from source, using git, will be applicable - the main difference is that once you have everything set up and working to build stock fgfs, you would add poweroftwo's gitlab branches as git remotes, and then build an older version of SimGear/FlightGear which contains the corresponding patches.— Hooray (Feb 20th, 2016). Re: 3.2 osgearth or other integrated real time satellite dat.
(powered by Instant-Cquotes) |
That's basically the whole idea behind osgEarth. It can do satellite/orthoimagery (that's what you see advertised the most), but it can also load shapefiles, DEM etc. And it even comes with built-in LOD — Gijs de Rooy (2015-03-14). Re: [Flightgear-devel] Google Code closing down.
(powered by Instant-Cquotes) |
Assumptions
- 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 https://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
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 https://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
FlightGear
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 https://gitorious.org/fg/flightgear-osgearth.git
git fetch simperative
git checkout --track -b topics/osgearth simperative/2.12-OsgEarthIntegration
FGData
git remote add simperative https://gitorious.org/fg/fgdata-osgearth.git
git fetch simperative
git checkout --track -b topics/osgearth simperative/2.12-OsgEarthIntegration