Scripted Compilation on Linux Debian/Ubuntu: Difference between revisions

Jump to navigation Jump to search
→‎Advanced options: Add crossref and mention the new --override-repo option
(→‎Choosing between stable and development versions: Add crossref to the place where --component-branch is presented)
(→‎Advanced options: Add crossref and mention the new --override-repo option)
Line 770: Line 770:
* Skip compilation of programs: <code>-c n</code>
* Skip compilation of programs: <code>-c n</code>
* Build with compositor: <code>--compositor</code>
* Build with compositor: <code>--compositor</code>
* Force the use of a particular branch for a given component: <code>--component-branch ''COMPONENT=BRANCH''</code> (e.g., <code>--component-branch OSG=OpenSceneGraph-3.6</code>, <code>--component-branch FGFS=next</code>, etc.—but remember that components FGFS, SIMGEAR and DATA must ''always'' be in sync).
* Force the use of a particular branch for a given component: <code>--component-branch ''COMPONENT=BRANCH''</code> (e.g., <code>--component-branch OSG=OpenSceneGraph-3.6</code>, <code>--component-branch FGFS=next</code>, etc.—but remember that components FGFS, SIMGEAR and DATA must ''always'' be in sync). See [[#Component-specific settings|Component-specific settings]] for details.
* Override the repository from which a given component is initially fetched: <code>--override-repo ''COMPONENT''=''SITE'':''ADDRESS''</code> (see [[#Component-specific settings|Component-specific settings]]).


For example, if you are a developer and wish to quickly recompile and reinstall only your own modifications for FlightGear, you can do this:
For example, if you are a developer and wish to quickly recompile and reinstall only your own modifications for FlightGear, you can do this:
377

edits

Navigation menu