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

Changes

Jump to: navigation, search
List of compiled programs: Update whole section (I'm not opposed to also removing most of the paragraph on HLA: redirecting to the page should be enough)
=== List of compiled programs ===
The <tt>download_and_compile.sh</tt> script is able to download and compile:* FlightGear [[SimGear]] (And all ”base libraries” that are part of the FlightGear project, and required)* FlightGear* [[FGData]] (base data needed to use itfiles that are part of the FlightGear project, and required)* [https://cmake .org/ CMake] (for newer cmake capabilitiesin case CMake is too old in your distribution)* [[PLIB]]* [[OpenSceneGraph]]
* [[FGRun]]
* [[FGo!]]
* [[TerraGear_GUI]]
* [[OpenRadar]]
* [[ATC-pie]]
* [[FlightGear HLA support (High Level Architecture) | OpenRTI]]
(Note that OpenRTI is just another an optional dependency for [[FlightGear high-level architecture support|HLA support: http://wiki]].flightgearFor the time being, you should be just fine building without it. Eventually, the idea is for HLA to replace the existing MP system and even increasingly distribute the FlightGear architecture such that more and more components can be more easily run in separate threads or even separate processes, possibly even on different machines. So this is going to be an important feature for professional users, using several computers and screens to create a comprehensive and immersive simulation environment.org/FlightGear_HLA_support_(High_Level_Architecture)
For At the time beingmoment, you should be just fine building without HLA support. Eventually, the idea is for HLA it's probably safe to replace the existing MP system and even increasingly distribute the FlightGear architecture such say that more and more components can be more easily run in separate threads or even separate processes, possibly even on different machines. So this HLA is going only of interest to be an important feature for professional users, using several computers developers and screens people willing to create a comprehensive and immersive simulation environmentplay with experimental features.)
At Each of the moment, it's probably safe items listed above corresponds to say that HLA is only a ''component'' in <tt>download_and_compile.sh</tt> terminology. Components are written in uppercase. The list of interest supported ones is currently:* SIMGEAR* FGFS (this corresponds to developers and people willing FlightGear)* DATA (this corresponds to play with experimental features[[FGData]])* CMAKE* PLIB* OSG (this corresponds to [[OpenSceneGraph]])* FGRUN* FGO* FGX* TERRAGEAR* TERRAGEARGUI* OPENRADAR* ATCPIE* OPENRTIThe up-to-date list of components can be obtained by running: download_and_compile.sh --help
What is the point of knowing this? Because you can may pass the '''-i''' option component names to compile OpenRTI<tt>download_and_compile.sh</tt> in order to tell it what you want to download, as well as SimGear build and FlightGear re-configured with -D ENABLE_RTI=ON option (experimental)install. By default, only the three essential components SIMGEAR, FGFS and DATA are taken care of, which means that the command: download_and_compile.shis equivalent to: download_and_compile.sh SIMGEAR FGFS DATA
In case you want to do the same build with just [[OpenSceneGraph]] added, you can use: download_and_compile.sh SIMGEAR FGFS DATA OSG You get the idea. When several components are passed on the same command line, <syntaxhighlight lang="bash"tt>./download_and_compile.sh -i</syntaxhighlighttt>chooses a reasonable order for processing, so don't worry about that.
==== When building Next you may see build errors ====
289
edits

Navigation menu