summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDenis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>2019-12-11 17:21:12 +0100
committerDenis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>2019-12-11 17:22:55 +0100
commitf0cdd689c8861176904a78e727869f3018588482 (patch)
tree5d37f384ac3040c157190418fb4cac803fbfa676
parent3e8233b486150d61b61beb4062a21c4395bdbd22 (diff)
downloadbuildsystem-presentation-f0cdd689c8861176904a78e727869f3018588482.tar.gz
buildsystem-presentation-f0cdd689c8861176904a78e727869f3018588482.tar.bz2
buildsystem-presentation-f0cdd689c8861176904a78e727869f3018588482.zip
build system internals: Explain where the binaries are installed
This improves clarity as in the GNU/Linux case we can create images by extracting the packages content, whereas in Android the build output ends up in a directory that is then used to build the image. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
-rw-r--r--full-description.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/full-description.md b/full-description.md
index 28daeed..d7f965e 100644
--- a/full-description.md
+++ b/full-description.md
@@ -40,7 +40,8 @@ For instance, it is possible to create OpenWRT images lacking a package manager.
In the AOSP build system, there is no package manager being used to build the
system components. Instead, most software components are built from git
repositories and bundled into a single image that includes the majority of the
-distribution.
+distribution. The output of the build ends up in a directory that is then used
+to create the distribution image that are to be installed on a device.
Besides the core components of AOSP, community distributions tend to use several
external projects like Mesa and the Linux kernel. These must usually be