377
edits
User:Rominet: Difference between revisions
Jump to navigation
Jump to search
→Using download_and_compile.sh to build FlightGear: Add -j$(nproc) tip
m (Typo) |
(→Using download_and_compile.sh to build FlightGear: Add -j$(nproc) tip) |
||
| Line 254: | Line 254: | ||
Replace <code>ssh://''username''@</code> with <code>https://</code> and save the file. As a consequence of this change, all future updates of your FGData clone will use the <tt>https</tt> protocol, therefore you won't be prompted anymore for your SourceForge password. | Replace <code>ssh://''username''@</code> with <code>https://</code> and save the file. As a consequence of this change, all future updates of your FGData clone will use the <tt>https</tt> protocol, therefore you won't be prompted anymore for your SourceForge password. | ||
All that remains to do is to run: | All that remains to do is to run, from the same directory as before (what we called <tt>''$dir''</tt> above): | ||
$ download_and_compile.sh | $ download_and_compile.sh | ||
or | |||
$ download_and_compile.sh -j$(nproc) | |||
(<code>-j$(nproc)</code> is “only” useful to save time—see the tip below). If you don't pass any non-option argument to <tt>download_and_compile.sh</tt> as done here, it will take care of the three base components needed to run FlightGear: <tt>SIMGEAR</tt>, <tt>FGFS</tt> and <tt>DATA</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 [https://sourceforge.net/p/flightgear/simgear/ci/next/tree/ SimGear], [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/ FlightGear] and [https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/ FGData] repositories). Therefore, the above command is presently exactly equivalent to: | |||
$ download_and_compile.sh SIMGEAR FGFS DATA | $ download_and_compile.sh SIMGEAR FGFS DATA | ||
| Line 268: | Line 269: | ||
$ ./run_fgfs.sh --launcher | $ ./run_fgfs.sh --launcher | ||
In case you find this tedious to type or have more arguments to pass on a regular basis, you can follow the advice given at the end of [https://sourceforge.net/p/flightgear/mailman/message/36634426/ this message] or use another launcher such as [[FFGo]] (but the [[FlightGear Qt launcher|FlightGear built-in launcher]] started with <code>run_fgfs.sh --launcher</code> is quite fine, be sure to try it first!). | In case you find this tedious to type or have more arguments to pass on a regular basis, you can follow the advice given at the end of [https://sourceforge.net/p/flightgear/mailman/message/36634426/ this message] or use another launcher such as [[FFGo]] (but the [[FlightGear Qt launcher|FlightGear built-in launcher]] started with <code>run_fgfs.sh --launcher</code> is quite fine, be sure to try it first!). | ||
{{Tip|You can considerably speed up the build process—literally, save hours—by telling <tt>download_and_compile.sh</tt> to use several cores simultaneously when compiling. With option <code>-j$(nproc)</code>, compilations will use all cores available on your processor; thus, a typical <tt>download_and_compile.sh</tt> command is <code>download_and_compile.sh -j$(nproc)</code>. If you want to use, say, 4 cores, replace <code>-j$(nproc)</code> with <code>-j4</code>.}} | |||
==== <span id="using-download-and-compile-sh-to-update-flightgear"></span> Using <tt>download_and_compile.sh</tt> to update FlightGear ==== | ==== <span id="using-download-and-compile-sh-to-update-flightgear"></span> Using <tt>download_and_compile.sh</tt> to update FlightGear ==== | ||