| commit | f07dcc48e88f11b5f3de4ebba2b0409ae2d18ab8 | [log] [tgz] |
|---|---|---|
| author | Cole Faust <colefaust@google.com> | Thu Jan 05 12:02:54 2023 -0800 |
| committer | Cole Faust <colefaust@google.com> | Thu Jan 05 12:06:26 2023 -0800 |
| tree | c37dd9e383b8c2c7c08b26b3a6c4541dac28865c | |
| parent | 17fb8e72a1329b444d5b15714f58c7bd576956fa [diff] |
Fix printing variables that have inherit references in them Inherit references (@inherit in make, 1-tuples in starlark) usually appear in list product variables, where they're evaluated before printing. But sometimes they can be copied into a regular global variable, in which case they won't be evaluated before printing. The 1-tuples were failing to print, so adapt them to their make representation before printing. Fixes: 264554449 Test: ./out/rbcrun ./build/make/tests/run.rbc Change-Id: I5ac6eb996c25ee5e77aa26ed5c4b6b6cc31819d1
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.