diff options
| author | 2019-03-06 15:48:08 +0000 | |
|---|---|---|
| committer | 2019-06-24 13:13:42 +0000 | |
| commit | 72f6774bf65222b7c93c3e4d706938635cacf050 (patch) | |
| tree | e121e3ce1f5b0e5215b7054fb8689e8e4ceded45 /compiler/optimizing/optimizing_compiler.cc | |
| parent | 2c029f35eebe7d8b0d00979342d64b2f2dad5a94 (diff) | |
Use flattened Runtime APEX contents in ART chroot-based device testing.
Copy the contents of the flattened Debug Runtime Module
directory (`/system/apex/com.android.runtime.debug`) to
`/apex/com.android.runtime` within the chroot directory on the device.
Avoid generating artifacts that are not expected in the `system`
directory (`TARGET_OUT`) of a "normal" build.
Adjust the chroot environment to have it use the system linker
configuration of the built target ("guest system") and the linker
configuration of the Runtime APEX, even if the linker configuration
flavor of the "guest system" (e.g. legacy configuration) does not
match the one of the "host system" (e.g. full-VNDK configuration).
This is done by renaming the configuration file provided by the "guest
system" (created according to the build target configuration) within
the chroot environment, using the name of the configuration file
expected by the linker (governed by system properties of the "host
system").
Test: ART chroot-based on-device testing using the master-art branch
Test: ART chroot-based on-device testing using the master branch (with
`TARGET_FLATTEN_APEX` set to `true` before building).
Bug: 124425036
Bug: 121117762
Change-Id: Ied3f6ee8b2d68c3473fab864d1bbed9e88df59d3
Diffstat (limited to 'compiler/optimizing/optimizing_compiler.cc')
0 files changed, 0 insertions, 0 deletions