commit | b285515ca12b199b94b9fb5bb1003cbccd60d7ce | [log] [tgz] |
---|---|---|
author | Bob Badour <bbadour@google.com> | Wed Dec 08 12:52:59 2021 -0800 |
committer | Bob Badour <bbadour@google.com> | Wed Dec 08 12:52:59 2021 -0800 |
tree | 4aa7e6fdccd66eed1a3fa63ffeafabbbef7195b0 | |
parent | 3a820dd5a0aa6612fc0dbacfee662b17cce22dd5 [diff] |
license metadata remove path on top-down walk Performance optimization means not every path will be traversed. Instead of updating parents via the path, perform a 2nd bottom-up walk after the top-down walk to propagate the new resolutions to parents. Note: the 2nd walk method will add resolutions to statically linked libraries etc. at deeper levels, but those do not affect what gets reported. In particular, note that test data for dumpresolutions changes, but none of the test data for listshare, checkshare etc. changes. Test: m all systemlicense listshare checkshare dumpgraph dumpresolutions Bug: 68860345 Bug: 151177513 Bug: 151953481 Change-Id: I76361c4e33bbadbbea38cbec260430e8f9407628
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.