| commit | 78b55b224408dc956f64f826fc666bc8df70e61d | [log] [tgz] |
|---|---|---|
| author | Yifan Hong <elsk@google.com> | Wed Oct 28 14:19:05 2020 -0700 |
| committer | Yifan Hong <elsk@google.com> | Wed Oct 28 17:05:18 2020 -0700 |
| tree | fe8d309f16ca43d9d13d96bae5fe0c039bc82304 | |
| parent | 78860164d08cdc7b938bde0496a5a53122c6373e [diff] |
Mount generic ramdisk as readwrite. With this change, first stage init can prepare and move resources to accomodate devices with and without a dedicated recovery partition. Test: build with and without recovery partition, and manually inspect Bug: 171512004 Change-Id: I7bd61f74c16ee77f3f05dc208e0f3cfe81e302b0
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.