| commit | ea6cbd0765dc0b3111de877737fdf7da595acb40 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Wed Sep 05 13:06:37 2018 -0700 |
| committer | Tao Bao <tbao@google.com> | Wed Sep 05 13:14:55 2018 -0700 |
| tree | cc7b9fa95f2f62f0a817dd06fcc70497190a61ad | |
| parent | 0e0ef050f9d9601bed195d03dc64156a0be8820c [diff] |
releasetools: Handle the case of not having ro.vendor.build.fingerprint.
Commit d572632f3d81608ebda57b2591562fa7e2c02518 added support in build
system to blacklist given vendor properties. When
ro.vendor.build.fingerprint gets blacklisted, the OTA generation script
can't rely on those properties to determine a change in vendor images.
This CL considers such a case as "vendor images must have changed"
between the two builds.
Bug: 113892939
Test: Generate an incremental package with builds not having
ro.vendor.build.fingerprint.
Test: python -m unittest test_ota_from_target_files
Change-Id: I188de9c3cbeecf26132c92b9356e9d5fef75205e
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.