| commit | 8b6f143b0c0e07efa010fa32d8d89ad193b08093 | [log] [tgz] |
|---|---|---|
| author | Inseob Kim <inseob@google.com> | Wed Jul 10 17:34:51 2024 +0900 |
| committer | Inseob Kim <inseob@google.com> | Tue Jul 16 03:01:40 2024 +0000 |
| tree | aa34a75c142910604c8a2ab17cab6f235c4a30c7 | |
| parent | 1f3f3219676721009187f45ab625398b50511425 [diff] |
Add option to use Soong defined system image By `USE_SOONG_DEFINED_SYSTEM_IMAGE`, a system image specified by PRODUCT_SOONG_DEFINED_SYSTEM_IMAGE will replace $OUT/system.img. Bug: 350599472 Test: USE_SOONG_DEFINED_SYSTEM_IMAGE=true m && cvd start Change-Id: I294ea5e1ce7f9273d0dafc440320b8f194ccf5ca
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.