| commit | a2076137a177ff07efe4eb37bd2a0f8f23dbf573 | [log] [tgz] |
|---|---|---|
| author | Tianjie <xunchang@google.com> | Wed Aug 19 17:25:32 2020 -0700 |
| committer | Tianjie <xunchang@google.com> | Wed Aug 26 16:17:35 2020 -0700 |
| tree | 7e0018bb51a50af8ca0d8c1464ff62e73abe9f4b | |
| parent | ff2c7454fecbda4e651bf7c3b51555571eb9db49 [diff] |
Define the protobuf for OTA metadata Background in http://go/android-partial-updates. For partial update (e.g. system-only) or devices with mixed build, the current fingerprint & device name no longer suffice as the precondition to install the package. Therefore, we need to additionally include the per-partition build props into the ota metadata. We also define a protobuf for the metadata so it can be extended later. The metadata of the legacy format is also kept for backward compatibility. Bug: 151088567 Test: unittest pass, generate an OTA and check the result Change-Id: I716f7da54a393cd340280dbddc3c92b3460f8ef8
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.