FlightGear wiki

Scripted Compilation on Linux Debian/Ubuntu: Difference between revisions

Page Discussion

Scripted Compilation on Linux Debian/Ubuntu (view source)

Revision as of 22:44, 21 April 2019

1,205 bytes added ,  21 April 2019
→‎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)
(→‎Disk Space Requirements: Update (11 GB now))
(→‎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))
Line 36: Line 36:


=== List of compiled programs ===
=== List of compiled programs ===
The script is able to download and compile:
The <tt>download_and_compile.sh</tt> script is able to download and compile:
* FlightGear (And all the data needed to use it)
* [[SimGear]] (”base libraries” that are part of the FlightGear project, and required)
* cmake (for newer cmake capabilities)
* FlightGear
* [[FGData]] (base data files that are part of the FlightGear project, and required)
* [https://cmake.org/ CMake] (in case CMake is too old in your distribution)
* [[PLIB]]
* [[OpenSceneGraph]]
* [[FGRun]]
* [[FGRun]]
* [[FGo!]]
* [[FGo!]]
Line 45: Line 49:
* [[TerraGear_GUI]]
* [[TerraGear_GUI]]
* [[OpenRadar]]
* [[OpenRadar]]
* [[ATC-pie]]
* [[FlightGear HLA support (High Level Architecture) | OpenRTI]]
* [[FlightGear HLA support (High Level Architecture) | OpenRTI]]


Note that OpenRTI is just another optional dependency for HLA support: http://wiki.flightgear.org/FlightGear_HLA_support_(High_Level_Architecture)
(Note that OpenRTI is just an optional dependency for [[FlightGear high-level architecture support|HLA support]]. For 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.


For the time being, you should be just fine building without HLA support. 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.
At the moment, it's probably safe to say that HLA is only of interest to developers and people willing to play with experimental features.)


At the moment, it's probably safe to say that HLA is only of interest to developers and people willing to play with experimental features.
Each of the items listed above corresponds to a ''component'' in <tt>download_and_compile.sh</tt> terminology. Components are written in uppercase. The list of supported ones is currently:
* SIMGEAR
* FGFS (this corresponds to FlightGear)
* DATA (this corresponds to [[FGData]])
* CMAKE
* PLIB
* OSG (this corresponds to [[OpenSceneGraph]])
* FGRUN
* FGO
* FGX
* TERRAGEAR
* TERRAGEARGUI
* OPENRADAR
* ATCPIE
* OPENRTI
The up-to-date list of components can be obtained by running:
download_and_compile.sh --help


you can pass the '''-i''' option to compile OpenRTI, as well as SimGear and FlightGear re-configured with -D ENABLE_RTI=ON option (experimental)
What is the point of knowing this? Because you may pass component names to <tt>download_and_compile.sh</tt> in order to tell it what you want to download, build and install. By default, only the three essential components SIMGEAR, FGFS and DATA are taken care of, which means that the command:
download_and_compile.sh
is equivalent to:
download_and_compile.sh SIMGEAR FGFS DATA


<syntaxhighlight lang="bash">./download_and_compile.sh -i</syntaxhighlight>
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, <tt>download_and_compile.sh</tt> chooses a reasonable order for processing, so don't worry about that.


==== When building Next you may see build errors ====
==== When building Next you may see build errors ====
Rominet
377

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/117884"