9d281d9271
In terms of sepolicy rules, every property should have an apporpriate owner attribute, which can be one of: system_property_type, product_property_type, or vendor_property_type. This will be enforced for devices launching with S or later. Devices launching with R or eariler can relax this by setting following under BoardConfig.mk: BUILD_BROKEN_ENFORCE_SYSPROP_OWNER := true See system/sepolicy/public/te_macros for more details. Bug: 131162102 Test: system/sepolicy/tools/build_policies.sh Change-Id: Iee05fc15beac1ccf61da4ea901a85b9d4068e0ca |
||
---|---|---|
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 | ||
rbesetup.sh | ||
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.