[Android] Build gtest APKs like other APKs

[Android] Build gtest APKs like other APKs

After much work, we can build gtest APKs without first transforming .java files, resource files, or the AndroidManifest.xml. We can directly use java_apk.gypi and build like all other APKs.

Do that.

Also, native_test_apk.xml was the last user of common.xml and sdk-targets.xml, and so those can now be removed.

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=193576

[Yaron, 2013-04-10 01:35:57]

https://codereview.chromium.org/13828003/diff/1/build/apk_test.gypi
File build/apk_test.gypi (right):

https://codereview.chromium.org/13828003/diff/1/build/apk_test.gypi#newcode33
build/apk_test.gypi:33: 'java_in_dir': '<(DEPTH)/testing/android/java',
Looks like this would recompile once for each test target. Instead, how about
making testing/android/java a jar and depend on it?

https://codereview.chromium.org/13828003/diff/1/testing/android/native_test_a...
File testing/android/native_test_apk.xml (left):

https://codereview.chromium.org/13828003/diff/1/testing/android/native_test_a...
testing/android/native_test_apk.xml:34: <fileset file="${android.gdbserver}"/>
This made me realize that I think we've lost the ability to use gdb for apks. We
need to bring that back in.

[cjhopman, 2013-04-10 23:24:03]

https://codereview.chromium.org/13828003/diff/1/build/apk_test.gypi
File build/apk_test.gypi (right):

https://codereview.chromium.org/13828003/diff/1/build/apk_test.gypi#newcode33
build/apk_test.gypi:33: 'java_in_dir': '<(DEPTH)/testing/android/java',
On 2013/04/10 01:35:57, Yaron wrote:
> Looks like this would recompile once for each test target. Instead, how about
> making testing/android/java a jar and depend on it?

This is required because the .java file in this directory refers to the
generated NativeLibraries.java and that is only generated when building the APK.

https://codereview.chromium.org/13828003/diff/1/testing/android/native_test_a...
File testing/android/native_test_apk.xml (left):

https://codereview.chromium.org/13828003/diff/1/testing/android/native_test_a...
testing/android/native_test_apk.xml:34: <fileset file="${android.gdbserver}"/>
On 2013/04/10 01:35:57, Yaron wrote:
> This made me realize that I think we've lost the ability to use gdb for apks.
We
> need to bring that back in.

I'm uncertain what has happened with gdbserver. Building a unittest_apk without
this change does not include gdbserver in the APK (even though it is copied into
the libs directory that is packaged in the APK).

[Yaron, 2013-04-10 23:49:47]

lgtm

I'm assuming you'll take care of cleaning up native_lib_target in a follow up..

[Yaron, 2013-04-10 23:50:02]

By which I mean input_shlib_path :)

[commit-bot: I haz the power, 2013-04-11 02:11:15]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/cjhopman@chromium.org/13828003/5001

[commit-bot: I haz the power, 2013-04-11 04:47:11]

Change committed as 193576