Scripted Compilation on Linux Debian/Ubuntu: Difference between revisions

Scripted Compilation on Linux Debian/Ubuntu (view source)

Revision as of 14:24, 23 April 2019

533 bytes added , 23 April 2019

→‎Compiling last stable versions (Experimental): Update, clarify

Rominet

377

edits

@@ Line 229: / Line 229: @@
 === Compiling last stable versions (Experimental) ===
-Even if the script fetches data and sources from bleeding edge developers repositories (which sometimes do not compile), you can still force the script to download latest known versions of the software that were compiling successfully by adding the -s option.
-<pre>
-./download_and_compile.sh -s
-</pre>
-How does it work? Inside the script there is a small list with latest known versions of successfully compiling revisions, it will download from svn/git those specific revisions, which have been found able to compile together.<BR/>
+Even if <tt>download_and_compile.sh</tt> fetches code and data from development branches of the source repositories by default (which sometimes causes compilation errors), it is possible to tell the script to download the latest known versions of the software that were compiling successfully by means of the <code>-s</code> option:
-Warning: If you run this option inside a folder where you previously compiled FGFS, it will probably fail to compile, you better run the script with this option inside an empty folder or a folder with the same FGFS version compiled previously.
+ ./download_and_compile.sh -s
+How does it work?
+* For [[SimGear]], FlightGear and [[FGData]], it uses the most recent stable release branch of the corresponding Git repository.
+* For some components, a known-stable version is hardcoded in <tt>download_and_compile.sh</tt> and used when the <code>-s</code> option is given<ref name="components-with-a-known-stable-version-hardcoded-in-download_and_compile_sh">As of April 2019, apart from SIMGEAR, FGFS and DATA, the only component for which <tt>download_and_compile.sh</tt> “knows” a stable version is OPENRTI.</ref> (for instance, the hardcoded information can be the name of a Git branch).
+* For the other components, the <code>-s</code> option has no effect.
+{{Warning|In a given folder where <tt>download_and_compile.sh</tt> is run, you should either always use the <code>-s</code> option, or never. Building some components with <code>-s</code> and others without (all within the same base folder) is not supported.}}
 === Advanced options ===