commit | 13ea2a6a7daefe4e691e91930821c60b7f81702b | [log] [tgz] |
---|---|---|
author | Anton Hansson <hansson@google.com> | Thu Mar 28 14:47:25 2019 +0000 |
committer | Anton Hansson <hansson@google.com> | Thu Mar 28 15:26:49 2019 +0000 |
tree | 5a5ce2d349d981cb0290f9e5be7c87548e453a1e | |
parent | fde506a6d752739794383bf959cb77b914d4d32a [diff] |
Automate the strip and assignment of PRODUCT_ vars With this change, all PRODUCT_ variables are treated the same when it comes to stripping and assigning them to their final variable name. In the past, all the PRODUCT variables needed to be listed in two places to achieve this. The documentation previously attached to the strip/assignment is moved to the PRODUCT_ variable list in product.mk. Also refactor some of the default value logic to cope with the new automation. Many places in the build system that currently refer to $(PRODUCTS.$(INTERNAL_PRODUCT).X) can now be modified to use $(X) directly. Bug: 116769560 Test: verified noop on PRODUCT_ variables on all products in the tree Change-Id: I5677c355e81359b1d3c0db2a2232941097a05047
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.