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 16:34, 18 December 2022

6 bytes added ,  18 December 2022
→‎Choosing between stable and development versions: Reduce the scope of the large note and reorder to improve readability
(→‎Choosing between stable and development versions: Add details and cross-reference to where --cleanup is explained)
(→‎Choosing between stable and development versions: Reduce the scope of the large note and reorder to improve readability)
Line 464: Line 464:
* For [[SimGear]], FlightGear and [[FGData]], <code>-s</code> uses the most recent stable release branch of the corresponding Git repository, <code>--lts</code> uses the most recent Long Term Stable release (LTS) and <code>--old-lts</code> uses the previous LTS release.
* For [[SimGear]], FlightGear and [[FGData]], <code>-s</code> uses the most recent stable release branch of the corresponding Git repository, <code>--lts</code> uses the most recent Long Term Stable release (LTS) and <code>--old-lts</code> uses the previous LTS release.
* For other components, a known-stable version is selected by <tt>download_and_compile.sh</tt>, which may be influenced by the use of <code>-s</code>, <code>--lts</code> or <code>--old-lts</code>.
* For other components, a known-stable version is selected by <tt>download_and_compile.sh</tt>, which may be influenced by the use of <code>-s</code>, <code>--lts</code> or <code>--old-lts</code>.
{{Note|In a given folder where <tt>download_and_compile.sh</tt> is run, you should normally either always use the <code>-s</code> option, or always use <code>--lts</code>, or always use <code>--old-lts</code>, or always none of these (in other words, stick to the same suite: latest stable, latest LTS, previous LTS or ''next'', consistently accross all components).
Actually, it ''is'' possible to switch between suites but you have to use the <code>--cleanup</code> option when doing the switch (see [[#Cleaning built and installed files|Cleaning built and installed files]] for information on this option). For instance:
* Build with <code>-s</code> as many times as you want.
* Want to try ''next''? Okay, then build once with <code>--cleanup</code> (no <code>-s</code> option anymore).
* You can then perform as many builds of ''next'' as you want; no need to use <code>--cleanup</code> unless something special went wrong.
* If you decide to switch back to the stable release, build once with <code>-s</code> and <code>--cleanup</code>, then only with <code>-s</code> for further builds.
* etc.
This way, ''you don't need to download the repositories again'' when trying the various suites. In particular, you can switch between ''next'', stable, LTS and old LTS without downloading nor having several copies of [[FGData]] on your hard drive. (This works because a Git repository may internally contain data for several branches, even if only one is “normally visible” in the filesystem at a given time.)}}


So, as far as the SIMGEAR, FGFS and DATA components are concerned, you can:
So, as far as the SIMGEAR, FGFS and DATA components are concerned, you can:
Line 485: Line 474:
}} branch of the FlightGear repository.
}} branch of the FlightGear repository.
The use of <code>-s</code>, <code>--lts</code> or <code>--old-lts</code> also influences the version of other components you may have selected (this can be overridden using <code>--component-branch</code>, for advanced users).
The use of <code>-s</code>, <code>--lts</code> or <code>--old-lts</code> also influences the version of other components you may have selected (this can be overridden using <code>--component-branch</code>, for advanced users).
{{Note|In a given folder where <tt>download_and_compile.sh</tt> is run, you should normally either always use the <code>-s</code> option, or always use <code>--lts</code>, or always use <code>--old-lts</code>, or always none of these (in other words, stick to the same suite: latest stable, latest LTS, previous LTS or ''next'', consistently accross all components).}}
Actually, it ''is'' possible to switch between suites but you have to use the <code>--cleanup</code> option when doing the switch (see [[#Cleaning built and installed files|Cleaning built and installed files]] for information on this option). For instance:
* Build with <code>-s</code> as many times as you want.
* Want to try ''next''? Okay, then build once with <code>--cleanup</code> (no <code>-s</code> option anymore).
* You can then perform as many builds of ''next'' as you want; no need to use <code>--cleanup</code> unless something special went wrong.
* If you later decide to switch back to the stable release, build once with <code>-s</code> and <code>--cleanup</code>, then only with <code>-s</code> for further builds.
* etc.
This way, ''you don't need to download the repositories again'' when trying the various suites. In particular, you can switch between ''next'', stable, LTS and old LTS without downloading nor having several copies of [[FGData]] on your hard drive. (This works because a Git repository may internally contain data for several branches, even if only one is “normally visible” in the filesystem at a given time.)


==== Building the latest Long Term Stable release of FlightGear ====
==== Building the latest Long Term Stable release of FlightGear ====
Rominet
377

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/136731"

Navigation menu