platform_build

Commit Graph

Author	SHA1	Message	Date
Anton Hansson	cb8276fa93	Put DEVICE/PRODUCT overlays in different partitions This change changes auto-generated RROs from DEVICE_PACKAGE_OVERLAYS to be generated in the vendor partition, as opposed to /product where they were generated in the past. Note that PRODUCT_PACKAGE_OVERLAYS continue generating RRO packages to /product, which means that a single app can be overlayed from different partitions. These RROs have been given module and package names based on their location. Bug: 127758779 Test: verify noop on presubmit targets Change-Id: I5cee70e28e3969e67b2d83eaf25d9c6e3a11102d	2019-03-22 13:25:20 +00:00
Anton Hansson	08231e1786	Refactor generate_enforce_rro A few tweaks to make it easier to extend to generating RROs in multiple partitions: - deduce the module name inside generate_enforce_rro - dedup rule definition - tweak framework-res check to use source module name instead Bug: 127758779 Test: verify noop on presubmit targets Change-Id: I2f0d6270b21f5427c372c04a5c6e7fb712e72a9a	2019-03-18 14:21:09 +00:00
Jaekyun Seok	3070610b72	Enforce RROs for all the build-time ROs This CL is to generate every static RRO package for its target package automatically at build-time. BOARD_ENFORCE_RRO build variable is added to specify whether enforcing RRO is required or not. BOARD_ENFORCE_RRO_EXEMPT_SOURCES build variable is added to specify the module list of which item should be exempt from enforcing RRO. Test: tested on bullhead and sailfish Bug: 34097942 Change-Id: I455b2ce34e66c57a540c299b5e378b7c4e78d5b8	2017-03-14 23:55:50 +09:00

Author

SHA1

Message

Date

Anton Hansson

cb8276fa93

Put DEVICE/PRODUCT overlays in different partitions

This change changes auto-generated RROs from DEVICE_PACKAGE_OVERLAYS
to be generated in the vendor partition, as opposed to /product where
they were generated in the past.

Note that PRODUCT_PACKAGE_OVERLAYS continue generating RRO packages
to /product, which means that a single app can be overlayed from
different partitions. These RROs have been given module and package
names based on their location.

Bug: 127758779
Test: verify noop on presubmit targets
Change-Id: I5cee70e28e3969e67b2d83eaf25d9c6e3a11102d

2019-03-22 13:25:20 +00:00

Anton Hansson

08231e1786

Refactor generate_enforce_rro

A few tweaks to make it easier to extend to generating RROs in
multiple partitions:
- deduce the module name inside generate_enforce_rro
- dedup rule definition
- tweak framework-res check to use source module name instead

Bug: 127758779
Test: verify noop on presubmit targets
Change-Id: I2f0d6270b21f5427c372c04a5c6e7fb712e72a9a

2019-03-18 14:21:09 +00:00

Jaekyun Seok

3070610b72

Enforce RROs for all the build-time ROs

This CL is to generate every static RRO package for its target package
automatically at build-time.

BOARD_ENFORCE_RRO build variable is added to specify whether enforcing
RRO is required or not.

BOARD_ENFORCE_RRO_EXEMPT_SOURCES build variable is added to specify
the module list of which item should be exempt from enforcing RRO.

Test: tested on bullhead and sailfish
Bug: 34097942
Change-Id: I455b2ce34e66c57a540c299b5e378b7c4e78d5b8

2017-03-14 23:55:50 +09:00

3 Commits