commit | 25b0dee820a893888268a619c540ba6ccc49cfb5 | [log] [tgz] |
---|---|---|
author | Austin Orion <auorion@microsoft.com> | Thu Oct 01 20:47:54 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Oct 02 07:29:31 2020 |
tree | dd15dfd1189995d50498b0de8a3d8e32fe69bef5 | |
parent | 5b5abd79106a1770bb6fdab9e40f7270c7d4259a [diff] |
Reland "Begin implementing WGC CaptureFrame" This reverts commit 61709a3233174618d5ab46e1ee5847e4b150c7ef. Reason for revert: Some downstream projects have issues building this change due to the inclusion of the <windows.graphics.capture.h> header which is newly available in the Win 10 SDK v10.0.19041. To get around this issue for now, this change adds an off-by-default build flag for these files. However, in the future we will want to toggle this flag on, and the downstream projects will either need to update their SDK versions or toggle this flag in their WebRTC clone. Original change's description: > Revert "Begin implementing WGC CaptureFrame" > > This reverts commit e820cef5340610b9beebbcb63868743b95b97fcd. > > Reason for revert: Breaks downstream client. I will investigate and > get back with a suggestion to fix. > > Original change's description: > > Begin implementing WGC CaptureFrame > > > > This change introduces the design that will allow us to deliver frames > > synchronously to callers despite the Windows.Graphics.Capture APIs being > > inherently asynchronous. > > > > We achieve this by having WindowCapturerWinWgc create and maintain a > > WgcCaptureSession object for each window that it is asked to capture a > > frame for. The capture session object will be the class that actually > > uses the WGC APIs, and it will store the frames it receives in a frame > > pool and deliver them via GetMostRecentFrame. > > > > The next CL will add the necessary functionality to the > > WgcCaptureSession class. > > > > Bug: webrtc:9273 > > Change-Id: I44e164f4874503d8ccc8e6a210e74f9c8458f6c4 > > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/184220 > > Commit-Queue: Austin Orion <auorion@microsoft.com> > > Reviewed-by: Tommi <tommi@webrtc.org> > > Cr-Commit-Position: refs/heads/master@{#32240} > > TBR=mbonadei@webrtc.org,jamiewalch@chromium.org,tommi@webrtc.org,auorion@microsoft.com > > Change-Id: I114944357ce5be7d1e2da817703dc95d544aa99a > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: webrtc:9273 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/186045 > Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> > Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#32248} Bug: webrtc:9273 Change-Id: I9644fbf8f1fd1a84cb716176b8f14e3683a3f7cb Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/186423 Commit-Queue: Tommi <tommi@webrtc.org> Reviewed-by: Tommi <tommi@webrtc.org> Cr-Commit-Position: refs/heads/master@{#32286}
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 here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.