Setup Blimp internal string resources.

blimp/client/public/resources/BUILD.gn

Index: blimp/client/public/resources/BUILD.gn
diff --git a/blimp/client/public/resources/BUILD.gn b/blimp/client/public/resources/BUILD.gn
new file mode 100644
index 0000000000000000000000000000000000000000..983356e1da466bd4a35d2f9cfe6e70da1bac071d
--- /dev/null
+++ b/blimp/client/public/resources/BUILD.gn
@@ -0,0 +1,13 @@
+# Copyright 2016 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.
+
+# Resources for the embedder, we build different resource sets based on |enable_blimp_client| build
+# flag in //blimp/client/core/resources.
+group("resources") {
+  visibility = [ "//chrome/*" ]

[David Trainor- moved to gerrit, 2016/10/26 00:43:18]

Should we just remove the visibility if it's meant to be hit by all embedders?

[xingliu, 2016/10/26 21:14:42]

Actually this target is only for chrome, because in core/resources:strings, we
do special things for enable_blimp_client flag, and the flag is only for chrome.

Added another target in here for blimp/client/app.

[David Trainor- moved to gerrit, 2016/10/28 04:20:08]

Why is it only for chrome?  We have to set enable_blimp_client for any embedder
right?

[xingliu, 2016/10/28 22:50:31]

Yes, but for blimp_shell it's directly depend on core/*, so if we let it go
through the target that checks |enable_blimp_client|, it might hit the scenario
that it didn't load the string but try to access the string.

+
+  public_deps = [
+    "//blimp/client/core/resources:strings",
+  ]
+}