commit | 3c589beee6331dd3164cd95d9bcbf84abf7ed28f | [log] [tgz] |
---|---|---|
author | Rasmus Brandt <brandtr@webrtc.org> | Wed Mar 13 10:32:40 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Wed Mar 13 15:00:05 2019 |
tree | e013b1f3d62699ac1c4507d6e9393afc14b70795 | |
parent | c032109cda1de08ad06502c5924c0b82611b2f7e [diff] |
Reland "Change clip_name -> clip_path in VideoQualityTestFixture::Params::Video." This is a reland of 184f6d5d75c198cb7b70b8f9b75e0b5096c6e577. Incorrect build dependencies in downstream tests have been fixed, and an initialization bug in this CL has also been fixed. Original change's description: > Change clip_name -> clip_path in VideoQualityTestFixture::Params::Video. > > This allows external users of this test fixture to specify a custom > path, rather than just a custom file name. > > Bug: webrtc:10349 > Change-Id: I84e886c8bc28583017ce9ed7b9e7ee6a8e95730f > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/126227 > Reviewed-by: Karl Wiberg <kwiberg@webrtc.org> > Reviewed-by: Åsa Persson <asapersson@webrtc.org> > Commit-Queue: Rasmus Brandt <brandtr@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#27033} TBR: kwiberg@webrtc.org Bug: webrtc:10349 Change-Id: I0ec9dd26cd96c3db8ac8482893a26e62a1b1eefc Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/127181 Commit-Queue: Rasmus Brandt <brandtr@webrtc.org> Reviewed-by: Åsa Persson <asapersson@webrtc.org> Cr-Commit-Position: refs/heads/master@{#27102}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.