commit | b0f436386fae7332cd039e046a3dfd7dec37356d | [log] [tgz] |
---|---|---|
author | Bowgo Tsai <bowgotsai@google.com> | Wed Mar 30 11:32:32 2022 +0800 |
committer | Bowgo Tsai <bowgotsai@google.com> | Wed Mar 30 11:52:39 2022 +0800 |
tree | 3d4f5b9eab0b5700ed5420e14ae7df4d3e8317eb | |
parent | 0b7aea6dc5331d20a03009862d1db83dd800fe8a [diff] |
Support per-partition settings for os_version AVB props The value of the AVB properties are parsed by the device bootloader, which might expect a different format of the value. Allowing them to have per-device settings. The default value of those per-partition os_version is $(PLATFORM_VERSION_LAST_STABLE), which is usually an integer, e.g., 12. Bug: 211364958 Test: build then `avbtool info_image` Change-Id: I2005df615c0ff35622030baa2477e29d9d20e94f
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.