Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 034cd871 authored by Jeongik Cha's avatar Jeongik Cha
Browse files

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
Merged-In: Ie110f20ff833229b23a777ff1decb32f84b9cef7
parent 04735a8e

core/main.mk

+1 −1
Original line number Diff line number Diff line
@@ -1179,7 +1179,7 @@ ifdef FULL_BUILD 
  static_whitelist_patterns += %__auto_generated_rro_product.apk

  static_whitelist_patterns += %__auto_generated_rro_vendor.apk

  # Auto-included targets are not considered

  static_whitelist_patterns += $(call module-installed-files,$(call auto-included-modules))

  static_whitelist_patterns += $(call product-installed-files,)

  # $(PRODUCT_OUT)/apex is where shared libraries in APEXes get installed.

  # The path can be considered as a fake path, as the shared libraries

  # are installed there just to have symbols files for them under