| commit | 879b007555b3cb565fd73e71d3823a08e8e8a067 | [log] [tgz] |
|---|---|---|
| author | Anton Hansson <hansson@google.com> | Mon May 13 18:06:45 2019 +0100 |
| committer | Anton Hansson <hansson@google.com> | Mon May 13 18:15:32 2019 +0100 |
| tree | 829ec7745be582dff847a762d303832a4a4f3c5f | |
| parent | 738b9963d5dbfd58e8e7f266f43c1504dc523114 [diff] |
Make PRODUCT_CHARACTERISTICS a single-valued variable
Values should be comma-separated, and things won't go down well
if there are multiple words in this variable.
Bug: 123783710
Test: Put this in product_config.mk and ran multiproduct_kati:
ifneq (1,$(words $(PRODUCT_CHARACTERISTICS)))
$(error oops)
endif
Change-Id: I5627f416093d68d8d19916a914739686b74d392f
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.