| commit | 27809667b4937a20732ea619cba7e41ca9e8d212 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Mon Oct 29 15:54:05 2018 -0700 |
| committer | Tao Bao <tbao@google.com> | Mon Oct 29 16:02:47 2018 -0700 |
| tree | a3ad5c09aca0b154d32c52342efda6e08e625f6c | |
| parent | 89fe71180b829916b09d76a8f76e217b34ab3ce1 [diff] |
Revert "Work around e2fsck issue for building sparse GSIs" This reverts commit ec7fa1cd0904419a2831b8da757ae670a875baed. The earlier e2fsck issue has been addressed by [1]. [1] https://android-review.googlesource.com/c/platform/external/e2fsprogs/+/725259/ Bug: 112062612 Test: m PRODUCT-aosp_x86_64-eng \ SANITIZE_HOST=address ASAN_OPTIONS=detect_leaks=0 \ -j e2fsck systemimage Change-Id: I7287cb8639ae45abdf753821421bd070b819a30e
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.