| commit | c7226590e6eb335e5e9826089292377141bb6ad1 | [log] [tgz] |
|---|---|---|
| author | Cole Faust <colefaust@google.com> | Wed Jan 12 21:20:07 2022 -0800 |
| committer | Cole Faust <colefaust@google.com> | Wed Jan 12 21:25:02 2022 -0800 |
| tree | c7c3550053148d94b172603f19a09efcbe434ffc | |
| parent | 7297032a8d2e469a05f27a323f4cde32e2e25dda [diff] |
Dump soong config variables in dump-variables-rbc There are some products whose board configurations use soong_config_get to read the values of soong config variables that were set in the product configuration. These variables were being lost, as dump-variables-rbc was skipping the soong config variables because mk2rbc couldn't handle converting the raw SOONG_CONFIG_* variables. To fix that issue, dump-variables-rbc now dumps them as calls to soong_config_set instead. Bug: 201700692 Test: m RBC_BOARD_CONFIG=1 nothing on certain products Change-Id: I91ca8418635a94cf80362cad1729f48854f6bc98
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.