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:47, 3 May 2019
, 3 May 2019“Compiling the last known-stable versions” was discussed in two places so far; gather them under “Choosing between stable and development versions”
(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)) |
(“Compiling the last known-stable versions” was discussed in two places so far; gather them under “Choosing between stable and development versions”) |
||
| Line 394: | Line 394: | ||
=== Choosing between stable and development versions === | === Choosing between stable and development versions === | ||
For the FGFS component (FlightGear) | By default, <tt>download_and_compile.sh</tt> fetches code and data from development branches of the source repositories (which sometimes causes compilation or runtime errors). However, it is possible to tell the script to download the latest ”stable” version of each component, for some suitable definition of “stable”. This is by means of the <code>-s</code> option: | ||
* build the latest | $ download_and_compile.sh -s ''COMPONENT1 COMPONENT2...'' | ||
How does it work? | |||
* For [[SimGear]], FlightGear and [[FGData]], it uses the most recent stable release branch of the corresponding Git repository. | |||
* For some components, a known-stable version is hardcoded in <tt>download_and_compile.sh</tt> and used when the <code>-s</code> option is given<ref name="components-with-a-known-stable-version-hardcoded-in-download_and_compile_sh">As of May 2019, apart from SIMGEAR, FGFS and DATA, the only components for which <tt>download_and_compile.sh</tt> “knows” a stable version are TERRAGEAR and OPENRTI.</ref> (for instance, the hardcoded information can be the name of a Git branch). | |||
* For the other components, the <code>-s</code> option has no effect. | |||
{{Warning|In a given folder where <tt>download_and_compile.sh</tt> is run, you should either always use the <code>-s</code> option, or never. Building some components with <code>-s</code> and others without (all within the same base folder) is not supported.}} | |||
Applying what we just said to the FGFS component (FlightGear) leaves us with two main options: | |||
* build the latest stable release; | |||
* build the current development version (bleeding edge), which lives in the {{flightgear source | * build the current development version (bleeding edge), which lives in the {{flightgear source | ||
| branch = next | | branch = next | ||
| Line 567: | Line 577: | ||
== Options == | == Options == | ||
=== Advanced options === | === Advanced options === | ||