948615083a
This makes the product-installed-files macro more accurately reflect the files installed for a given product, as well as fixing bugs in the previous implementation. Specifically, the complete list of overrides found so far is stripped in each round of expanding required modules. Previously, overrides were stripped out *after* expanding required modules. This meant that for a scenario where B depends on C, and A overrides B, C could get installed. It's unclear if this was a problem in practice. The other effect is that the offending artifacts txt is more accurate, since overridden modules are now correctly removed. Bug: 80410283 Test: build_test downstream Change-Id: I8bfc7c40bedd5cb2afba567bae4b998f51770793 |
||
|---|---|---|
| core | ||
| target | ||
| tests | ||
| tools | ||
| .gitignore | ||
| Android.mk | ||
| buildspec.mk.default | ||
| Changes.md | ||
| CleanSpec.mk | ||
| envsetup.sh | ||
| help.sh | ||
| navbar.md | ||
| OWNERS | ||
| README.md | ||
| tapasHelp.sh | ||
| Usage.txt | ||
Android Make Build System
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.