| commit | c0f77ee489552782f76526d97374a875de2a796e | [log] [tgz] |
|---|---|---|
| author | xunchang <xunchang@google.com> | Wed Feb 20 15:03:43 2019 -0800 |
| committer | xunchang <xunchang@google.com> | Wed Feb 20 15:47:30 2019 -0800 |
| tree | ed2398d39b49a7b6fecc9295be6ace34a5c93d3d | |
| parent | 5fa7e2fa2cfdd17d7cd24760ec3b968dfe110635 [diff] |
Check the completeness of original blocks during target files validation The validate_target_files.py checks the 'incomplete' field of the range in file_map. And range has already considered the shared blocks and could be smaller in size than the original file range. Therefore, the 'incomplete' flag was set on the original range in common.py; and we should switch to use the original range also during validation. I also checked another flag usage in CanUseImgdiff(), and it has explicitly rejected cases of shared blocks. Bug: 124868891 Test: unit tests pass Change-Id: I03959625d7b81fd83420db98f01d23f54064bcd2
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.