Move SharedBitmapManager implementation out of content/

components/display_compositor/child/BUILD.gn

Index: components/display_compositor/child/BUILD.gn
diff --git a/components/display_compositor/child/BUILD.gn b/components/display_compositor/child/BUILD.gn
new file mode 100644
index 0000000000000000000000000000000000000000..bb52d125a058a26d422bc790769c72dd7a828d38
--- /dev/null
+++ b/components/display_compositor/child/BUILD.gn
@@ -0,0 +1,25 @@
+# Copyright 2017 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("//testing/test.gni")
+
+component("child") {
+  output_name = "display_compositor_child"
+
+  defines = [ "DISPLAY_COMPOSITOR_IMPLEMENTATION" ]

[danakj, 2017/02/28 20:34:56]

separate components should have separate IMPLEMENTATION and export macros

[xlai (Olivia), 2017/03/01 20:02:45]

This is not a separate implementation. It still belongs to display_compositor,
just like //components/discardable_memory/ having separate folders for renderer
and browser respectively.

[danakj, 2017/03/03 19:21:55]

That makes me question this a bit more then. //components/display_compositor is
the cc embedder for the display compositor. But the child is not part of the
display compositor so it should not be in that component.

+
+  sources = [
+    "child_shared_bitmap_manager.cc",
+    "child_shared_bitmap_manager.h",
+  ]
+
+  deps = [
+    "//base",
+    "//cc",
+    "//components/display_compositor",
+    "//components/display_compositor/interfaces",
+    "//mojo/public/cpp/bindings",
+    "//ui/gfx",
+  ]
+}