| commit | 22632cc82c0404bdbddaef41eb79cc99071894d0 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Thu Oct 03 23:12:55 2019 -0700 |
| committer | Tao Bao <tbao@google.com> | Thu Oct 03 23:21:22 2019 -0700 |
| tree | 5904d85be45e73c3825f4029294b22b5ae0526d4 | |
| parent | 9c683dc968111364e887497435f2e689197b4888 [diff] |
releasetools: Support verifying files with non-monotonic ranges.
Fixes: 79951650
Test: Run validate_target_files on target_files.zip with files in
non-monotonic ranges.
Test: python -m unittest test_validate_target_files
Test: python3 -m unittest test_validate_target_files
Change-Id: I82571d3358598775de4cdeb5e64035689fea6487
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.