commit | 29bb6132c825ff8de41f50cbb58379fd4858dbba | [log] [tgz] |
---|---|---|
author | Cole Faust <colefaust@google.com> | Mon Nov 29 17:26:03 2021 -0800 |
committer | Cole Faust <colefaust@google.com> | Tue Nov 30 14:00:57 2021 -0800 |
tree | 4cb1a344ac5d943cb377d80477b6ef38536e2d31 | |
parent | 359665674fece57939282a45f9259f85455509a6 [diff] |
Strip more board config variables These variables' values show up in the command line of certain build commands, so they need to be stable to have stable ninja files. The starlark board configuration strips these variables, causing a discrepency between the starlark and make versions of board configuration. Bug: 201700692 Test: ./build/bazel/ci/rbc_regression_test.sh beagle_x15-userdebug Change-Id: Id053435409821a3fe5997c07610ef835e0c83112
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.