commit | 1b83413b5a765204e3def88ab758139df27123c2 | [log] [tgz] |
---|---|---|
author | Vic Yang <victoryang@google.com> | Fri Jan 18 19:37:47 2019 -0800 |
committer | Vic Yang <victoryang@google.com> | Wed Mar 20 10:22:21 2019 -0700 |
tree | bf7537444d647748f1f8e7951d6a80f75ebe8a63 | |
parent | bec4aa868a06433b61eec0e796e63fc3b1a24935 [diff] |
Add module-target-built-files function This is similar to module-built-files, except that it only returns files built for the target, not the host. Bug: 119423884 Test: Build with the no-vendor-variant VNDK change that uses this function. Change-Id: I2a3d99003b05999eae01c0b90bb62b5263d65592
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.