b64ecd9960
The side effect of not filtering on V4L2_CAP_VIDEO_CAPTURE is that every device is enumerated twice. Because we look up devices by name, and the device that supports V4L2_CAP_VIDEO_CAPTURE seems to always appear first in /dev/video, this does not seem to end up with us ever choosing an inappropriate device. We might get away with just filtering device names from the list, but if the order of devices ever changed in /dev/video there could be problems. Bug: webrtc:11641 Change-Id: I16fee4edc873838ed4643ee16a8bbc699d6bbcf5 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/176460 Reviewed-by: Per Kjellander <perkj@webrtc.org> Commit-Queue: Dan Minor <dminor@webrtc.org> Cr-Commit-Position: refs/heads/master@{#31508}
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: http://build.chromium.org/p/client.webrtc
- Coding style guide
- Code of conduct