Building FlightGear with osgEarth Integration: Difference between revisions

No edit summary
Line 26: Line 26:


}}
}}


== Objective ==
== Objective ==
{{FGCquote
  |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.
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=228406#p228406
    |title=<nowiki>Re: 3.2 </nowiki>
    |author=<nowiki>Hooray</nowiki>
    |date=<nowiki>Tue Dec 30</nowiki>
  }}
}}
{{FGCquote
  |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.
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=228441#p228441
    |title=<nowiki>Re: 3.2 </nowiki>
    |author=<nowiki>Hooray</nowiki>
    |date=<nowiki>Tue Dec 30</nowiki>
  }}
}}
{{FGCquote
  |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.
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=228114#p228114
    |title=<nowiki>Re: Initial FlightGear / </nowiki>
    |author=<nowiki>poweroftwo</nowiki>
    |date=<nowiki>Fri Dec 26</nowiki>
  }}
}}


== Assumptions ==
== Assumptions ==