| commit | fa7ddae29b506c5e10b04d4fcfcc7685e494dd11 | [log] [tgz] |
|---|---|---|
| author | Anton Hansson <hansson@google.com> | Tue Mar 19 18:20:30 2019 +0000 |
| committer | Anton Hansson <hansson@google.com> | Tue Mar 19 18:20:30 2019 +0000 |
| tree | 30984ede2448561e74bf1e84084f4061ce6d0b85 | |
| parent | ab28c2d4eff4679ba31dfdc540832211c192bf0c [diff] |
Fix missing modules check for dont_bother goals Like If1f817d855cbe329b83caee9fdd68c2cce55f02b, but for PRODUCT_PACKAGES, which is only enabled for a few builds. Also share the ALLOW_MISSING_DEPENDENCIES check with the host version. Test: m product-graph Change-Id: Iab55072e7d7c0fc9f4680cc515e139a5214dc3b4
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.