| commit | f4249d1052eb481addd532bbe8915351f7f6d36e | [log] [tgz] |
|---|---|---|
| author | Dan Willemsen <dwillemsen@google.com> | Thu Feb 07 17:34:57 2019 -0800 |
| committer | Dan Willemsen <dwillemsen@google.com> | Thu Feb 07 18:43:53 2019 -0800 |
| tree | 07e4665bbaafce0ed7db5b67fc831bdd1c2b382f | |
| parent | 2b526bf7f36095fae1b1ab43c2c43c33a5c799a8 [diff] |
Make the duplicate header copy warning more explicit So that it's easier to understand which makefile is actually being used, and which ones are being ignored. Test: manually check the warnings on a device that sets BUILD_BROKEN_DUP_COPY_HEADERS Change-Id: If9e29458eaa655b28e6b770d194d1da867cb8d16
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.