| commit | f71547079a1c9c5a175f41a8ef5fe51df57f2aa7 | [log] [tgz] |
|---|---|---|
| author | Isaac Chen <ycchen@google.com> | Thu Apr 19 14:18:54 2018 +0800 |
| committer | Isaac Chen <ycchen@google.com> | Mon Apr 23 19:19:29 2018 +0800 |
| tree | ab999a24ef5c24b31a876846a3fb2b47261dd142 | |
| parent | 020b22ead6fdb579b18ffb780df62c23d205d298 [diff] |
Enable VNDK for aosp_arm(64)
This is needed for the system images of aosp_arm(64) products to
be used as their respective GSIs in P, and for also aosp_arm(64)
products to boot with the current GSIs.
Bug: 78255604
Test: Built and booted the following products to home screen
$ lunch aosp_arm-userdebug; m -j; emulator
$ lunch aosp_arm64-userdebug; m -j; emulator
# The system image, both userdebug and user builds, of
# aosp_arm64 could also boot to home screen and browse
# the network on a physical device.
Change-Id: I83b79fd4d4e6e522ee78c720fb8c5f6f67ee411b
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.