| commit | c02b1c463e02f9ce48cadf3d4c1b4cbfff532f93 | [log] [tgz] |
|---|---|---|
| author | Jiyong Park <jiyong@google.com> | Tue Nov 03 11:06:39 2020 +0900 |
| committer | Jiyong Park <jiyong@google.com> | Tue Nov 03 11:06:39 2020 +0900 |
| tree | 317f280cd1544c4a1b049e58b48f528283acf5b2 | |
| parent | 0806152b8307950b1543e200312048ea5eb46a19 [diff] |
Export SOONG_HOST_OUT as ANDROID_SOONG_HOST_OUT Some host tools (launch_cvd, etc.) have been using HOST_OUT. As their dependencies are now installed by soong, the tools should refer to SOONG_HOST_OUT. Export it as ANDROID_SOONG_HOST_OUT. Bug: 172065015 Test: build aosp_cf_x86_phone, execute launch_cvd Change-Id: Ie175049f15b89485feec0d33d82e756b12a7ad8a
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.