commit | 75abbe9c93681aeafc1e39ccdf04cb82f3aaf62c | [log] [tgz] |
---|---|---|
author | Fredrik Solenberg <solenberg@webrtc.org> | Wed Mar 19 16:57:55 2025 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Mar 19 21:39:34 2025 |
tree | 71ed62498b4ba324037402619d881556eb55b0b8 | |
parent | 05eb774a2441e9da4f0651c41c905e129a9682d2 [diff] |
Revert "Remove cricket::MediaType as a separate enum definition" This reverts commit 886c99a5ac7147b8228cd94204dde077fb1fab86. Reason for revert: breaks downstream project Original change's description: > Remove cricket::MediaType as a separate enum definition > > Using constants and alias names to ensure that existing code compiles. > The part that is not backwards compatible is switch statements that > don't have default; they will react to the new value ANY. > > Bug: webrtc:42222911 > Change-Id: I83320381d8f1b0acbf1adba3ac5c04bcd17e3d6f > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/381660 > Commit-Queue: Harald Alvestrand <hta@webrtc.org> > Reviewed-by: Evan Shrubsole <eshr@webrtc.org> > Cr-Commit-Position: refs/heads/main@{#44164} Bug: webrtc:42222911 No-Presubmit: true No-Tree-Checks: true No-Try: true Change-Id: Ifffddb374b6fd93cb151c40d62d645f863f0d2c1 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/381820 Reviewed-by: Harald Alvestrand <hta@webrtc.org> Auto-Submit: Fredrik Solenberg <solenberg@webrtc.org> Commit-Queue: Harald Alvestrand <hta@webrtc.org> Cr-Commit-Position: refs/heads/main@{#44166}
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.