| commit | 5fcaa1f635ca9bb6ba9f1c68391325bb4217d0cb | [log] [tgz] |
|---|---|---|
| author | Kelvin Zhang <zhangkelvin@google.com> | Wed Aug 21 19:37:23 2024 -0700 |
| committer | Kelvin Zhang <zhangkelvin@google.com> | Thu Aug 29 13:38:45 2024 -0700 |
| tree | b5e3c03d11c1a570493e10a23cb59557c2e9ee4f | |
| parent | 8948d13afc3523ffb4e28909de28a0d1fd7c3821 [diff] |
Support incremental dev option OTA during signing This allows incremental dev option to be used on release-key devices. Boot images are signed during the signing process, and hence the dev option OTAs(which are derivative of boot image) need to be re-generated. Previously we only re-generate full OTAs, now we support incrementals too. Test: th Bug: 339658378 Change-Id: I4755379b49ff8adf351ccaf76fe38f19c1685e9e
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.