3 Commits

Author	SHA1	Message	Date
Jiyong Park	722b9ca4ca	AOSP: e2fsdroid and mke2fs are dynamic executable in recovery partition ... The two utilities are now converted to dynamic executables as shared libraries are supported in recovery mode. As part of the conversion, shared libraries that are depended from them are also marked as recovery_available: true. Bug: 79146551 Test: adb reboot recovery, and select 'Wipe data/factory reset'. The data partition is formatted and there is no selinux denial. Signed-off-by: Theodore Ts'o <tytso@mit.edu> Change-Id: I22fbc83a4ff0496096efca90721b0db1237c32cd From AOSP commit: df1f088849ed3336bb4f6f200c29b30682f15948	2018-06-27 23:51:40 -04:00
Theodore Ts'o	2df733facd	Update Android build files so the 1.43 branch builds on AOSP ... Recent changes in the 1.43 branch as well as the latest AOSP caused the Android build to break; fix them. Signed-off-by: Theodore Ts'o <tytso@mit.edu>	2015-05-25 20:25:28 -04:00
Theodore Ts'o	321f3446f3	Add files to build on Android ... The Android.mk files were taken from the Android AOSP sources, and updated for the 1.43 next branch. The intention is that this will allow the repository which is currently located in external/e2fsprogs with one which is based off of the upstream e2fsprogs. Right now external/e2fsprogs was not created using "git clone", so it means that git merges don't work. After the external/e2fsprogs Android repository is replaced, with one based off the upstream repository, Android will be able to synchronize with the upstream repository by pulling and merging from upstream, and then running the script "./util/gen-android-files" to update any generated files. (This is necessary because in the Android build system, the Android.mk files are rather stylized and don't make it easy to run arbitrary shell scripts during the build phase.) Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>	2015-03-01 15:45:11 -05:00