Jump to: navigation, search

Scripted Compilation on Linux Debian/Ubuntu

382 bytes added, 17:22, 4 October 2019
add prerequisites section since dnc doesn't automatically pull these needed tools if they are not already installed.
Apart from its main purpose, <tt></tt> can be used to find hopefully up-to-date build-dependency information for FlightGear and related software. You would do so by inspecting [ the script] at the point where it installs packages.<ref name="note-inspecting-download-and-compile-sh-to-gather-build-dependency-information">Look for strings such as <tt>zlib1g-dev</tt>, <tt>libglew-dev</tt> or <tt>qt5-default</tt>.</ref>
== Prerequisites == Before embarking on building your own FlightGear binaries, you must have already installed the necessary tools to compile the source code with. These preliminary tools are * build-essential* git* subversion* cmake* automake They can be installed quite simply by running the following command line.  $ sudo apt-get install build-essential git subversion cmake automake Once these tools are installed, the script can be run. It will install possibly needed additional tools and libraries as it runs. == <span id="disk-space-requirements-and-build-time"></span> Disk space requirements and build time ==
As of April 2019, building FlightGear requires about 12 [ GiB] of disk space. Note that this includes downloaded source code for [[SimGear]] and FlightGear, generated build files and the large [[FGData]] repository (about 6 GiB for that one).
Of course, it is always possible to make commands shorter by setting up aliases (see tips at the end of [ this message]), by adding the directory containing <tt></tt> to your <tt>PATH</tt> or by creating a symbolink link pointing to <tt></tt> in a directory that is part of your <tt>PATH</tt>. This is not necessary, though; do it only if you feel the need (when enabled, persistent shell history is often enough for such things).
{{Note|The following commands should be run from an empty directory<ref name="dedicated-directory-won-t-stay-empty-forever">Well, empty before the first time; later, <tt></tt> is going to populate it with plenty of FlightGear files and subdirectories, of course.</ref> in a partition that has enough free space (see [[FGData]] currently takes about 5 [ GiB] #disk-space-requirements-and you'll need several more gibibytes to download the [[SimGear-build-time | Disk space requirements and build time]] plus FlightGear sources, and build them. As of April 2019, a complete build including SimGear, FlightGear and FGData requires approximately 12 GiB of disk space). As explained in [[#getting-started-with-download-and-compile-sh-notations|Notations]], we are going to choose the directory <tt>~/flightgear/dnc-managed</tt> for this purpose, in order to express that the whole directory tree is managed by <tt></tt>. This is just an example; feel free to choose another directory if you want.
'''Don't run the commands from a non-dedicated directory,''' because it will be filled with files and directories created by <tt></tt> and the FlightGear, SimGear, etc. build systems. That would be a complete mess! In particular, ''don't'' run the commands from the directory containing your [[FGMeta]] clone.}}
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></tt>). Note this place: the full path of the <tt>~/flightgear/dnc-managed/install/flightgear/fgdata</tt> directory is your [[$FG_ROOT]].
Now open , change the protocol to use for future updates of your FGData clone:<ttref name="changing-the-protocol-for-a-git-remote-manual-method">[[$FG_ROOT]]Another way would be to manually change the relevant line starting with <code><nowiki>url = ssh://SFusername@</nowiki></code> for the <code>origin</code> remote in the <tt>.git/config</tt> file that lives inside your FGData repository clone (i.e., <tt>~/flightgear/dnc-managed/install/flightgear/fgdata/.git/config</tt> in our example). You should see a paragraph resembling this:</ref> [remote "origin"](cd install/flightgear/fgdata && \ git remote set-url = sshorigin <nowiki>https://''SFusername'' fetch = +refs/heads/*:refs</remotes/origin/*nowiki>)Replace (you can check at any time the protocol(s) in use with the command <code>ssh://''SFusername''@git remote -v</code> with run inside a Git repository—in this case, inside the folder <codett>https:install/flightgear/fgdata</codett> and save the file). As a consequence of this change, all future updates of your FGData clone will use the <tt>https</tt> protocol, therefore you won't be prompted anymore for your SourceForge password.
All that remains to do is to run, from the same directory as before (<tt>~/flightgear/dnc-managed</tt> in our example):
}} for FlightGear.}}
This can be useful for instance to work around bugs in a part of SimGear or FlightGear that you don't need, but causes a build or runtime failure (see [https://{{|t=35740 |text=here] }} for example). This is often convenient when using the development version of FlightGear, but doesn't mean such bugs shouldn't be reported!
If you have several such options to pass, just use spaces to separate them inside the quotes:
$ rm -rf build/* install/simgear/ install/openrti/ install/flightgear/share/ install/flightgear/bin/
See [https://{{|t=26244 |text=this thread] }} for more details.
== Options ==
The same can be done for the [[FlightGear_Launch_Control|FGRun]] launcher:
$ sed 's|\./fgrun|optirun ./fgrun|' > && chmod +x
== Remove warning message for DDS files ==
You can remove the warning message displayed when DDS files are parsed by SimGear by adding the following line just after '''cd "simgear"''' line :
$ sed -i s/SG_ALERT,\ \"Image/SG_WARN,\ \"Image/g simgear/scene/model/ModelRegistry.cxx
== See also ==
[[Category:Building from source]]
[[nl:Compileren met een Script op Linux Debian/Ubuntu]]
[[fr:Script de compilation sous Linux Debian/Ubuntu]]
[[nl:Compileren met een Script op Linux Debian/Ubuntu]]

Navigation menu