Adding third_party/openh264 build files for encoding

content/test/BUILD.gn

Index: content/test/BUILD.gn
diff --git a/content/test/BUILD.gn b/content/test/BUILD.gn
index c6d764c19b33c98b4eb3611458c10b809986c3be..3b69a75d4ad3795049f686457d6a9534165e589b 100644
--- a/content/test/BUILD.gn
+++ b/content/test/BUILD.gn
@@ -10,6 +10,7 @@ import("//build_overrides/v8.gni")
 import("//media/media_options.gni")
 import("//mojo/public/tools/bindings/mojom.gni")
 import("//testing/test.gni")
+import("//third_party/openh264/openh264_args.gni")
 
 content_tests_gypi_values =
     exec_script("//build/gypi_to_gn.py",
@@ -773,6 +774,11 @@ test("content_unittests") {
   if (is_mac && use_openssl) {
     deps += [ "//third_party/boringssl" ]
   }
+
+  if (use_openh264) {
+    sources += [ "../browser/media/openh264_unittests.cc" ]
+    deps += [ "//third_party/openh264/testing:openh264_testing" ]

[Dirk Pranke, 2015/11/19 02:46:56]

see comment in openh264_unittests; I don't understand why this is part of
content_unittests and not a separate binary?

[hbos_chromium, 2015/11/19 13:00:43]

There's overhead in creating new test binaries, I've been told that you probably
don't want to do that for a single test class and might get pushback. Also, we
only want the unittests to be included if you build with use_openh264, meaning
producing and for the trybots running the binary would be conditional or it
would have to produce a binary that doesn't have any tests if !use_openh264.

I created and landed a CL that created a new binary specifically for openh264
unittests but we reverted it in favor of content_unittests. I'll take a look at
media_unittests as an alternative.

+  }
 }
 
 test("content_perftests") {