Age | Commit message (Collapse) | Author |
|
The marked library(ies) were available to the APEXes via the
hand-written whitelist in build/soong/apex/apex.go. Trying to remove the
whitelist by adding apex_available property to the Android.bp of the
libraries.
Bug: 150999716
Test: m
Test: ./art/tools/run-libjdwp-tests.sh --mode=host
Outcomes: 417. Passed: 415, Failed: 0, Skipped: 0, Warnings: 2. Took 14m18s.
Killing stalled dalvikvm processes...
Done.
Change-Id: I223a1c99ea9a46597041a7ec3f8e948abac9c964
|
|
Reason for revert: relanding with fix
Reverted Changes:
Ic4119368c:Revert submission 1191937-art_apex_available
Ia084976bb:Revert submission 1191937-art_apex_available
Iada86226d:Revert submission 1191937-art_apex_available
Ic76735eac:Revert submission 1191937-art_apex_available
I1eb30e355:Revert submission 1191937-art_apex_available
Icaf95d260:Revert submission 1191937-art_apex_available
Ie8bace4be:Revert submission 1191937-art_apex_available
I8961702cf:Revert submission 1191937-art_apex_available
I39316f9ef:Revert submission 1191937-art_apex_available
I522a7e83b:Revert submission 1191937-art_apex_available
I8b9424976:Revert submission 1191937-art_apex_available
I48b998629:Revert submission 1191937-art_apex_available
Exempt-From-Owner-Approval: relanding the same change
Change-Id: I6ebb05063af36b4155e2c65f9326c20ab1a82e20
|
|
Original Commit Message:
"""
Rename modules that are APEX-only
The renamed modules are only available for APEXes, but not for the
platform. Use the <module_name>.<apex_name> syntax to correctly install
the APEX variant of the modules.
"""
Reason for revert: Build Cop - Breaks about 15 AOSP targets, with high confidence due to these changes being the only non-robot changes in those builds.
Reverted Changes:
I190ce2d10:Use apex_available property
I990e0a67e:Use apex_available property
I0d1295683:Revert "Avoid duplicated classes for boot dex jars...
I5fb725403:Find the jar libraries in APEX from the correct pa...
I322b1efcc:Rename modules that are APEX-only
Ifa2bd0f8f:Use apex_available property
Iac6533177:Use apex_available property
Ie999602c6:Use apex_available property
I2a3d73397:Use apex_available property
Ic91bcbb9a:Use apex_available property
Ia6c324eed:Use apex_available property
I964d0125c:Use apex_available property
Change-Id: Ia084976bb5a0a7ee8bd0b2126ee7776c5d5c8391
|
|
Use apex_available property to prevent modules that are only for the ART
apex from being used outside of the APEX.
Bug: 128708192
Bug: 133140750
Test: m
Change-Id: I2a3d73397c1dc03f8e2bf214117abc7d00537ef8
|
|
This class relies on Java 8-only constructs such as the jdk.Exported
annotation and won't compile when targetting Java language level 9.
It is only used for testing, specifically in
CtsJdwpTunnelHostTestCases. With this change, those tests pass on a
build done with EXPERIMENTAL_USE_OPENJDK9=true (which changes the
default to target Java language level 9). (This change is a no-op
without that setting.)
Bug: 131678633
Test: `cts-tradefed run cts-dev -m CtsJdwpTunnelHostTestCases` with `EXPERIMENTAL_USE_OPENJDK9=true`
Change-Id: I465980785b815dea7563ca0aeed1924d7d7dfa39
|
|
This adds a jdi-support 'jar' which contains the debugee side of the
debugger. This allows for tests and tools to interact with debuggers
using the standard JDI classes without having to rely on the
configuration of the host classpath.
Test: CtsJdwpTunnelTestCases
Test: m jdi-support
Bug: 124507633
Change-Id: I2e38ca05c38d48e7440e3545061ac8e710cd4b57
|
|
Soong now treats the binary wrapper as a host binary variant,
so it is no longer necessary or correct to set
compile_multlib: first.
Bug: 68397812
Test: m checkbuild
Change-Id: Ida6dc4df7752bad494b5cf773f5590e2f7ca5051
|
|
There isn't any real reason to build darwin at all so we will just
disable it entirely.
This reverts commit eab990b981d3a9eea45f4afad8920b3d87c4b03d.
Reason for revert: Disabling darwin build seems a better long-term
solution.
Test: linux builds.
Change-Id: I2a113ca379c9aa4ca858fd6599275bd892d87d2e
|
|
Mac needs slightly different includes from all other builds. Import
the macosx/javavm/export/ header files and use them when building for
darwin targets.
Test: Build on linux
Change-Id: I9a530ee01c77127d729b5de5563e7900187ace6f
|
|
We were incorrectly assuming that jdwpgen would be in the PATH during
the genrule when we should be calling it using a full path.
Test: mma -j40
Change-Id: Iae670939dc45f11cebc66ad810c41936c98002f0
|
|
Adds an Android.bp file capable of building libjdwp.so, libnpt.so, and
libdt_socket.so. Add some ancillary files needed for the build
process.
Test: mma -j40
Test: ./art/tools/run-jdwp-tests.sh \
--mode=host \
--debug \
--variant=x64 \
-Xplugin:$ANDROID_HOST_OUT/lib64/libopenjdkjvmtid.so \
--jdwp-path $ANDROID_HOST_OUT/lib64/libjdwp.so \
--agent-wrapper $ANDROID_HOST_OUT/lib64/libwrapagentproperties.so=$PWD/art/tools/libjdwp-compat.props \
--expectations $PWD/art/tools/libjdwp_art_failures.txt
Test: adb root && adb remount && adb sync && \
adb push $PWD/art/tools/libjdwp-compat.props \
/data/local/tmp/libjdwp-compat.props && \
./art/tools/run-jdwp-tests.sh \
--mode=device \
--debug \
--variant=x64 \
-Xplugin:libopenjdkjvmtid.so \
--jdwp-path libjdwp.so \
--agent-wrapper libwrapagentproperties.so=/data/local/tmp/libjdwp-compat.props \
--expectations $PWD/art/tools/libjdwp_art_failures.txt
Bug: 62821960
Bug: 68397812
Change-Id: I980ba706f99789d9a5755f539231268d21bb356b
|