| commit | 99ddfcbaba66b8bd0aea7c5d1a6b690534755329 | [log] [tgz] |
|---|---|---|
| author | Jae Hoon Kim <kimjae@google.com> | Wed Feb 19 00:31:41 2025 -0800 |
| committer | Jae Hoon Kim <kimjae@google.com> | Wed Feb 19 20:23:49 2025 -0800 |
| tree | 3422c65105aec355eea73cfeedebe676c20f48d3 | |
| parent | 585797b9f143e245573848bc205cd4d69efb3d8b [diff] |
core/Makefile: Add generated product FW image ... allowing for FW images to be uploaded based on PRODUCT package. To be used within provision/flash flows. This message aims to ensure consistency within the lab environment. Currently, the provisioning and flashing processes retrieve data from predefined buckets. However, these buckets may become outdated or cached by various services within the lab, potentially leading to unintended behavior. To address this issue, we intend to modify the process to directly retrieve artifacts for lab test runs from the build artifacts associated with the target build. Bug: 396461815, 397532690 Test: m dist Flag: EXEMPT desktop only change Change-Id: Id54f5065a722d7b1364746812fe5f97b816f7e68
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.