| commit | 38e7d980027f171effd2c4a2e9da77bea173f0fc | [log] [tgz] |
|---|---|---|
| author | Bruno Martins <bgcngm@gmail.com> | Tue Nov 14 14:02:35 2023 +0000 |
| committer | LuK1337 <priv.luk@gmail.com> | Sat Oct 19 00:16:02 2024 +0200 |
| tree | 83274218f4b581b67270bf22a516209b5b8ecfd7 | |
| parent | a927af6775b0d66ce50e9257eb7cf3d1da923746 [diff] |
build: Introduce android-info-extra.txt support This allows adding android-info-extra.txt to OTA packaging folder in case it exists in the target device tree, so that it can then be used in conjunction with custom releasetools. Historically, devices used to do assertions based on the modem version or even trusted zone version in order to prevent flashing builds if certain conditions were not met. That however, breaks `fastboot flashall` command since it looks for the requirements set in board-info.txt. With this, targets can define whatever non-standard requirements in the newly introduced android-info extra file, keeping OTA assertions in place and `fastboot flashall` command working without having to pass `--force` argument. Change-Id: I029d778b44be4d9d877701d05124451052a4b73c
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.