Scripted Compilation on Linux Debian/Ubuntu: Difference between revisions

Jump to navigation Jump to search
→‎Choosing between stable and development versions: Add details and cross-reference to where --cleanup is explained
(→‎Task-specific instructions: Add subsection “Overriding the source repository or branch for a component”)
(→‎Choosing between stable and development versions: Add details and cross-reference to where --cleanup is explained)
Line 467: Line 467:
{{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).
{{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. For instance:
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.
* 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).
* Want to try ''next''? Okay, then build once with <code>--cleanup</code> (no <code>-s</code> option anymore).
Line 474: Line 474:
* etc.
* 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 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:
377

edits

Navigation menu