Go to file
Jaekyun Seok 1b2242895e Use product-based inclusive rule for enforcing RRO
Board-based rule can cause unexpected regression because build-time overlays
are different among products. So each product should be tested with its own
product-based rule considering its build-time overlays before applying
enforcing RRO.

Additionally RRO conversion is mandatory only for overlays of which target is
included in AOSP system image and is critical for CTS/VTS tests with AOSP
system image. So inclusive rule is more suitable instead of exclusive rule
to avoid unexpected regression due to unnecessary RRO conversion.

Note that we still support conversion for all the overlays by specifying
PRODUCT_ENFORCE_RRO_TARGETS as "*".

Test: building succeeded and tested with auto-generated RROs.
Bug: 36231603
Change-Id: I8e1d701d4f78b818c89ef3e7638110105370c5bc
(cherry picked from commit 2a209997e8)
2017-04-04 11:31:24 +09:00
core Use product-based inclusive rule for enforcing RRO 2017-04-04 11:31:24 +09:00
target Switch to a shell_and_utilities phony module. 2017-04-03 17:13:58 +00:00
tests Add TARGET_PLATFORM_VERSION to lunch 2017-03-23 09:44:08 -07:00
tools Don't include the dev-key on IOT products. 2017-04-03 15:04:35 -07:00
.gitignore Add build subprojects to .gitignore 2015-07-23 13:18:47 -07:00
Android.mk Add new Android.mk to handle repo move 2016-06-16 15:30:19 -07:00
CleanSpec.mk Refactor sanitized library on-disk layout - Make. 2017-03-30 20:14:27 -07:00
buildspec.mk.default Add TARGET_PLATFORM_VERSION to lunch 2017-03-23 09:44:08 -07:00
envsetup.sh Merge "Small fixes for environment variables." 2017-03-24 16:15:07 +00:00