Scripted Compilation on Linux Debian/Ubuntu: Difference between revisions

Be more precise on space requirements
m (→‎Optimus technology: Pure form update (no idea if the advice is still applicable))
(Be more precise on space requirements)
Line 36: Line 36:
=== Disk Space Requirements ===
=== Disk Space Requirements ===


As of April 2019, building FlightGear requires about 11 Gigabytes of disk space. Note that this includes downloaded source code, build files and the large [[FGData]] repository (about 5 Gigabytes for that one).
As of April 2019, building FlightGear requires about 12 [https://en.wikipedia.org/wiki/Gibibyte 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).


=== List of compiled programs ===
=== List of compiled programs ===
Line 263: Line 263:
== Disk usage and build time ==
== Disk usage and build time ==


Keeping compiled programs, source code and data repositories requires some hard disk space: it will take something like 12 GB of space for just [[SimGear]], FlightGear and [[FGData]] (i.e., the SIMGEAR, FGFS and DATA components).
Keeping compiled programs, source code and data repositories requires some hard disk space: it will take something like 12 [https://en.wikipedia.org/wiki/Gibibyte GiB] of space for just [[SimGear]], FlightGear and [[FGData]] (i.e., the SIMGEAR, FGFS and DATA components).


With an Intel Core i7 860 CPU (2.80 GHz) purchased in 2009, compiling [[SimGear]] and FlightGear 2019.2 with option <code>-j8</code> takes about 14 minutes. If you don't have a fast machine and build using only one core, it may require several hours.
With an Intel Core i7 860 CPU (2.80 GHz) purchased in 2009, compiling [[SimGear]] and FlightGear 2019.2 with option <code>-j8</code> takes about 14 minutes. If you don't have a fast machine and build using only one core, it may require several hours.
377

edits