commit | 04d4c089290b90371c3f35ead809bf547f7ef32a | [log] [tgz] |
---|---|---|
author | Yifan Hong <elsk@google.com> | Wed Jan 22 12:39:39 2020 -0800 |
committer | Yifan Hong <elsk@google.com> | Thu Jan 23 13:21:09 2020 -0800 |
tree | f244e226bf64c0cf9e7b83b0d1a3c70112dcd1c6 | |
parent | 9a190e25d010346b37f07d0d583f9c1bbdb899d4 [diff] |
Add e2fsck_ramdisk for VAB devices e2fsck_ramdisk is critical for VAB devices to boot after an OTA in case of corruption in metadata partition. Test: pass Bug: 147347110 Change-Id: I44ce456c11961ec978dcb4e68c32d72c1fab0c4d
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.