Hook components/gcm_driver up to JNI Generator

components/gcm_driver/android/component_jni_registrar.h

Index: components/gcm_driver/android/component_jni_registrar.h
diff --git a/components/gcm_driver/android/component_jni_registrar.h b/components/gcm_driver/android/component_jni_registrar.h
new file mode 100644
index 0000000000000000000000000000000000000000..b2a67c4b8a3f4c9a79c7b16bb4f06f9469bcbf98
--- /dev/null
+++ b/components/gcm_driver/android/component_jni_registrar.h
@@ -0,0 +1,21 @@
+// Copyright 2014 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef COMPONENTS_GCM_DRIVER_ANDROID_COMPONENT_JNI_REGISTRAR_H_
+#define COMPONENTS_GCM_DRIVER_ANDROID_COMPONENT_JNI_REGISTRAR_H_
+
+#include <jni.h>

[jianli, 2014/05/15 18:13:39]

nit: probably you don't need to include this header file. Instead, you can
forward declare JNIEnv.

[johnme, 2014/05/15 19:29:42]

Unfortunately, JNIEnv is defined as:

struct _JNIEnv;
#if defined(__cplusplus)
typedef _JNIEnv JNIEnv;
#else
typedef const struct JNINativeInterface* JNIEnv;
#endif

and you can't forward declare a typedef without exposing implementation
details[1] :-|

[1]:
http://stackoverflow.com/questions/804894/forward-declaration-of-a-typedef-in-c

+
+namespace gcm {

[jianli, 2014/05/15 18:13:39]

Wrong namespace. I am also going to update namespace in other gcm component
files to use gcm_driver namespace.

[jianli, 2014/05/15 19:04:43]

We decide not to update namespace to gcm_driver at this moment. We're going to
do it after all files have been componentized. So you can keep using gcm
namespace.

+
+namespace android {
+
+// Register all JNI bindings necessary for the gcm_driver component.
+bool RegisterGCMDriverJni(JNIEnv* env);
+
+}  // namespace android
+
+}  // namespace gcm
+
+#endif  // COMPONENTS_GCM_DRIVER_ANDROID_COMPONENT_JNI_REGISTRAR_H_