mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-19 16:25:38 +00:00
715e2622ab
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. Differential Revision: https://phabricator.services.mozilla.com/D75593 |
||
---|---|---|
.. | ||
build/internal | ||
chromium_deps | ||
google_apis/build | ||
net | ||
third_party/gflags | ||
tools/clang | ||
webrtc | ||
AUTHORS | ||
DEPS | ||
dummy_file.txt | ||
LICENSE | ||
Makefile.old | ||
OWNERS | ||
peerconnection_client.target.mk | ||
peerconnection.Makefile | ||
README.md |
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. This page is maintained by the Google Chrome team.
Development
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://chromium.googlesource.com/external/webrtc
- 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