| commit | 53acaeab0a73b034cb7ddf3c101f85b5a7f22144 | [log] [tgz] |
|---|---|---|
| author | Jiyong Park <jiyong@google.com> | Tue May 29 16:29:24 2018 +0900 |
| committer | Jiyong Park <jiyong@google.com> | Thu Jun 14 02:03:57 2018 +0900 |
| tree | 012ff7a8d4dd23c73d813e94fa37e946f1f5c88f | |
| parent | cfbe8cf3bb1a302c8e41caed528c2d8ea6c70d4b [diff] |
Support shared library in recovery mode The dyanmic linker and the linker config script for the recovery mode (*.recovery variants) are added to PRODUCT_PACKAGES. Also this removes the mountpoint /system_root from the recovery image as the recovery image is self-contained and the real system image is mounted at /mnt/system which is created automatically at runtime. 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: Ice6c75b0b81bb9be696aaff3e095d87f19278995
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.