377
edits
Scripted Compilation on Linux Debian/Ubuntu: Difference between revisions
Jump to navigation
Jump to search
Scripted Compilation on Linux Debian/Ubuntu (view source)
Revision as of 22:21, 9 July 2020
, 9 July 2020→When building 'next', you may see build errors: Update according to the latest FG policy and available d&c options
(→Advanced options: Document option --component-branch) |
(→When building 'next', you may see build errors: Update according to the latest FG policy and available d&c options) |
||
| Line 392: | Line 392: | ||
You get the idea. When several components are passed on the same command line, <tt>download_and_compile.sh</tt> chooses a reasonable order for processing, so don't worry about that. | You get the idea. When several components are passed on the same command line, <tt>download_and_compile.sh</tt> chooses a reasonable order for processing, so don't worry about that. | ||
== When building 'next', you may | == When building ''next'', you may encounter problems == | ||
Keeping in mind that this script compiles sometimes bleeding edge software, it can happen that what was successfully compiling last week, does not compile anymore today. Building the stable version should always work, unless there is a problem with the script. | Keeping in mind that this script compiles sometimes bleeding edge software, it can happen that what was successfully compiling last week, does not compile anymore today. Building the latest stable version (option <code>-s</code>) or the latest Long Term Support release (option <code>--lts</code>) should always work, unless there is a problem with the script (well, in some cases, there may be packages of your distribution that are too recent for <code>--lts</code>; for instance, in July 2020, <code>--lts</code> doesn't build with OpenSceneGraph 3.6, but simply passing the OSG component on the <tt>download_and_compile.sh</tt> command solves the problem, because at the time of this writing, option <code>--lts</code> selects OpenSceneGraph 3.4). | ||
That said, | That said, you may want to build the development version (called ''next''): this is the one developers use all the time, so kindly asking on the flightgear-devel [[Mailing_lists|mailing list]] in case a problem popped up<ref name="what-to-provide-when-asking-for-help">Don't forget in this case to precisely tell what you did and include the <tt>compilation_log.txt</tt> file written by <tt>download_and_compile.sh</tt>.</ref> should allow you to find good advice and get the problem quickly fixed, if it's a new one. | ||
{{Warning|As of July 2020, heavy development will be done on ''next'', the development branch of FlightGear. It is expected to be rather unstable for several months. Unless you are really interested in FlightGear development or in providing feedback to the developers, you're probably better off building either the latest stable version (option <code>-s</code>) or the latest Long Term Support release (option <code>--lts</code>).}} | |||
== Task-specific instructions == | == Task-specific instructions == | ||