| commit | dba4b0023259b3fbbe5f00d8dced62430ae7fd4d | [log] [tgz] |
|---|---|---|
| author | Bill Peckham <bpeckham@google.com> | Thu Jan 02 17:59:11 2020 -0800 |
| committer | Bill Peckham <bpeckham@google.com> | Thu Feb 06 00:21:31 2020 +0000 |
| tree | 4726584ad0452df96cf5e26f115952e6a95e44ad | |
| parent | 99f9f35e2990eae3c1dabde76f3dc73047754561 [diff] |
Add functions for easier vendor var definitions. The add_soong_config_namespace adds a namespace and initializes it to be empty. The add_soong_config_var function adds a pre-existing variable as a Soong config variable, and the add_soong_config_var_value function defines a make variable and also adds it as a soong config variable. Bug: 144532889 Test: $(OUT)/soong/soong.variables contains variables. Change-Id: I5cc6a670a089ecd5163f19f7a2fba33f5860c952
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.