Add RemoteDebuggingController.java and its (native) dependencies.

content/browser/android/remote_debugging_controller.cc

+// Copyright (c) 2012 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.
+
+#include "content/browser/android/remote_debugging_controller.h"
+
+#include <jni.h>
+
+#include "content/public/browser/android/devtools_server.h"
+#include "jni/remote_debugging_controller_jni.h"
+
+static void StartRemoteDebugging(JNIEnv*, jclass) {

[jochen (gone - plz use gerrit), 2012/06/18 11:32:40]

what about moving those three functions into an anonymous namespace instead of
making them static?

[mnaganov (inactive), 2012/06/18 12:26:52]

They are called from Java code via JNI. This is the convention used by the
bridge code generator.

[Philippe, 2012/06/18 13:28:59]

Indeed, the JNI generator emits the following prototypes in
jni/remote_debugging_controller_jni.h:

static void StartRemoteDebugging(JNIEnv*, jclass);
static void StopRemoteDebugging(JNIEnv* , jclass);
...

It does not support namespace specification for free functions yet. We have a
bug tracking that internally.

+  content::DevToolsServer::GetInstance()->Start();
+}
+
+static void StopRemoteDebugging(JNIEnv* , jclass) {
+  content::DevToolsServer::GetInstance()->Stop();
+}
+
+static jboolean IsRemoteDebuggingEnabled(JNIEnv*, jclass) {
+  return content::DevToolsServer::GetInstance()->is_started();
+}
+
+namespace content {
+
+bool RegisterRemoteDebuggingController(JNIEnv* env) {
+  return RegisterNativesImpl(env);
+}
+
+}  // namespace content