commit | c193ae4c04d7495a230468e8450cd5613226535e | [log] [tgz] |
---|---|---|
author | dimitry <dimitry@google.com> | Thu May 23 13:49:53 2019 +0200 |
committer | dimitry <dimitry@google.com> | Thu May 23 16:01:50 2019 +0200 |
tree | 566f12f3b8531ff108d4ac0ef693d310f8a10f85 | |
parent | 6ae7967309c6a89ed3d9e463b44f71f92423ad98 [diff] |
Fix typo in APEX_LIBS_ABSENCE_CHECK_EXCLUDE arm64 guest libraries are located in lib64/arm64 Bug: http://b/77159578 Test: lunch cf_x86_64_phone-userdebug in internal master; mm -j48 dist Change-Id: I9f1f9426cbaed0a269126cb242e1a6df9249b167
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.