diff options
author | Jiyong Park <jiyong@google.com> | 2018-05-29 13:56:37 +0900 |
---|---|---|
committer | Jiyong Park <jiyong@google.com> | 2018-06-09 01:57:00 +0900 |
commit | 2e6743176a385a94d42f40ad8b3ee5bc74308dad (patch) | |
tree | 469ce125c62065d12c01fff0de96b909d2d30b64 /cc/binary.go | |
parent | 6a25de47dcf50d1a8f86165a348bcf3a09bf2136 (diff) | |
download | build_soong-2e6743176a385a94d42f40ad8b3ee5bc74308dad.tar.gz build_soong-2e6743176a385a94d42f40ad8b3ee5bc74308dad.tar.bz2 build_soong-2e6743176a385a94d42f40ad8b3ee5bc74308dad.zip |
Recovery partition has same layout as system
Recovery partition has same layout as system. In other words,
executables are installed to <recovery_root>/system/bin and libs are
installed to ../system/lib.
This is made possible because the recovery partition is now
self-contained, i.e., shell, adbd, etc. are hosted in the recovery
partition and thus we no longer has to mount the real system.img
to /system. So /system is now available to executables built for
recovery mode.
Bug: 63673171
Test: `adb reboot recovery; adb devices` shows the device ID
Test: Select 'mount /system' in the recovery mode, then `adb shell`.
$ lsof -p `pidof adbd` shows that libm.so, libc.so, etc. are loaded from
the /lib directory.
Change-Id: I6c4f903ad21fd3dd10a07c4588be85d3d678c099
Diffstat (limited to 'cc/binary.go')
-rw-r--r-- | cc/binary.go | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/cc/binary.go b/cc/binary.go index 04b912a6..4a6eb931 100644 --- a/cc/binary.go +++ b/cc/binary.go @@ -357,11 +357,6 @@ func (binary *binaryDecorator) link(ctx ModuleContext, } func (binary *binaryDecorator) install(ctx ModuleContext, file android.Path) { - // <recovery>/bin is a symlink to /system/bin. Recovery binaries are all in /sbin. - if ctx.inRecovery() { - binary.baseInstaller.dir = "sbin" - } - binary.baseInstaller.install(ctx, file) for _, symlink := range binary.Properties.Symlinks { binary.symlinks = append(binary.symlinks, |