Scripted Compilation on Linux Debian/Ubuntu: Difference between revisions

Jump to navigation Jump to search
m
→‎For the impatient: Lighter wording
m (→‎Download: Mention --lts as well)
m (→‎For the impatient: Lighter wording)
Line 63: Line 63:
The command <tt>run_fgfs.sh --launcher</tt> starts the [[FlightGear Qt launcher|FlightGear built-in launcher]]. This is often convenient but not compulsory. Another way to start FlightGear could be <code>./run_fgfs.sh --airport=PHTO --aircraft=c172p</code>. There are plenty of other options, which are listed by <code>./run_fgfs.sh --help --verbose</code>.
The command <tt>run_fgfs.sh --launcher</tt> starts the [[FlightGear Qt launcher|FlightGear built-in launcher]]. This is often convenient but not compulsory. Another way to start FlightGear could be <code>./run_fgfs.sh --airport=PHTO --aircraft=c172p</code>. There are plenty of other options, which are listed by <code>./run_fgfs.sh --help --verbose</code>.


In some cases, <tt>download_and_compile.sh</tt> stops and waits for your answer before continuing. This is done when there is something important that you should know. When you are used to these prompts and would rather not see them anymore, you may pass the <code>--non-interactive</code> option to suppress them.
In some cases, <tt>download_and_compile.sh</tt> stops and waits for your answer before continuing. This is done when there is something important that you should know. When you are used to these prompts and would rather not see them anymore, pass the <code>--non-interactive</code> option to suppress them.


More detailed instructions are given below. The following sections also explain how to update <tt>download_and_compile.sh</tt> and FlightGear.
More detailed instructions are given below. The following sections also explain how to update <tt>download_and_compile.sh</tt> and FlightGear.
377

edits

Navigation menu