936
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 23:21, 3 April 2023
, 3 April 2023-G Ninja and --verbose options added
(→Task-specific instructions: Add section showing how to pass -DCMAKE_VERBOSE_MAKEFILE=1 when building SG or FG) |
(-G Ninja and --verbose options added) |
||
| Line 372: | Line 372: | ||
There we are! You now have a clean, up-to-date [[FGData]] clone in <tt>~/flightgear/dnc-managed/install/flightgear/fgdata</tt> (remember: <tt>~/flightgear/dnc-managed</tt> is the directory from which you ran <tt>download_and_compile.sh</tt>). Note this place: the full path of the <tt>~/flightgear/dnc-managed/install/flightgear/fgdata</tt> directory is your [[$FG_ROOT]]. | There we are! You now have a clean, up-to-date [[FGData]] clone in <tt>~/flightgear/dnc-managed/install/flightgear/fgdata</tt> (remember: <tt>~/flightgear/dnc-managed</tt> is the directory from which you ran <tt>download_and_compile.sh</tt>). Note this place: the full path of the <tt>~/flightgear/dnc-managed/install/flightgear/fgdata</tt> directory is your [[$FG_ROOT]]. | ||
Now, change the protocol to use for future updates of your FGData clone:<ref name="changing-the-protocol-for-a-git-remote-manual-method">Another way would be to manually change the relevant line starting with <code><nowiki> | Now, change the protocol to use for future updates of your FGData clone:<ref name="changing-the-protocol-for-a-git-remote-manual-method">Another way would be to manually change the relevant line starting with <code>url = <nowiki>ssh://SFusername@</nowiki></code> for the <code>origin</code> remote in the <tt>.git/config</tt> file that lives inside your repository clone (i.e., <tt>~/flightgear/dnc-managed/install/flightgear/fgdata/.git/config</tt> in our example).</ref> | ||
(cd install/flightgear/fgdata && \ | (cd install/flightgear/fgdata && \ | ||
git remote set-url origin <nowiki>https://git.code.sf.net/p/flightgear/fgdata</nowiki>) | git remote set-url origin <nowiki>https://git.code.sf.net/p/flightgear/fgdata</nowiki>) | ||
| Line 773: | Line 773: | ||
* 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. | * 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]]). | * 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]]). | ||
* Generate build.ninja files and build using Ninja: -G Ninja | |||
* Run Cmake in verbose mode: --verbose | |||
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: | ||