Initial skeletal implementation of the PrincipalService. Also, use the Login()/GetUserBlessing()

services/vanadium/security/BUILD.gn

Index: services/vanadium/security/BUILD.gn
diff --git a/services/vanadium/security/BUILD.gn b/services/vanadium/security/BUILD.gn
new file mode 100644
index 0000000000000000000000000000000000000000..5ab34476949471292868f9432b2db35e21ab7fc6
--- /dev/null
+++ b/services/vanadium/security/BUILD.gn
@@ -0,0 +1,31 @@
+# Copyright 2015 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.
+
+import("//mojo/go/rules.gni")
+
+if (defined(go_build_tool) && go_build_tool != "") {
+  go_mojo_application("principal_service") {
+    sources = [
+      "principal_service.go",
+    ]
+    deps = [
+      "//mojo/services/vanadium/security/public/interfaces",
+    ]
+  }
+} else {
+  import("//mojo/public/mojo_application.gni")
+
+  mojo_native_application("principal_service") {

[jamesr, 2015/08/17 21:38:22]

instead of having two ways to build the same .mojo i think it'd be better to
have both targets listed out with different names, possibly with the go one
guarded, so that a developer can build both. with this setup it's impossible in
one checkout to build the go and C++ versions for a particular build (without
mucking around with the go_build_tool variable between builds).

[gautham, 2015/08/18 01:54:22]

I removed the C++ version and deleted principal_service.cc. The bank example and
principal-service only work with go/android. Made the necessary BUILD.gn
modifications. 

+    sources = [
+      "principal_service.cc",
+    ]
+    deps = [
+      "//base",
+      "//mojo/common",
+      "//mojo/public/cpp/application:standalone",
+      "//mojo/public/cpp/bindings",
+      "//mojo/services/vanadium/security/public/interfaces",
+    ]
+  }
+}