| commit | ab50b8fa85c06ceaa3be2252f7ec0e6747b381fb | [log] [tgz] |
|---|---|---|
| author | Jeongik Cha <jeongik@google.com> | Tue Mar 24 22:42:41 2020 +0900 |
| committer | Jeongik Cha <jeongik@google.com> | Fri Apr 24 05:08:02 2020 +0000 |
| tree | cd36a8e6ec06dff88245d96522b7f98c08feeb24 | |
| parent | c0d90ac9ac14ef396de8ced527468996fed64747 [diff] |
Extend static_whitelist_patterns
product-installed-files generates more default artifacts than
$(call module-installed-files,$(call auto-included-modules)),
and it causes problems when we try to apply this mechanism to other
partition
So use product-installed-files with an empty parameter as static
whitelist
Test: apply require-artifacts-in-path to other partition(or path),
and then, m nothing
Test: add system module outside mainline_system.mk, and check if there is error.
Bug: 148993225
Change-Id: Ie110f20ff833229b23a777ff1decb32f84b9cef7
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.