diff options
| author | Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> | 2019-12-11 17:07:02 +0100 |
|---|---|---|
| committer | Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> | 2019-12-11 17:07:07 +0100 |
| commit | 3e8233b486150d61b61beb4062a21c4395bdbd22 (patch) | |
| tree | 77471374bff8b241d0175032df027bdb5a686111 | |
| parent | 8ed1bc3ba72423d51dcfc16e5994d43f53dc56ac (diff) | |
| download | buildsystem-presentation-3e8233b486150d61b61beb4062a21c4395bdbd22.tar.gz buildsystem-presentation-3e8233b486150d61b61beb4062a21c4395bdbd22.tar.bz2 buildsystem-presentation-3e8233b486150d61b61beb4062a21c4395bdbd22.zip | |
Building: Insist on the build system package manager
Not having user installable packages is not the main
concern.
What creates most of the issues is that no packages are
used during the image build process.
Because of that:
- We cannot use any software build system (autotools)
- We don't have clear information on licensing
Though having a package manager usable by the user would
also bring many benefits.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
| -rw-r--r-- | full-description.md | 19 |
1 files changed, 11 insertions, 8 deletions
diff --git a/full-description.md b/full-description.md index d5e7c30..28daeed 100644 --- a/full-description.md +++ b/full-description.md @@ -30,14 +30,17 @@ short of taking it closer to the modularity and flexibility found in most GNU/Linux distributions. ## Building AOSP vs building GNU/Linux distros -Virtually all GNU/Linux distributions use package managers, which wrap around -the build system of choice of the software being packaged and bundle it into a -reusable package that can be installed for direct use and or as a dependency for -others. These packages can also be delivered and updated via software -repositories after the initial installation of the distribution. In AOSP, there -is no package manager. Most software components are built from git repositories -and bundled into a single image that includes the majority of the distribution. -Updating a single component thus becomes much harder. +Virtually all GNU/Linux distributions use package managers when building their +software. This wrap around the build system being used by the software +(Makefiles, autools, cmake, etc) and bundles the output in a reusable package. +While such packages can usually be installed by the user, and are typicaly +delivered and updated via software repositories, it is not always the case. +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. Besides the core components of AOSP, community distributions tend to use several external projects like Mesa and the Linux kernel. These must usually be |