commit | e709b094e4b049ddfd6e65fc5bec1deb87fa57b1 | [log] [tgz] |
---|---|---|
author | Tao Bao <tbao@google.com> | Wed Feb 07 12:40:00 2018 -0800 |
committer | Tao Bao <tbao@google.com> | Tue Feb 13 11:14:23 2018 -0800 |
tree | e92f6dc3a0932f4e7188f3af05a7cace743ed535 | |
parent | 4ccea8549e889b4d4a17ccc11f3fb71dd97369ef [diff] |
releasetools: Allow generating BBOTA for images with shared blocks. When target defines 'BOARD_EXT4_SHARE_DUP_BLOCKS := true', the generated system/vendor images may contain shared blocks (i.e. some blocks will show up in multiple files' block list), which violates the current assumptions in BBOTA script. This CL allows generating BBOTAs by considering the first occurrence as the "owner" of the shared blocks. All the later users of the shared blocks will have an incomplete block list, whose RangeSet's will be tagged with 'uses_shared_blocks'. Files with 'uses_shared_blocks' tag will not be diff'd with imgdiff, potentially with patch size penalty. Such files will be accounted for in imgdiff stats report, where we can revisit for a better solution. Bug: 64109868 Test: Generate BBOTA full and incremental package with targets defining 'BOARD_EXT4_SHARE_DUP_BLOCKS := true'. Change-Id: I87fbc22eef7fafe2a470a03fdcfa1babf088ea8d
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.