It2Me native messaging: GYP and source refactoring

1. Add "me2me" to the names of all the me2me specific GYP targets and source files. This makes it easier for my next CL that will add the It2Me native messaging host component.
2. Create a remoting_native_messaging_base GYP target that contains the common native messaging plumbing code shared between remoting_core, remoting_me2me_native_messaging_host and the to-be-created remoting_it2me_native_messaging_host.
3. Clean up some dependencies in remoting.gyp: e.g. the native messaging manifest should be depended on by the archive targets, not the native messaging host binary targets.
4. Rename It2MeImpl to It2MeHost.

BUG=309844

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

Review URL: https://codereview.chromium.org/49113003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@232543 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 18 insertions, 0 deletions

diff --git a/remoting/host/setup/me2me_native_messaging_host_main.cc b/remoting/host/setup/me2me_native_messaging_host_main.cc
new file mode 100644
index 0000000..e69abfc
--- /dev/null
+++ b/remoting/host/setup/me2me_native_messaging_host_main.cc
@@ -0,0 +1,18 @@
+// Copyright 2013 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 "base/at_exit.h"
+#include "base/command_line.h"
+#include "remoting/host/logging.h"
+#include "remoting/host/setup/me2me_native_messaging_host.h"
+
+int main(int argc, char** argv) {
+  // This object instance is required by Chrome code (such as MessageLoop).
+  base::AtExitManager exit_manager;
+
+  CommandLine::Init(argc, argv);
+  remoting::InitHostLogging();
+
+  return remoting::NativeMessagingHostMain();
+}