| commit | 83db9510d0e8a2dbbf2e9250b08bfb72a381c949 | [log] [tgz] |
|---|---|---|
| author | Jeongik Cha <jeongik@google.com> | Thu Sep 12 13:04:22 2024 +0900 |
| committer | Jeongik Cha <jeongik@google.com> | Thu Sep 12 22:10:44 2024 +0900 |
| tree | 81fecb59940230ab4c322d2c933ccecb20467d1e | |
| parent | 1d09815d07f3a1a474837b905704fed311ff0f8a [diff] |
Use Soong-defined system image's artifacts in target_files.zip To ensure the artifacts is ready, add SOONG_DEFINED_SYSTEM_IMAGE_PATH as an explict dependency of target_files Bug: 350599478 Test: m dist Test: check ninja deps Change-Id: I7adf5c55a3b52da2bd160f930b6f6f100e648e86
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.