| commit | cb73aed1f00ebafe2b9319ec20e41734da9d6b88 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Wed Jan 31 17:32:40 2018 -0800 |
| committer | Tao Bao <tbao@google.com> | Fri Feb 09 12:46:01 2018 -0800 |
| tree | 5b776797b4c6ada89a1e71e37e10172242154e9a | |
| parent | acb3cecc4640afbb38bf757bd760e101c7febff1 [diff] |
releasetools: Refactor the condition checking for using imgdiff. In Transfer class, unbundle 'intact' with the monotonicity of the input ranges. Negate the logic of 'intact', and thus rename it to 'trimmed'. Move this property from an attribute of Transfer class as the one in RangeSet.extra. 'trimmed' indicates whether the source / target ranges have been modified after creating the Transfer() instance. The logic that determines whether we can apply imgdiff has been refactored and consolidated into BlockImageDiff.CanUseImgdiff(). Now both of the two paths call this single copy, i.e. the one that detects large APKs (before creating Transfer()'s), and the other that's about to generate the patch for a given Transfer instance. Bug: 68016761 Test: python -m unittest test_blockimgdiff Test: Generate an incremental BBOTA package. Change-Id: Id07195f63f1fa6c3af6e9091940d251cf09fa104
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.