commit | d32936d6572a525e09c3e02682deff4f7342e586 | [log] [tgz] |
---|---|---|
author | Tao Bao <tbao@google.com> | Thu May 17 19:42:41 2018 -0700 |
committer | Tao Bao <tbao@google.com> | Thu May 17 19:45:16 2018 -0700 |
tree | 2d682fa21b99d6e86c76e01833ac27772061b487 | |
parent | 7e15b44c23ca89920255cc6a1838bb8be0dd7731 [diff] |
releasetools: Skip checking files with non-monotonic ranges. Bug: 79951743 Test: Run validate_target_files.py on target_files.zip that has non-monotonic ranges listed in IMAGES/system.map. Change-Id: I28d3ca6972d361362589cd51e60731af9994a551
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.