377
edits
Scripted Compilation on Linux Debian/Ubuntu: Difference between revisions
Scripted Compilation on Linux Debian/Ubuntu (view source)
Revision as of 13:16, 2 May 2019
, 2 May 2019More consistent header names
(Reduce redundancy (only one copy of the list of available components in the main text—sample output of download_and_compile.sh --help has a second copy)) |
m (More consistent header names) |
||
| Line 389: | Line 389: | ||
}} branch of the FlightGear repository. | }} branch of the FlightGear repository. | ||
=== | === 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 397: | ||
{{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 === | ||
When executing <tt>download_and_compile.sh</tt> without any option, the latest development version is built: | When executing <tt>download_and_compile.sh</tt> without any option, the latest development version is built: | ||