6,566
edits
mNo edit summary |
(→Getting the source: Switched to the {{fgmeta clone}} and {{repo link}} templates and use of the {{#tag:tagname|content|parameters}} magic word to create the <source> tags.) |
||
Line 9: | Line 9: | ||
In all cases, you should get the superbuild by doing a clean clone (from Git) of fgmeta, with the --recursive option: | In all cases, you should get the superbuild by doing a clean clone (from Git) of fgmeta, with the --recursive option: | ||
{{ | {{#tag:source | ||
| {{fgmeta clone | |||
| opt = --recursive | |||
| post = flightgear-fgmeta | |||
}} | |||
| lang=sh | |||
}} | |||
This tells Git to clone submodules, which we need since both flightgear and simgear are submodules of fgmeta. The source repository is {{repo link|site=sf|proj=fgmeta}}. | |||
Note that providing you cloned with <code>--recursive</code>, git pull will also update submodules automatically; some documentation and pages may tell you to manually run <code>git update submodules</code> but providing you do the initial clone with <code>--recursive</code> option, it should not be needed. | |||
Note the superbuild does not include any data repository or base files - you should separately download these or clone fgdata, and pass the location to fgfs when running in your preferred way, eg via the <code>--fg-root</code> command line argument. | |||
Once the clone is complete, check out the <code>next</code> branch of fgmeta; the superbuild is not supported on the release branches. | |||
Once the clone is complete, check out the | |||
<source lang=sh> | |||
cd flightgear-fgmeta | cd flightgear-fgmeta | ||
git checkout next | |||
{{Git checkout|next}} | </source> | ||
<!-- FIXME: Needs to be made compatible with the <source> tags: {{Git checkout|next}} --> | |||
===Superbuild on Windows=== | ===Superbuild on Windows=== |