TEST CL: To see if rtc_use_h264=1 is still passing all bots.

webrtc/build/common.gypi

 # Copyright (c) 2012 The WebRTC project authors. All Rights Reserved.
 #
 # Use of this source code is governed by a BSD-style license
 # that can be found in the LICENSE file in the root of the source
 # tree. An additional intellectual property rights grant can be found
 # in the file PATENTS.  All contributing project authors may
 # be found in the AUTHORS file in the root of the source tree.
 
 # This file contains common settings for building WebRTC components.
 
@@ skipping 142 matching lines @@
 
     'conditions': [
       # Enable this to build OpenH264 encoder/FFmpeg decoder. This is supported
       # on all platforms except Android and iOS. Because FFmpeg can be built
       # with/without H.264 support, |ffmpeg_branding| has to separately be set
       # to a value that includes H.264, for example "Chrome". If FFmpeg is built
       # without H.264, compilation succeeds but |H264DecoderImpl| fails to
       # initialize. See also: |rtc_initialize_ffmpeg|.
       # CHECK THE OPENH264, FFMPEG AND H.264 LICENSES/PATENTS BEFORE BUILDING.
       # http://www.openh264.org, https://www.ffmpeg.org/
-      ['proprietary_codecs==1 and OS!="android" and OS!="ios"', {
+      ['OS!="android" and OS!="ios"', {
         'rtc_use_h264%': 1,
       }, {
         'rtc_use_h264%': 0,
       }],
 
       # FFmpeg must be initialized for |H264DecoderImpl| to work. This can be
       # done by WebRTC during |H264DecoderImpl::InitDecode| or externally.
       # FFmpeg must only be initialized once. Projects that initialize FFmpeg
       # externally, such as Chromium, must turn this flag off so that WebRTC
       # does not also initialize.
@@ skipping 329 matching lines @@
           # For access to standard POSIXish features, use WEBRTC_POSIX instead
           # of a more specific macro.
           'defines': [
             'WEBRTC_POSIX',
           ],
         }],
       ],
     },
   }, # target_defaults
 }