| commit | e88ac677c5e278b9e4caf5b67a32a591cf0e79de | [log] [tgz] |
|---|---|---|
| author | Tianjie <xunchang@google.com> | Thu Oct 15 17:22:48 2020 -0700 |
| committer | Tianjie <xunchang@google.com> | Thu Oct 15 18:31:00 2020 -0700 |
| tree | dc7f726a9164f2a4e722cd8964c33ff552d1187a | |
| parent | f3d4f2f26b208126bc5843e0acaf413618bf94ec [diff] |
Make the ro.build.version.release consistent between device build prop & partition build prop The ro.build.version.release has updated to use the last stable platform version in go/ab/10260813. But the logic for per-partition build prop has never been updated. This mismatch eventually reflects in the device's build fingerprints and cause confusion. This cl updates the partition build props to match the behavior of the top level build props. Also the device's fingerprints is heavily used in static analysis, e.g. ota targeting, the change to its computation may cause unexpected effects. Bug: 170968068 Bug: 158483506 Test: build system image for coral, check the build prop Change-Id: Icf741c915f2eba970258979efc274e424187ac69
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.