| commit | c63ce1ab58c8d01d6d2694953a3a660b3008e72b | [log] [tgz] |
|---|---|---|
| author | Cole Faust <colefaust@google.com> | Tue May 09 14:56:36 2023 -0700 |
| committer | Cole Faust <colefaust@google.com> | Tue May 09 15:12:58 2023 -0700 |
| tree | 5f5051168e23c3240958c68ada2f5808dcee3472 | |
| parent | 20f0cd3f915925cfa2b4ea8158aa6630626c9444 [diff] |
Allow importing starlark code in makefiles Adds a new `$(call run-starlark,my/starlark/file.bzl)` function that will run the starlark file and set all the variables in the variables_to_export_to_make dictionary as make variables. Fixes: 280685526 Test: m nothing repeatedly causes no ninja regeneration, but touching all_versions.bzl does. go test, ./out/rbcrun -mode=rbc ./build/make/tests/run.rbc Change-Id: Ic72e18dd28dba8233ba2dfb658b5d03ccece1bfd
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.