| commit | dfa8e7796b2580b8f430a67a38426f14bd034afd | [log] [tgz] |
|---|---|---|
| author | Isaac Chen <ycchen@google.com> | Tue Apr 03 11:06:12 2018 +0800 |
| committer | Isaac Chen <ycchen@google.com> | Thu Apr 12 16:06:26 2018 +0800 |
| tree | 18f82b53bd0470ddc94d74e6db47522859b969c3 | |
| parent | 191badd71b4c921c3ccd095fa0dfffc213b6df76 [diff] |
ARM emulator: aosp_arm on 64-bit binder and kernel
Starting in P, all 32-bit and 64-bit architectures use 64-bit
binder interface. This is similar to ag/3576770 for x86.
Bug: 71861550
Test: the following products can boot to home screen successfully:
lunch aosp_arm-userdebug; m -j; emulator
lunch sdk_phone_armv7-userdebug; m -j; emulator
Change-Id: Ibe1f53a5798342555e2e84395a13b48d461f483d
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.