| commit | ac406f5c68dfebbdbc9c61d845c453c3a305a073 | [log] [tgz] |
|---|---|---|
| author | Dan Willemsen <dwillemsen@google.com> | Wed Apr 04 21:37:42 2018 -0700 |
| committer | Dan Willemsen <dwillemsen@google.com> | Thu Apr 05 17:26:35 2018 -0700 |
| tree | 888014d219eb62e8deb6785dc48ad267e39b10aa | |
| parent | e543e409d21795cc8b07aa58d0a2ac230f46361d [diff] |
Allow boards to turn overriding commands into an error Many boards have warnings like this, saying that we defined a build rule, but later something else came in and overrode it with something else: art/build/Android.gtest.mk:677: warning: overriding commands for target `test-art-target-gtest-cmdline_parser_test' art/build/Android.gtest.mk:674: warning: ignoring old commands for target `test-art-target-gtest-cmdline_parser_test' Beyond the obvious problem of replacing the rule with something else, target-specific variables can be combined as well, leading to some very strange problems. Since so many boards still have problems like this, but we don't currently have any global problems, add a flag so that we can mark boards as not broken. This should prevent regressions while we clean up the individual problems. Once the non-broken devices number significantly more than the broken devices, we'll switch this default. And once they're all cleaned up this variable will become obsolete, and these warnings will always be errors. Bug: 77611511 Test: lunch aosp_arm-eng; m nothing Test: lunch aosp_marlin-eng; m nothing Test: build_test on all downstream branches Change-Id: I43b645658f468c23a5b9ebcfcd9d4516537db540
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.