commit | 3c7b91bac1b9588ded74ac8e8a163019aae66389 | [log] [tgz] |
---|---|---|
author | Inseob Kim <inseob@google.com> | Fri Aug 25 21:28:49 2023 +0900 |
committer | Inseob Kim <inseob@google.com> | Mon Aug 28 07:33:12 2023 +0000 |
tree | 3ac6696122b36847fc3ba841f51996abf5b51bd2 | |
parent | 5d7f9cb2a1f719fa56572b2a7b7a3c1aa36690ae [diff] |
Use board api level for seapp coredomain check Rather than PRODUCT_SHIPPING_API_LEVEL, use board api level (BOARD_API_LEVEL or BOARD_SHIPPING_API_LEVEL) to determine whether we check coredomain violations or not. Also provides a Makefile variable to override the flag, for targets that want to turn on the check optionally. Bug: 280547417 Test: see build command of vendor_seapp_contexts Change-Id: I177630d33313334ca4a56a9be88b78cff678281e
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.