Add a way for JNI registrars to specify methods to be registered for tests.

Add a way for JNI registrars to specify methods to be registered for tests.

The Cl adds a macro which allows jni registrars to add methods to a
global list. All the methods in the list are registered before APK tests
are run.

This is loosely based on how  MULTIPROCESS_TEST_MAIN macro works.

BUG=125059
TEST=

[John Grabowski, 2012-06-20 22:26:23]

Let's talk.

[nilesh, 2012-06-25 16:48:06]

On 2012/06/22 15:23:39, nileshagrawal1 wrote:

Another options is to define a pre-processor macro in each of these unittests
targets to conditionally call the corresponding registrar.
Please see: http://codereview.chromium.org/10658017/

[bulach, 2012-06-25 16:51:01]

+joth

Joth suggested a few times to use some dynamic registration mechanism that's
used by Skia (I'm not too familiar with it and didn't find any reference..
joth?).

if that works, maybe we could use the same mechanism for both tests and regular
code, and avoid that single global array of register functions altogether? would
that work?

[joth, 2012-06-25 17:07:38]

There's nothing that magic in what skia does, it's just a pattern: have a
static instance of an object per .cc that in its constructor adds the
functions needed for registration from that .cc into a global linked list
of stuff to initialize.

Downside is it adds another static initializer per file, which is very bad
for startup time. Hence why we avoided doing it.


On 25 June 2012 09:51, <bulach@chromium.org> wrote:

> +joth
>
> Joth suggested a few times to use some dynamic registration mechanism
> that's
> used by Skia (I'm not too familiar with it and didn't find any reference..
> joth?).
>
> if that works, maybe we could use the same mechanism for both tests and
> regular
> code, and avoid that single global array of register functions altogether?
> would
> that work?
>
>
http://codereview.chromium.**org/10591005/<http://codereview.chromium.org/105...
>