Fix backwards WebRTC-in-Chromium override and expose Chromium logging setup

third_party/webrtc_overrides/webrtc/base/logging.h

Index: third_party/webrtc_overrides/webrtc/base/logging.h
diff --git a/third_party/webrtc_overrides/webrtc/base/logging.h b/third_party/webrtc_overrides/webrtc/base/logging.h
index e9ca47e03269f6384586394fcc71f68fd76636ce..b3b3fc8ab57840f0ae90e3e6d9b353b27791c64c 100644
--- a/third_party/webrtc_overrides/webrtc/base/logging.h
+++ b/third_party/webrtc_overrides/webrtc/base/logging.h
@@ -26,6 +26,13 @@
 
 #include "third_party/webrtc_overrides/webrtc/base/diagnostic_logging.h"
 
+// Chromium allows a minimum programmatically-set log level of -1

[Henrik Grunell, 2016/05/18 08:43:26]

Explain that this function is only used when WebRTC standalone is built but it
used the Chromium logging.

Add TODO for removing it when the fuzzers are built/run on WebRTC bots, i.e. not
inside Chromium. (Sorry for any incorrect/confused terminology...:)) Link to
bug.

[katrielc, 2016/05/18 09:06:42]

I checked with phoglund@ and they don't plan to move the ClusterFuzz uploads to
the WebRTC bot, hence probably it makes sense not to add a TODO/bug link.

[Henrik Grunell, 2016/05/18 09:29:32]

Acknowledged.

+// unless there is a command line set up with --v=x. This exposes
+// those initialisation calls to WebRTC code.
+namespace rtc {
+  void InitChromiumLoggingAndCommandLine();
+}
+
 //////////////////////////////////////////////////////////////////////
 // WebRTC macros which in DiagnosticLogMessage are mapped over to
 // their VLOG equivalent in base/logging.h.