summaryrefslogtreecommitdiffstats
path: root/runtime/runtime.cc
diff options
context:
space:
mode:
authorAndreas Gampe <agampe@google.com>2014-03-25 18:09:32 -0700
committerAndreas Gampe <agampe@google.com>2014-04-01 13:58:32 -0700
commitafbaa1aab02cfe519d00336870b1bcd24b61378d (patch)
treeec33583d52a42ee49082f4bce404e8c434cfd8f5 /runtime/runtime.cc
parent8ce67ac16abcd25b376be622cbd20a34aec4a59d (diff)
downloadart-afbaa1aab02cfe519d00336870b1bcd24b61378d.zip
art-afbaa1aab02cfe519d00336870b1bcd24b61378d.tar.gz
art-afbaa1aab02cfe519d00336870b1bcd24b61378d.tar.bz2
Build changes to build multilib tests
Test files will be emitted into directories for both first and second target architectures. Going with the naming scheme for binaries, single-architecture and 32b cases have the standard name, and 64b goes into a directory with "64" suffix. In multi-architecture setups, the default concrete test targets are extended with a "32" and "64" suffix, e.g., test-art-target-oat-JniTest64. The suffix-less form is linked to the primary architecture target (usually 64). That means running combined targets, e.g., test-art-target-oat, will only test the primary architecture right now. Fixed target run tests calling the right dalvikvm. Fixed library search path for tests derived from CommonRuntimeTest. Missing in this work-in-progress is correct handling of dex2oat for the secondary architecture. To make it work on 64b, comment out line 101 in build/Android.executable.mk Change-Id: I3d260994e6efe8b73b56c71994053cc9392943a9
Diffstat (limited to 'runtime/runtime.cc')
0 files changed, 0 insertions, 0 deletions