Building FlightGear with osgEarth Integration: Difference between revisions

Line 78: Line 78:
}}
}}
== Status ==
== Status ==
{{FGCquote
|1= 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.
|2= {{cite web
  | url    = http://forum.flightgear.org/viewtopic.php?p=276880#p276880
  | title  = <nowiki>Re: 3.2 osgearth or other integrated real time satellite dat</nowiki>
  | author = <nowiki>Hooray</nowiki>
  | date  = Feb 20th, 2016
  | added  = Feb 20th, 2016
  | script_version = 0.25
  }}
}}
{{FGCquote
{{FGCquote
   |That's basically the whole idea behind osgEarth. It can do satellite/orthoimagery (that's what you see<br/>
   |That's basically the whole idea behind osgEarth. It can do satellite/orthoimagery (that's what you see<br/>