| commit | d8f8fb4eb5dea79aa3fc9373d7306534933800f9 | [log] [tgz] |
|---|---|---|
| author | xiaomanwang <xiaomanwang@t2mobile.como> | Thu Jun 17 10:15:28 2021 +0800 |
| committer | Karsten Tausche <karsten@fairphone.com> | Mon Nov 13 19:05:26 2023 +0100 |
| tree | c4378330b3798c2311345ccbc0e5fc9e74b053f9 | |
| parent | ff7f5f5318237357a991fa03e9550157cca8b4f7 [diff] |
Add support for prebuilt userdata image When a device model ships with different internal storage sizes, building a userdata.img through the Android build system doesn't make sense. Instead, allow providing a prebuilt (empty) userdata image, which triggeres the device to format userdata on boot, adjusting to the correct storage size. Issue: ALM:11105594 Issue: FP4-279 Issue: FP4-INT#13 Change-Id: Ica36fd96c8c1c7db0fcae5519af33223b28b67ee (cherry picked from commit a6ae279d5f00f8b65e8201a04058e0077cecb9cb) (cherry picked from commit f56568296640df4699121fbbab56a9f42e26b5cb)
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.