377
edits
Scripted Compilation on Linux Debian/Ubuntu: Difference between revisions
Jump to navigation
Jump to search
Scripted Compilation on Linux Debian/Ubuntu (view source)
Revision as of 06:17, 3 May 2019
, 3 May 2019Move “Selecting the components to build” inside “Task-specific instructions” (not an option per se, and so important that it deserves to come very early)
(Precisions (note: the “above” will really be above in a minute)) |
(Move “Selecting the components to build” inside “Task-specific instructions” (not an option per se, and so important that it deserves to come very early)) |
||
| Line 381: | Line 381: | ||
{{Note|In this section, we assume you've read and followed the advice given in [[#getting-started-with-download-and-compile-sh|Getting started with <tt>download_and_compile.sh</tt>]].}} | {{Note|In this section, we assume you've read and followed the advice given in [[#getting-started-with-download-and-compile-sh|Getting started with <tt>download_and_compile.sh</tt>]].}} | ||
=== <span id="selecting-the-components-to-work-on"></span> Selecting the components to build === | |||
By default, <tt>download_and_compile.sh</tt> downloads or updates, then compiles, [[SimGear]] and FlightGear, and downloads or updates [[FGData]] (by nature, FGData can't be compiled). This is what happens when running: | |||
$ download_and_compile.sh | |||
To make it download or update and compile something else, you may pass non-option arguments naming the ''components'' you want, for instance: | |||
$ download_and_compile.sh SIMGEAR FGFS DATA OSG | |||
SIMGEAR, FGFS, DATA and OSG are the component names respectively corresponding to [[SimGear]], FlightGear, [[FGData]] and [[OpenSceneGraph]] in <tt>download_and_compile.sh</tt>'s terminology. | |||
A [[#list-of-available-components|list of available components]] is provided on this page, but the fully up-to-date list can always be obtained by running <code>download_and_compile.sh --help</code>. | |||
=== Choosing between stable and development versions === | |||
For the FGFS component (FlightGear), there are two main options: | For the FGFS component (FlightGear), there are two main options: | ||
| Line 389: | Line 401: | ||
}} branch of the FlightGear repository. | }} branch of the FlightGear repository. | ||
=== Building the latest stable FlightGear release === | ==== Building the latest stable FlightGear release ==== | ||
When executing <tt>download_and_compile.sh</tt>, use the <code>-s</code> option to build the latest stable release: | When executing <tt>download_and_compile.sh</tt>, use the <code>-s</code> option to build the latest stable release: | ||
| Line 397: | Line 409: | ||
{{Note|If you decide to use the <code>-s</code> option in a given directory tree, you should use it for all components in that directory tree (SIMGEAR, FGFS, DATA, etc.). Running <tt>download_and_compile.sh</tt> in a given directory with the <code>-s</code> option for some components and not for others is not supported.}} | {{Note|If you decide to use the <code>-s</code> option in a given directory tree, you should use it for all components in that directory tree (SIMGEAR, FGFS, DATA, etc.). Running <tt>download_and_compile.sh</tt> in a given directory with the <code>-s</code> option for some components and not for others is not supported.}} | ||
=== Building the current FlightGear development version === | ==== Building the current FlightGear development version ==== | ||
When executing <tt>download_and_compile.sh</tt> without any option, the development version of every selected component is built: | When executing <tt>download_and_compile.sh</tt> without any option, the development version of every selected component is built: | ||
| Line 555: | Line 567: | ||
== Options == | == Options == | ||
=== Compiling the last known-stable versions === | === Compiling the last known-stable versions === | ||