| commit | a5fa89818921fbc54d7e6d79efe5d3aa826b4d45 | [log] [tgz] |
|---|---|---|
| author | Anton Hansson <hansson@google.com> | Tue Jul 24 13:31:08 2018 +0100 |
| committer | Anton Hansson <hansson@google.com> | Tue Jul 24 13:52:55 2018 +0100 |
| tree | 202fb19293a4643defb17250a1c24abce562e9a2 | |
| parent | 7b4b1b1548c38fdb188c7fdfb77bfe5922b0cded [diff] |
Don't apply path enforcements for non-full builds. The installed files lists are wildly inaccurate unless all the makefiles in the tree have been parsed, so the "redundant whitelist" computation will be too trigger-happy in this case. Bug: 111757442 Test: mmm -j system/extras/partition_tools Test: m out/target/product/generic_arm64/offending-artifacts.txt Change-Id: Id3a9f61d2366de77cdedf9cb1e4e39f7d18ade6f
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.