commit | dede32071bc7b5b74af31e7deaa6c178af019bde | [log] [tgz] |
---|---|---|
author | Yumi Yukimura <me.cafebabe@gmail.com> | Sun Mar 24 02:19:46 2024 +0800 |
committer | Jan Altensen (Stricted) <info@stricted.net> | Tue Jul 02 00:26:22 2024 +0000 |
tree | fc0b17d9b72a0950ef5586c9cac84a9887ad3d33 | |
parent | 941ff41f72ba8ef327153409d7b225077e1d71e1 [diff] |
releasetools: Pass non-sparse super_empty.img to update_dynamic_partitions() * So that updater program can load dynamic partitions metadata from OTA when it fails to load from the device Change-Id: I73687009a2cb243aba1bfec6f357c8ff25f27784
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.