72c626f017
This enables mixed builds to use the file_contexts.bin from the system build when regenerating images that come from system target files, and similarly for file_contexts.bin from the other build when regenerating images from other target files. In monolithic (non-mixed) builds all image-specific selinux_fc props point to the same file_contexts. Bug: 132108151 Test: Built and booted mixed build devices. Change-Id: Id51ed6d96ea6337879f1ab21d47c93c67bc25312 |
||
---|---|---|
common | ||
core | ||
packaging | ||
target | ||
tests | ||
tools | ||
.gitignore | ||
Changes.md | ||
CleanSpec.mk | ||
Deprecation.md | ||
OWNERS | ||
README.md | ||
Usage.txt | ||
buildspec.mk.default | ||
envsetup.sh | ||
help.sh | ||
navbar.md | ||
tapasHelp.sh |
README.md
Android Make Build System
This is the Makefile-based portion of the Android Build System.
For documentation on how to run a build, see Usage.txt
For a list of behavioral changes useful for Android.mk writers see Changes.md
For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.
This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.