Scripted Compilation on Linux Debian/Ubuntu: Difference between revisions

Line 24: Line 24:
then execute it (no need to execute it as root).
then execute it (no need to execute it as root).


Here is for example a sequence of commands to get the script and launch it in a new folder.
Here is for example a sequence of commands to get the script:
<pre>
<pre>
mkdir ~/fgfs
mkdir ~/fgfs
Line 30: Line 30:
wget http://www.gitorious.org/fg/fgmeta/blobs/raw/master/download_and_compile.sh
wget http://www.gitorious.org/fg/fgmeta/blobs/raw/master/download_and_compile.sh
chmod 755 download_and_compile.sh
chmod 755 download_and_compile.sh
</pre>
You have two options now: build the latest ''stable'' FlightGear release or build the ''current development'' version (bleeding edge).
=== Build the latest stable FlightGear release ===
When executing the script, use the "-s" option to build the latest stable release:
<pre>
sh download_and_compile.sh -s
</pre>
=== Build the current FlightGear development verison ===
When executing the script without any option, the latest development version is built.
'''Warning''': The development version changes on an almost daily basis. It provides the latest features, but is not always guaranteed to work reliably. If you're unfamiliar with software testing, you may prefer to use the latest stable release.
<pre>
sh download_and_compile.sh
sh download_and_compile.sh
</pre>
</pre>
Once the script is finished, you will successfully get Flightgear and Fgrun installed in the ~/fgfs directory.
Once the script is finished, you will successfully get Flightgear and Fgrun installed in the ~/fgfs directory.


159

edits