diff options
author | Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> | 2019-12-11 17:27:26 +0100 |
---|---|---|
committer | Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> | 2019-12-11 17:27:33 +0100 |
commit | 6b6b513fffc52383fb8db37d4b0062225635d7f8 (patch) | |
tree | b33b3e7c0177c1fb6bb93d0e5acca3ee34cbc14f | |
parent | 35c5501fb3647ab0a46e15f88b1cf48318ae4c3b (diff) | |
download | buildsystem-presentation-6b6b513fffc52383fb8db37d4b0062225635d7f8.tar.gz buildsystem-presentation-6b6b513fffc52383fb8db37d4b0062225635d7f8.tar.bz2 buildsystem-presentation-6b6b513fffc52383fb8db37d4b0062225635d7f8.zip |
build system internals: Mention the effort required to add convert to Blueprint
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
-rw-r--r-- | full-description.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/full-description.md b/full-description.md index 89ad553..4ad7e2b 100644 --- a/full-description.md +++ b/full-description.md @@ -46,7 +46,7 @@ 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. These must usually be integrated into the build tree as they depend on AOSP's libc. In such cases, Google expects the project -maintainers to keep their project compatible with AOSP's build system, +maintainers to make and keep their project compatible with AOSP's build system, i.e. nowadays they expect the project to have its own Blueprint files. This contrasts with GNU/Linux distributions, which provide ways to build each project in its own native build system and then incorporate it into the distro |