commit | 474afa8f06e297924c7fe03e47ce8d6e7c703024 | [log] [tgz] |
---|---|---|
author | Daniel Zheng <zhengdaniel@google.com> | Wed Feb 28 12:59:52 2024 -0800 |
committer | Daniel Zheng <zhengdaniel@google.com> | Wed Feb 28 20:47:20 2024 -0800 |
tree | 98237e725bd3a8d5a14a5e80d10131391f8c9f40 | |
parent | e6045f8b74ae7962701f0e1f05f90e1e3cae1072 [diff] |
fallback on older cow version If a device's source or target cow version is specified at 2 (or undefined) we should fallback on using the v2 writer. e.g. 1. v3 -> v2 downgrade OTA 2. v2 -> v3 Bug: 322279333 Test: ota_from_target_files Change-Id: I8c5139eceeb64ee255ddea66017b3e17bbdc44c0
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.