commit | a337cab322322875fddf51bb077607eb8c652c67 | [log] [tgz] |
---|---|---|
author | Jeremy Leconte <jleconte@webrtc.org> | Wed Mar 19 13:17:14 2025 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Mar 19 14:05:17 2025 |
tree | 212e087b1da1a79bbaff5ce19b89020919a2d2d6 | |
parent | 537158885bc60ffe64c2c0c8a7c89d74cb7c105b [diff] |
Revert "Checkout base/ only if fuzzing is enabled" This reverts commit 924b73c1d3110d8dfd7cd5c9c60e94a6db0fcb46. Reason for revert: This is breaking the DEPS update script (https://logs.chromium.org/logs/webrtc/buildbucket/cr-buildbucket/8721155299506494929/+/u/autoroll_DEPS/stdout) Original change's description: > Checkout base/ only if fuzzing is enabled > > Bug: webrtc:42223878 > Change-Id: I7d25551f8b82e84d4d123ef7768899342b87fde8 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/380120 > Auto-Submit: Daniel.L (Byoungchan) Lee <daniel.l@hpcnt.com> > Reviewed-by: Björn Terelius <terelius@webrtc.org> > Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org> > Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> > Cr-Commit-Position: refs/heads/main@{#44057} Bug: webrtc:42223878 Change-Id: I7c871bdad972859a501d0db84263d2a7466bf8cf Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/381760 Commit-Queue: Jeremy Leconte <jleconte@webrtc.org> Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Reviewed-by: Björn Terelius <terelius@webrtc.org> Bot-Commit: rubber-stamper@appspot.gserviceaccount.com <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#44163}
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.