

This is supported on + # all platforms except iOS. 'use_objc_h264%': 0, - 'conditions':, + # Enable this to build OpenH264 encoder/FFmpeg decoder. +++ -141,21 +141,17 Enabling this may break interop with Android clients that support H264. > Cr-Commit-Position: Skipping CQ checks because original CL landed less than 1 days ago.Ĭr-Commit-Position: -git a/webrtc/build/common.gypi b/webrtc/build/common.gypi > the switch, this CL prevents chromium from using H.264 just > before we have chromium browser tests and are ready to flip > feature in Chrome, but because we do not want to do that

> This change would otherwise be enough to launch this > be able to test and enable H.264 in chromium. > Chromium build) and offical Chrome build, meaning we will

> This is used by both Chromium trybots (but not default > instead of rtc_use_h264=1 & ffmpeg_branding=Chrome. > can be used to enable this H.264 enc/dec implementation > This means proprietary_codecs=1 & ffmpeg_branding=Chrome > Default build flag |rtc_use_h264| to |proprietary_codecs| Trybots red? Don't have time to intvestigate Revert of Default build flag |rtc_use_h264| to |proprietary_codecs| if not on Android/iOS.
