c6879f3ddd
Before this change, the build system had special logic to find mainline BCP jars and copy them to a special location for app dexpreopt. This logic doesn't work on `next`. In fact, we don't need this logic anymore. Since we are now generating the mainline boot image extension, we can reference the inputs of the mainline boot image extension, which are exactly the mainline BCP jars needed for app dexpreopt. Bug: 309302263 Test: atest art_standalone_dexpreopt_tests (on next) Test: m --no-skip-soong-tests nothing Change-Id: I055018ffbc5d7e5678f305e65a7f1c7e73bf3b99 |
||
---|---|---|
.. | ||
Android.bp | ||
androidmk.go | ||
apex.go | ||
apex_sdk_member.go | ||
apex_singleton.go | ||
apex_test.go | ||
bootclasspath_fragment_test.go | ||
bp2build.go | ||
bp2build_test.go | ||
builder.go | ||
classpath_element_test.go | ||
deapexer.go | ||
dexpreopt_bootjars_test.go | ||
key.go | ||
platform_bootclasspath_test.go | ||
prebuilt.go | ||
systemserver_classpath_fragment_test.go | ||
TEST_MAPPING | ||
testing.go | ||
vndk.go | ||
vndk_test.go |