| commit | 9b8e6cf0670616d1b2ec7aca6b814dac78cc6f3b | [log] [tgz] |
|---|---|---|
| author | Anton Hansson <hansson@google.com> | Mon Aug 20 15:20:19 2018 +0100 |
| committer | Anton Hansson <hansson@google.com> | Wed Aug 22 10:49:18 2018 +0100 |
| tree | 15819226e397b20e40407013481cc52b14605dc8 | |
| parent | 85d8ce044fa8ae187d22d7b504dcf865313d6870 [diff] |
Fix dump-products. m dump-products didn't print anything useful prior to this change, however this was visible in the terminal: 15:18:58 Error dumping make vars: Failed to parse make line: "==== build/target/product/aosp_arm.mk ====" Convert this goal to normal target instead, which apart from making $(info) actually print something, considers the build successful when running "m dump-products" too. This makes it easier to run with e.g. multiproduct_kati. Test: m dump-products Change-Id: I944c87cd0fd323687690b0fcc3c37a8f37242cd9
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.