media: Mark Widevine CDM and manifest as data_deps of the adapter

third_party/widevine/cdm/BUILD.gn

Index: third_party/widevine/cdm/BUILD.gn
diff --git a/third_party/widevine/cdm/BUILD.gn b/third_party/widevine/cdm/BUILD.gn
index f77c369bf54a88f9bb9ad18b0b0f3211cee9872f..e5fdb29e858fec1137a2182c18db6304279b4c24 100644
--- a/third_party/widevine/cdm/BUILD.gn
+++ b/third_party/widevine/cdm/BUILD.gn
@@ -143,10 +143,13 @@ if ((is_chrome_branded || enable_widevine) && enable_pepper_cdms) {
     output_dir = "$root_out_dir/$widevine_cdm_path"
     deps = [
       ":version_h",
-      ":widevine_cdm_manifest",
       ":widevinecdm",
       ":widevinecdmadapter_resources",
     ]
+    data_deps = [
+      ":widevine_cdm_manifest",
+      ":widevinecdm",

[ddorwin, 2016/06/01 20:16:43]

deps doesn't imply data_deps?

[xhwang, 2016/06/01 20:24:12]

Apparently not based on "gn help runtime_deps" unless it's a shared library:

  To a first approximation, the runtime dependencies of a target are
  the set of "data" files, data directories, and the shared libraries
  from all transitive dependencies.

[Dirk Pranke, 2016/06/01 21:33:16]

Correct, `deps` does not imply `data_deps`. You might depend on `protoc` in
order to generate the proto buffer stubs, but that doesn't mean you need the
protocol compiler itself to be present at runtime.

+    ]
 
     if (is_linux) {
       ldflags =