| commit | 0e3b095886d9bcd2728390b4cd2f028dbd5d755e | [log] [tgz] |
|---|---|---|
| author | Peter Collingbourne <pcc@google.com> | Fri Feb 18 19:17:04 2022 -0800 |
| committer | Peter Collingbourne <pcc@google.com> | Fri Feb 18 20:03:10 2022 -0800 |
| tree | 73a37001a0941c4d8c675cd9612025d389a782e9 | |
| parent | c3ee009f38b2c8c94f6dc6c5b11e3f8851f22304 [diff] |
Change how we set ro.product.first_api_level. The goal of this change is to cause ro.product.first_api_level to be set in /system/build.prop in targets with PRODUCT_FULL_TREBLE=false (which may be the case for targets without the usual set of hardware interfaces, such as the mini targets being added in https://r.android.com/1966051). Setting ro.product.first_api_level is necessary for devices with newer kernels to boot because it controls which metadata encryption format is used, and an old format that is incompatible with new kernels is used by default (see commit 4073c0b5241b635cb59e9e8a75ddcc783b5a99ce in system/vold). There also appear to be e.g. bionic tests that check this property. So it seems reasonable to set it even if PRODUCT_FULL_TREBLE is false. To begin with, stop adding it to ADDITIONAL_SYSTEM_PROPERTIES. There's basically no point in adding it there because it will be filtered out by the property blocklist for the system partition, whether PRODUCT_FULL_TREBLE is true or false. This lets us remove the blocklist entry, which causes ro.product.first_api_level to appear in /system/build.prop via ADDITIONAL_VENDOR_PROPERTIES on PRODUCT_FULL_TREBLE=false targets. Bug: 217455793 Change-Id: I8c07baf9d308ea734ffed5d9b1776b60cdbf3435
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.