| commit | 985fa48a98520c8cf56fddfd261048dd94c69d48 | [log] [tgz] |
|---|---|---|
| author | Cole Faust <colefaust@google.com> | Thu Oct 07 17:14:23 2021 -0700 |
| committer | Cole Faust <colefaust@google.com> | Thu Nov 04 16:13:24 2021 -0700 |
| tree | 00db60d8bf486c76e8ba9800fb10d9238d02c228 | |
| parent | 936e704999b699b7d3fe01215484662a413ad8e7 [diff] |
Make starlark board configuration work with sdk_phone_x86_64 The main issue with board configuration up till this cl was that it didn't have access to the product configuration variables. Pass those in by dumping the make variables to a temporary file, which is then converted to RBC, loaded, and passed to the starlark board config.. Bug: 201700692 Test: build/bazel/ci/rbc_product_config.sh -pb sdk_phone_x86_64-userdebug Change-Id: I9a4946b970ca43c5b5f53a6c507ad2c1a2eca61e
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.