diff options
| author | Lucio Andrés Illanes Albornoz (arab, vxp) <lucio@lucioillanes.de> | 2018-05-17 11:48:32 +0000 |
|---|---|---|
| committer | Lucio Andrés Illanes Albornoz (arab, vxp) <lucio@lucioillanes.de> | 2018-05-17 11:48:32 +0000 |
| commit | 70467c56951e01cad359872794c56305fca40e2e (patch) | |
| tree | bb66e15c91679b2256754bfc3c347dd4843fed17 /etc | |
| parent | 752a003cb9c289ca10533e4290a303bf80b1fedf (diff) | |
| download | midipix_build-70467c56951e01cad359872794c56305fca40e2e.tar.bz2 midipix_build-70467c56951e01cad359872794c56305fca40e2e.tar.xz | |
etc/README: updated re: build time.
Diffstat (limited to 'etc')
| -rw-r--r-- | etc/README | 7 |
1 files changed, 3 insertions, 4 deletions
@@ -22,10 +22,9 @@ the most recent distribution tarball and follow the instructions below. It is, however, recommended to anyone intending to use Midipix as a development platform to familiarise themselves with the build process. Other reasons to prefer building a Midipix distribution yourself include integrating new 3rd party software or local -runtime component patches. At present, a full build from scratch takes about 30 -(thirty) minutes to finish on an 8-core host with eight simultaneous make jobs, -minus the generation of the tarballs. The build script can be obtained from the -following GitHub repository: <https://github.com/lalbornoz/midipix_build>. +runtime component patches. At present, a full build from scratch, excluding tarballs, +takes between 1 and 2 hours to finish on an 8-core Xeon 3.5 GHz host. +The build script can be obtained from the following GitHub repository: <https://github.com/lalbornoz/midipix_build>. If you obtained a Midipix distribution tarball, extract it into a directory and drive of your choice, henceforth referred to as target directory; the drive can |