| commit | e59a87946fdff155537c03acff71135b994a2e53 | [log] [tgz] |
|---|---|---|
| author | Frederick Mayle <fmayle@google.com> | Mon Aug 22 22:40:23 2022 +0000 |
| committer | Frederick Mayle <fmayle@google.com> | Mon Aug 22 22:40:23 2022 +0000 |
| tree | aa50041952e40e89084d942f790add99f4ec2172 | |
| parent | 34570d33f4b4e1cda2cbbb9ff2a8b088a5241fde [diff] |
envsetup.sh: partly fix syswrite
The grep doesn't work because "Reboot" is capitalized in the
enable-verity output. Now, syswrite gets farther, but fails before the
final remount.
$ syswrite
adbd is already running as root
Successfully disabled verity
Enabled overlayfs
rebooting
restarting adbd as root
error: closed
Test: ran syswrite on freshly flashed device
Change-Id: I26aaa6278d76dcab56fd4bde3d70ac7841ae2a3b
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.