377
edits
(Add precision: what happens when --launcher is omitted) |
(→Avoiding multiple downloads of FGData: FG build uses FGData too (picks up translations and creates .qm files), therefore FGData version must match FG version also when building FG) |
||
Line 445: | Line 445: | ||
{{Warning|This can only work simply if all trees that share a given FGData repository are from the same release (e.g., current stable or development). Running a “stable“ FlightGear with FGData from the ''next'' branch or the other way round, a development version of FlightGear with FGData from a release branch, doesn't work—and FlightGear should tell you when you start it in such a situation. | {{Warning|This can only work simply if all trees that share a given FGData repository are from the same release (e.g., current stable or development). Running a “stable“ FlightGear with FGData from the ''next'' branch or the other way round, a development version of FlightGear with FGData from a release branch, doesn't work—and FlightGear should tell you when you start it in such a situation. | ||
That said, people comfortable with Git can check out the correct FGData branch before starting FlightGear, for instance: | That said, people comfortable with Git can check out the correct FGData branch before building or starting FlightGear, for instance: | ||
$ cd /path/to/fgdata && git checkout release/2019.1 | $ cd /path/to/fgdata && git checkout release/2019.1 | ||
or | or |
edits