| commit | 07ceaa71c101a01052e2e36e86ec2adc6d57ca3b | [log] [tgz] |
|---|---|---|
| author | Justin Yun <justinyun@google.com> | Fri Apr 02 16:29:06 2021 +0900 |
| committer | Justin Yun <justinyun@google.com> | Tue Apr 06 16:33:07 2021 +0900 |
| tree | e85cbc332a04240e912e58549714c289aefb6553 | |
| parent | 3c610dd0aae6c0330576704efdab09c66daefee2 [diff] |
Use BOARD_API_LEVEL to define ro.board.api_level GRF devices must define the API level of which the SoC is first shipped by setting BOARD_SHIPPING_API_LEVEL. As this is a permanent value, vendors may not change this value even if they implement new features under the GRF policy. BOARD_API_LEVEL can be optionally defined in this case to manually set the api level of the vendor implementation. The current api level will be set to `ro.board.api_level` property. Bug: 176950752 Test: atest --host post_process_props_unittest Change-Id: Ib126c1a622ded9848650f3f60c0f15005867272d
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.