commit | 1af3d82b10e58741c87423ebea2cc51969d80397 | [log] [tgz] |
---|---|---|
author | Henrik Kjellander <kjellander@webrtc.org> | Thu Oct 05 08:28:43 2017 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Oct 05 08:28:51 2017 |
tree | 33b2ae0dea39cfaa8331ac535b606ad84a16022e | |
parent | 9185aca9ce1f66e983d9a5e797cab77a64cc46b0 [diff] |
Revert "Reland "Clean up libjingle API dependencies."" This reverts commit 9185aca9ce1f66e983d9a5e797cab77a64cc46b0. Reason for revert: Still breaks Chromium: https://build.chromium.org/p/chromium.webrtc.fyi/builders/Mac%20Builder/builds/29052 You cannot trust the *chromium* trybots due to https://bugs.chromium.org/p/chromium/issues/detail?id=771159 Original change's description: > Reland "Clean up libjingle API dependencies." > > This is a reland of 5117b047875970cf61f2403b590c44c37bfa8272 > Original change's description: > > > Clean up libjingle API dependencies. > > > > > > This CL moves candidate.h into the public API, since it has > > > been implicitly included before. > > > > > > This is a straightforward way of solving the circular > > > dependencies involving that file. For instance, > > > libjingle_peerconnection_api includes candidate.h from > > > jsepicecandidate.h, but _api can't depend on rtc_p2p, which > > > depends on _api. In fact, _api can't depend on much at all > > > since it's a very high level abstraction; instead, things > > > should depend on it. > > > > > > Furthermore, we have the case where deprecated headers > > > include headers in internal modules. I just have to turn > > > off include checking for those, but that's not a big deal. > > > > > > This CL punts the problem of callfactoryinterface.h being > > > implicitly included, and pulling in most of the call > > > module with it. This should be addressed in a follow-up > > > CL. > > > > > > Bug: webrtc:7504 > > > Change-Id: I1b1729408158418333ccdf702bf529386090f0d7 > > > Reviewed-on: https://webrtc-review.googlesource.com/2020 > > > Commit-Queue: Patrik Höglund <phoglund@webrtc.org> > > > Reviewed-by: Fredrik Solenberg <solenberg@webrtc.org> > > > Reviewed-by: Taylor Brandstetter <deadbeef@webrtc.org> > > > Cr-Commit-Position: refs/heads/master@{#20034} > > Bug: webrtc:7504 > Change-Id: Icae0ba1a0488550e2871cc65e66d3661707aa5b6 > Reviewed-on: https://webrtc-review.googlesource.com/6460 > Reviewed-by: Fredrik Solenberg <solenberg@webrtc.org> > Reviewed-by: Taylor Brandstetter <deadbeef@webrtc.org> > Commit-Queue: Patrik Höglund <phoglund@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#20156} TBR=phoglund@webrtc.org,deadbeef@webrtc.org,solenberg@webrtc.org Change-Id: I699c68bd330b537005c3f2b8fe31702025df4e39 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:7504 Reviewed-on: https://webrtc-review.googlesource.com/6800 Reviewed-by: Henrik Kjellander <kjellander@webrtc.org> Commit-Queue: Henrik Kjellander <kjellander@webrtc.org> Cr-Commit-Position: refs/heads/master@{#20157}
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 http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.