GN: Build rules and fixes for (almost) all mojo unittest targets

mojo/public/cpp/environment/tests/BUILD.gn

Index: mojo/public/cpp/environment/tests/BUILD.gn
diff --git a/mojo/public/cpp/environment/tests/BUILD.gn b/mojo/public/cpp/environment/tests/BUILD.gn
new file mode 100644
index 0000000000000000000000000000000000000000..4422076c3c39ae5a5d22efb66d99a75776c0d30e
--- /dev/null
+++ b/mojo/public/cpp/environment/tests/BUILD.gn
@@ -0,0 +1,22 @@
+# 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.
+
+# GYP version: mojo/mojo_public_tests.gypi:mojo_public_environment_unittests
+test("mojo_public_environment_unittests") {
+  deps = [
+    "//mojo/common/test:run_all_unittests",
+    "//mojo/public/cpp/environment:standalone",
+    "//mojo/public/cpp/test_support:test_utils",
+    "//mojo/public/cpp/utility",
+    "//testing/gtest",
+  ]
+
+  include_dirs = [ "../../../../.." ]

[viettrungluu, 2014/08/20 16:44:45]

Is there a way to avoid this sort of thing (e.g., by having // in the default
list of include dirs)?

(Alternatively, is there a way to specify include dirs using an absolute path
instead (i.e., "//") instead?)

+
+  sources = [
+    "async_waiter_unittest.cc",
+    "logger_unittest.cc",
+    "logging_unittest.cc",
+  ]
+}