417
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 15:05, 11 March 2025
, 11 March→Building FlightGear: download_and_compile.sh now also processes CARES and PLIB when no explicit list of components is specified
(→Getting download_and_compile.sh the “right way”: Update --help text) |
(→Building FlightGear: download_and_compile.sh now also processes CARES and PLIB when no explicit list of components is specified) |
||
| Line 161: | Line 161: | ||
{{Note|Because of the <code>-s</code> option, the above <tt>download_and_compile.sh</tt> command would build the latest stable release of FlightGear. If you want to build the latest Long Term Stable release, use <code>--lts</code> instead. For the previous LTS release, use <code>--old-lts</code>. If you want to build the development version of FlightGear, use none of <code>-s</code>, <code>--lts</code> and <code>--old-lts</code>, but be warned: it may very well be unstable and unsuitable for flying. For more details on these options, see [[#Release selection|Release selection]].}} | {{Note|Because of the <code>-s</code> option, the above <tt>download_and_compile.sh</tt> command would build the latest stable release of FlightGear. If you want to build the latest Long Term Stable release, use <code>--lts</code> instead. For the previous LTS release, use <code>--old-lts</code>. If you want to build the development version of FlightGear, use none of <code>-s</code>, <code>--lts</code> and <code>--old-lts</code>, but be warned: it may very well be unstable and unsuitable for flying. For more details on these options, see [[#Release selection|Release selection]].}} | ||
When you don't pass any non-option argument to <tt>download_and_compile.sh</tt> as done here, it takes care of the base components needed to run FlightGear in good conditions: <tt>SIMGEAR</tt>, <tt>FGFS</tt>, <tt>DATA</tt> and <tt>OSG</tt> (these are the component names used by <tt>download_and_compile.sh</tt>, i.e., the final arguments one can optionally give in a <tt>download_and_compile.sh</tt> command; in normal speech, they correspond to the {{simgear source | When you don't pass any non-option argument to <tt>download_and_compile.sh</tt> as done here, it takes care of the base components needed to run FlightGear in good conditions: <tt>CARES</tt>, <tt>PLIB</tt>, <tt>SIMGEAR</tt>, <tt>FGFS</tt>, <tt>DATA</tt> and <tt>OSG</tt> (these are the component names used by <tt>download_and_compile.sh</tt>, i.e., the final arguments one can optionally give in a <tt>download_and_compile.sh</tt> command; in normal speech, they correspond to the {{github source | ||
| proj = c-ares | |||
| repo = c-ares | |||
| text = c-ares | |||
}}, {{sourceforge source | |||
| proj = libplib | |||
| repo = code | |||
| text = PLIB | |||
}}, {{simgear source | |||
| text = SimGear | | text = SimGear | ||
}}, {{flightgear source | }}, {{flightgear source | ||
| Line 167: | Line 175: | ||
}} and {{fgdata source | }} and {{fgdata source | ||
| text = FGData | | text = FGData | ||
}} repositories as well as a suitable repository for [[OpenSceneGraph]]). Therefore, the above command is presently exactly equivalent to: | }} repositories, as well as a suitable repository for [[OpenSceneGraph]]). Therefore, the above command is presently exactly equivalent to: | ||
$ download_and_compile.sh -s -j$(nproc) SIMGEAR FGFS DATA OSG | $ download_and_compile.sh -s -j$(nproc) CARES PLIB SIMGEAR FGFS DATA OSG | ||
In case you want to build another component such as, say, | In case you want to build another component such as, say, CMAKE, you can add it to the command, like this: | ||
$ download_and_compile.sh -s -j$(nproc) SIMGEAR FGFS DATA OSG | $ download_and_compile.sh -s -j$(nproc) CARES PLIB SIMGEAR FGFS DATA OSG CMAKE | ||
When the command terminates, you should have a script called <tt>run_fgfs.sh</tt> in the directory from which you ran <tt>download_and_compile.sh</tt> (i.e., <tt>~/flightgear/dnc-managed</tt> in the suggested setup). This will be your script to run FlightGear. For instance, in order to start the [[FlightGear Qt launcher|built-in launcher]], you can run the following commands:<ref name="no-need-to-change-to-dnc-managed-dir-before-starting-generated-scripts">We give these commands because they are easy to read, but the <code>cd</code> command is not needed if you use the correct path, as in <code>~/flightgear/dnc-managed/run_fgfs.sh --launcher</code>.</ref> | When the command terminates, you should have a script called <tt>run_fgfs.sh</tt> in the directory from which you ran <tt>download_and_compile.sh</tt> (i.e., <tt>~/flightgear/dnc-managed</tt> in the suggested setup). This will be your script to run FlightGear. For instance, in order to start the [[FlightGear Qt launcher|built-in launcher]], you can run the following commands:<ref name="no-need-to-change-to-dnc-managed-dir-before-starting-generated-scripts">We give these commands because they are easy to read, but the <code>cd</code> command is not needed if you use the correct path, as in <code>~/flightgear/dnc-managed/run_fgfs.sh --launcher</code>.</ref> | ||