| commit | c0655eb04265a79bcfe8aeeb03c25c172ef7dd3f | [log] [tgz] |
|---|---|---|
| author | Anton Hansson <hansson@google.com> | Mon Jun 25 18:16:04 2018 +0100 |
| committer | Anton Hansson <hansson@google.com> | Mon Jun 25 19:17:42 2018 +0100 |
| tree | 0ef0ae88fadf18734bfa93cc119b531c0ddc0cc0 | |
| parent | 674454f223f5185c2ed15ed6fd0bddda048e6469 [diff] |
Include PRODUCT_COPY_FILES in artifact check. The product-installed-files macro is not really thorough - it only includes packages, but not other files which are included as part of the build. Extend it to also include PRODUCT_COPY_FILES. Bug: 80410283 Test: downstream CL Change-Id: I803c7a59e695c226fa413fa1602ec315ef9886a8
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.