commit | 0301d64545256e15d800cd3b3fdfc90df6765cd8 | [log] [tgz] |
---|---|---|
author | Sasha Smundak <asmundak@google.com> | Wed Nov 11 14:41:08 2020 -0800 |
committer | Sasha Smundak <asmundak@google.com> | Thu Nov 12 10:19:02 2020 -0800 |
tree | 91dc9d14aadf6d9101dffc47a5d65c755f17f470 | |
parent | 66589d1328dec8dc0b77e60a3095ca7fa2579e47 [diff] |
Mark PRODUCT_xxx variables as single item instead of list Evidenced by soong_config.mk settings and assignements across code base. Test: treehugger Bug: 116769560 Change-Id: I7dc27049a32df7b39680d93bddb23e6e6f1e84ca
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.