commit | dd33d75d39ad71e66bb73b70ed90fc3cd1a4e3df | [log] [tgz] |
---|---|---|
author | Steven Laver <lavers@google.com> | Mon Apr 27 16:26:31 2020 -0700 |
committer | Steven Laver <lavers@google.com> | Thu Apr 30 10:54:48 2020 -0700 |
tree | 82b69a5fb958d113b5f2bbc8ed98511b3b1ce69c | |
parent | e414a3fd3d06e4cc0f1a50978470018edfc137dd [diff] |
releasetools: correct allowed property sources for incremental OTAs When loading build info from a previous version of Android, the set of allowed property sources should match those available in that version. In this particular case, the product_services partition was a valid property source in Android 10. Bug: 155053195 Test: ran unit tests from test_common.py Test: generated an incremental OTA which previously failed Change-Id: Ic0b0a112656533eca78dee31517deff7e3c8d7cc Merged-In: Ic0b0a112656533eca78dee31517deff7e3c8d7cc
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.