| commit | f1f49bb9101448bd6b508625b1eae0ae30e127fa | [log] [tgz] |
|---|---|---|
| author | Cole Faust <colefaust@google.com> | Wed Dec 01 13:49:12 2021 -0800 |
| committer | Cole Faust <colefaust@google.com> | Thu Dec 02 20:47:31 2021 -0800 |
| tree | 86585709527b1409def28994154a025b22c6fac7 | |
| parent | 5a0cef1c00a80c1fa574560bb3ad9310925df6f4 [diff] |
Pass input variables to product config Passing variables via a makefile instead of rblf_cli / rblf_env allows us to give them correct types while converting the makefile to starlark, as opposed to the variables always being strings when given via rblf_cli / rblf_env. This also allows us to remove some hand-converted starlark code. Bug: 201700692 Test: ./out/soong/rbcrun ./build/make/tests/run.rbc Change-Id: I58c4f20b29171c14e5ae759beb26a849426f6961
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.