Visualization tool for WebrtcEventLogs

webrtc/tools/BUILD.gn

Index: webrtc/tools/BUILD.gn
diff --git a/webrtc/tools/BUILD.gn b/webrtc/tools/BUILD.gn
index 2d095636dfa424de569660555b78294b08e2eccd..e568b45f9aa21a66ec331dd0623bef033d6b470e 100644
--- a/webrtc/tools/BUILD.gn
+++ b/webrtc/tools/BUILD.gn
@@ -171,6 +171,38 @@ source_set("agc_test_utils") {
 
 # Exclude tools depending on gflags since that's not available in Chromium.
 if (rtc_include_tests) {
+  if (rtc_enable_protobuf) {
+    executable("event_log_visualizer") {
+      sources = [
+        "event_log_visualizer/analyzer.cc",
+        "event_log_visualizer/analyzer.h",
+        "event_log_visualizer/generate_timeseries.cc",
+        "event_log_visualizer/plot_base.h",
+        "event_log_visualizer/plot_python.cc",
+        "event_log_visualizer/plot_python.h",
+      ]
+
+      configs += [ "..:common_config" ]
+      public_configs = [ "..:common_inherited_config" ]
+
+      if (is_clang && !is_nacl) {
+        # Suppress warnings from the Chromium Clang plugin.
+        # See http://code.google.com/p/webrtc/issues/detail?id=163 for details.
+        configs -= [ "//build/config/clang:find_bad_constructs" ]
+      }
+
+      defines = [ "ENABLE_RTC_EVENT_LOG" ]
+      deps = [
+        "../:rtc_event_log_parser",
+        "../:rtc_event_log_proto",
+        "../:webrtc_common",
+        "../modules/rtp_rtcp:rtp_rtcp",

[phoglund, 2016/07/11 14:28:53]

The dependency lists differ slightly between gyp and gn.  Is there no need to
depend on the proto in the gyp case?

[terelius, 2016/07/12 09:33:36]

As discussed offline, the gyp file uses export_dependent_settings to avoid
having an explicit dependency on the proto. I've added the proto to the
public_deps of the parser, to make the gn case analogous.

+        "../system_wrappers:system_wrappers_default",
+        "//third_party/gflags",
+      ]
+    }
+  }
+
   executable("agc_harness") {
     testonly = true
     sources = [