| commit | fdda51d2ae9e2d9aa96bb9f8f1f6439479910e1d | [log] [tgz] |
|---|---|---|
| author | Tianjie <xunchang@google.com> | Wed May 05 14:46:35 2021 -0700 |
| committer | Tianjie <xunchang@google.com> | Mon May 10 11:35:48 2021 -0700 |
| tree | bdc1087540802f0d275011ab21a69fa18d4c90a3 | |
| parent | a530481db10db31fae6b9f10644be5d96aa10463 [diff] |
Calculate the runtime ro.build.id in ota scripts If the build prop ro.build.id isn't set at build time, init will set it at runtime. The logic is appending the vbmeta digest to the ro.build.legacy.id. Make the same change in ota scripts, so the correct build fingerprint will be saved in the ota metadata. Bug: 186786987 Test: generate an OTA, check the metadata Change-Id: I278f59c41c1f98d4cbea749e5d9e4eaf7a6b9565
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.