| commit | d6867167d1793dad242ac51fd559a1fedd4f1487 | [log] [tgz] |
|---|---|---|
| author | Tianjie <xunchang@google.com> | Sun May 10 14:30:13 2020 -0700 |
| committer | Tianjie <xunchang@google.com> | Wed May 20 19:01:17 2020 -0700 |
| tree | a9369422b9dff5673a725de524ddf6bbdd88c294 | |
| parent | ed67178e4a1132ea899e9e66db5123b527a2cd0c [diff] |
Add an option to input the boot variables for OTA package generation The values of the ro.boot* variables are not part of the image files and are provided (e.g. by bootloaders) at runtime. Meanwhile, their values may affect some of the device build properties, as a different build.prop file can be imported by init during runtime. This cl adds an option to accepts a list of possible values for some boot variables. The OTA generation script later use these values to calculate the alternative runtime fingerprints of the device; and list the device names and fingerprints in the OTA package's metadata. The OTA metadata is verified by the OTA server or recovery to ensure the correct OTA package is used for update. We haven't made any restrictions on what ro.boot* variables can be used for fingerprint override. One possible candidate can be the skus listed in ODM_MANIFEST_SKUS. Bug: 152167826 Test: unittests pass, generate an OTA file with the new option Change-Id: I637dea3472354236d2fd1ef0a3306712b3283c29
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.