87d0f2703f
OEMs may need to have different device configurations that use different signing configurations for mainline modules. The network stack mainline module has a sepolicy context referencing its certificate, so the generated plat_mac_permission.xml differs based on the module signing configuration. The added PRODUCT_MAINLINE_SEPOLICY_DEV_CERTIFICATES variable defines a per-product directory for the certificates, so that which certificate to use can be configured in the product makefile, instead of replacing the certificate file itself. This change is to be submitted together with another change in sepolicy makefile. Test: changed certificate path, m, verified plat_mac_permissions.xml has new certificate. Bug: 134995443 Bug: 138097611 Change-Id: I863a9904d4a2ea2abad679ae0969d50e374f269d |
||
---|---|---|
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.