commit | b87b773042981bf4c72c1742b0dd93bc666c0857 | [log] [tgz] |
---|---|---|
author | Sasha Smundak <asmundak@google.com> | Fri Mar 04 13:51:18 2022 -0800 |
committer | Sasha Smundak <asmundak@google.com> | Mon Mar 07 11:26:59 2022 -0800 |
tree | 4347e4e32cd165fa7a9a15d5d60ba41832aace54 | |
parent | d40c94633b7b7a1778f4f45b054282ce0a8fd68d [diff] |
Add an option to use Starlark-based configuration by default. In order to use Starlark-based product and board configuration for a product, add its name to the STARLARK_OPT_IN_PRODUCTS list in the AndroidProducts.mk file where this product is defined. Fixes: 220379303 Test: Temporarily added STARLARK_OPT_IN_PRODUCTS to build/make/target/product/AndroidProducts.mk Change-Id: Iacd23cec00a7a1958701873bce0fc9d5f79b1f17
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.