| commit | e86d1bccc0ab1c60903939308870e7de8cf94231 | [log] [tgz] |
|---|---|---|
| author | Tianjie Xu <xunchang@google.com> | Wed Feb 26 21:50:47 2020 -0800 |
| committer | Tianjie Xu <xunchang@google.com> | Thu Feb 27 13:24:11 2020 -0800 |
| tree | c4aba685936d58be1559880fe987c457a2f4c1db | |
| parent | 7b285149a36f865202ba91bd52a69a744adf7a99 [diff] |
Preserve the monotonic property when subtracting 0 block The monotonic property of the range is lost after the recent change to subtract 0th block from the file range. As a result, we read the block in the wrong order when pull files from the raw image. This yields a incorrect hash during validation. Bug: 150334561 Test: run validate_target_file. unittests Change-Id: Id4fedaaf273c42c8d21a4549fda4c9a45e22066a (cherry picked from commit f02ececc7f76bf77f988e4a02c50771a808e9673)
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.