User:Rominet: Difference between revisions

Jump to navigation Jump to search
→‎Getting started with download_and_compile.sh: Add section about notations (dollar or hash sign preceding commands)
(Add section explaining how to use d&c.sh to update FG and/or other components)
(→‎Getting started with download_and_compile.sh: Add section about notations (dollar or hash sign preceding commands))
Line 26: Line 26:
This text in this section corresponds to the method described in [https://sourceforge.net/p/flightgear/mailman/message/36633375/ this message] on the <tt>flightgear-devel</tt> mailing list. It is more detailed, though, and should hopefully be easier to follow for non-experts.
This text in this section corresponds to the method described in [https://sourceforge.net/p/flightgear/mailman/message/36633375/ this message] on the <tt>flightgear-devel</tt> mailing list. It is more detailed, though, and should hopefully be easier to follow for non-experts.


We'll first explain how to get <tt>download_and_compile.sh</tt> in a way that makes updates easy and causes the command
We'll first explain how to get <tt>download_and_compile.sh</tt> in a way that makes updates easy and causes the command <code>download_and_compile.sh --version</code> to work as intended (the “version” is a Git blob id such as <tt>6a5e4f05e2ccf27115eec58313be027b11266097</tt><ref name="not-on-download-and-compile-sh-version-being-a-Git-blob-id">This looks like, but is ''not'' a Git commit identifier. This kind of “version number” is admittedly not very pretty, but it doesn't pollute Git commits  (the diffs) and is automatically updated by Git every time you update <tt>download_and_compile.sh</tt> the way we are going to present; thus, the advantages compensate for the ugliness.</ref>). Then we'll show you how to clone the large [https://sourceforge.net/p/flightgear/fgdata/ref/next/ FGData] repository, and finally give the last instructions to get FlightGear up and running.
download_and_compile.sh --version
 
to work as intended (the “version” is a Git blob id such as <tt>6a5e4f05e2ccf27115eec58313be027b11266097</tt><ref name="not-on-download-and-compile-sh-version-being-a-Git-blob-id">It's admittedly not very pretty, but is automatically updated by Git every time you update <tt>download_and_compile.sh</tt> the way we are going to present, which is very convenient and compensates for the ugliness.</ref>). Then we'll show you how to clone the large [https://sourceforge.net/p/flightgear/fgdata/ref/next/ FGData] repository, and finally give the last instructions to get FlightGear up and running.
==== <span id="en-getting-started-with-download-and-compile-sh-notations"></span> Notations ====
 
When a command should be run as an unpriviledged user, it will be preceded by a dollar sign:
$ whoami
toto
In contrast, a hash sign (#) means that the command must be run with superuser privileges to achieve the desired effect:
# whoami
root


==== <span id="en-getting-download-and-compile-sh-the-right-way"></span> Getting <tt>download_and_compile.sh</tt> the “right way” ====
==== <span id="en-getting-download-and-compile-sh-the-right-way"></span> Getting <tt>download_and_compile.sh</tt> the “right way” ====
377

edits

Navigation menu