| commit | e78ad74b2be076ac4aeb64ebf096cfcc141d66a6 | [log] [tgz] |
|---|---|---|
| author | Jooyung Han <jooyung@google.com> | Mon Sep 11 13:40:52 2023 +0900 |
| committer | Jooyung Han <jooyung@google.com> | Mon Sep 11 13:40:52 2023 +0900 |
| tree | 6008c255d1436031ec4301526a6732d4a3fdcad7 | |
| parent | 6f0db025d012e01136d6e777cd12196c48fddada [diff] |
Run apex_sepolicy_tests for all installed APEXes This is to check if unknown file context labels are used in APEX. The reason why this is done in Makefile is to cover vendor-specific SE policy and prebuilt APEXes. Note that there's already a validation check when building APEXes (in Soong), which only checks the generic rules, not vendor-specific. Bug: 299391194 Test: atest apex_sepolicy_tests_test Test: m Change-Id: I4378b7530e8433d2bf188db95cb5bf791e3bf778
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.