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 11:53, 10 July 2020
, 10 July 2020→Updating FlightGear: If build was done with -s or --lts, updates should use the same option
m (→Release selection: Markup) |
(→Updating FlightGear: If build was done with -s or --lts, updates should use the same option) |
||
| Line 334: | Line 334: | ||
=== <span id="using-download-and-compile-sh-to-update-flightgear"></span> Updating FlightGear === | === <span id="using-download-and-compile-sh-to-update-flightgear"></span> Updating FlightGear === | ||
{{Note|If you built FlightGear with either <code>-s</code> or <code>--lts</code>, you need to pass the ''same option'' to the <tt>download_and_compile.sh</tt> command given below that will update your FlightGear installation. Otherwise, <tt>download_and_compile.sh</tt> will automatically build the ''next'' suite (bleeding-edge development version), which is probably not what you wish. Moreover, if you do want to switch from one suite to another (for instance from ''stable'' to ''next'', or from ''Long Term Support'' to ''stable''), using the <code>--cleanup</code> option of <tt>download_and_compile.sh</tt> is heartily recommended.}} | |||
Keeping the above note in mind, go to the directory from which you previously ran <tt>download_and_compile.sh</tt> (<tt>~/flightgear/dnc-managed</tt> in our example). This is the folder which, if you did a complete run of <tt>download_and_compile.sh</tt> as shown in the previous section, contains the <tt>run_fgfs.sh</tt> script and a log file named <tt>compilation_log.txt</tt> that records what <tt>download_and_compile.sh</tt> did in its last run. If you wish to update, say, {{simgear source | |||
| text = SimGear | | text = SimGear | ||
}}, {{flightgear source | }}, {{flightgear source | ||