commit | 74e4cf10bf1c3b120aa31121011dbf3a625c6a07 | [log] [tgz] |
---|---|---|
author | Colin Cross <ccross@android.com> | Mon Oct 29 23:17:02 2018 -0700 |
committer | Colin Cross <ccross@android.com> | Tue Oct 30 15:48:33 2018 -0700 |
tree | 482d4efe5af3407cf7715e7828f9a5d4e6c10c44 | |
parent | afc4604f6731f0d427dc48e3996d4ba3ffe9297b [diff] |
Store AAR path from Soong for dist Store the path to the AAR file from Soong so that it will be picked up by dist if requested in TARGET_BUILD_APPS. Test: m checkbuild Change-Id: Ifeaf2b5ca3f405fbe79a966ceee9989a38d77f6e
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.