| commit | c9dd2d5b2e6ad853ed77999ac82a66734fbea075 | [log] [tgz] |
|---|---|---|
| author | Justin Yun <justinyun@google.com> | Mon Aug 26 13:23:19 2024 +0900 |
| committer | Justin Yun <justinyun@google.com> | Wed Sep 11 05:06:42 2024 +0000 |
| tree | 0154c58b1fea51c750564ce0395fce041b2f222b | |
| parent | 963298af9789a093cd40be22aa1f976226e02f59 [diff] |
Add soong system image configs
USE_SOONG_DEFINED_SYSTEM_IMAGE is true when the target is using a
system image defined in soong.
PRODUCT_SOONG_DEFINED_SYSTEM_IMAGE is the module name of the soong
defined system image.
Bug: 350599535
Test: lunch aosp_cf_x86_64_phone_soong_system-trunk_staging-userdebug
&& m
Change-Id: Ic5c848fb649a5a61de1a5a253438b2d77d200a6b
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.