| commit | acb3084aa26b5d72095bcc6d20005868e6b3b962 | [log] [tgz] |
|---|---|---|
| author | Anton Hansson <hansson@google.com> | Mon Dec 17 18:19:33 2018 +0000 |
| committer | Anton Hansson <hansson@google.com> | Tue Dec 18 14:34:29 2018 +0000 |
| tree | 2ab6aadc7a5cf18499baf771bc27bfffad7ef72a | |
| parent | 9aaf0d40192462c433d1675b8764614bb6f6d5ef [diff] |
Allow mainline_arm64 to have product contents The device currently targeted does not have a product partition. Adding product-specific apps to it therefore trips up the artifact path check for /system. Workaround that by whitelisting /system/product/% for now. This should be removed when the device has the right partitions. Bug: 110072687 Test: build mainline_arm64 Merged-In: I54175bc51df5dfe82c64f66f255a2cea6ff9b9ab Change-Id: I54175bc51df5dfe82c64f66f255a2cea6ff9b9ab
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.