e39daf4146
This reverts commit e1223747c27e22c4c4c3006af10d58aec9718b28. Reason for revert: Breaks WebRTC roll into Chromium. E.g: https://ci.chromium.org/ui/p/chromium/builders/try/cast_shell_linux/1166014/overview Original change's description: > wayland: Add a common interface for screencast and remote desktop portal > > Change adapts the `base_capturer_pipewire` so that a portal can be > injected in the capturer. This allows the remoting to inject its > own portal for the purpose of capturing desktop stream as long > as the injected portal provides implementation of the new interface > that is added as part of this change. > > Additionally, a method has been exposed on the capturer to get > details about the portal session so that the remoting > implementation can use the same underlying session for controlling > inputs on the remote host. > > Finally, desktop capturer interface is extended with a generic > method `GetMetadata` that is used to retrieve session related > information by CRD and relay it over to its input injector. Clients > provide override for the method and it eventually invokes the > underlying `GetSessionDetails` method on the portal instance. > > Bug: chromium:1291247 > Change-Id: I81b7ce3b949d8be2e24e2d303d5fbc76a849209c > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/256400 > Reviewed-by: Alexander Cooper <alcooper@chromium.org> > Commit-Queue: Salman Malik <salmanmalik@google.com> > Cr-Commit-Position: refs/heads/main@{#36323} Bug: chromium:1291247 Change-Id: I73fbb1b9a103d61fd8d7f04bb8452b3e29da9025 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/256801 Bot-Commit: rubber-stamper@appspot.gserviceaccount.com <rubber-stamper@appspot.gserviceaccount.com> Owners-Override: Henrik Boström <hbos@webrtc.org> Commit-Queue: Henrik Boström <hbos@webrtc.org> Cr-Commit-Position: refs/heads/main@{#36331}
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.
Development
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.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: https://ci.chromium.org/p/webrtc/g/ci/console
- Coding style guide
- Code of conduct
- Reporting bugs
- Documentation