commit | c4d5642e136331459db922dbeb68f995d6f2411c | [log] [tgz] |
---|---|---|
author | Oleh Prypin <oprypin@webrtc.org> | Wed Nov 21 09:15:23 2018 |
committer | Commit Bot <commit-bot@chromium.org> | Wed Nov 21 09:20:41 2018 |
tree | b90b71308e5eaa1f2e985c836d2b2ec03bddc7af | |
parent | c69a56ef04c47c21cfd14009ed2465bee528d7de [diff] |
Revert "Default to dlopening the PipeWire." This reverts commit a13be019017449c57f48203d0fb778f34f7553a7. Reason for revert: The GN definitions cause problems for downstream tooling. They're also generally complicated and reach deep into Chromium's build which is undesirable. Setting `rtc_use_pipewire = true` by default should also be re-evaluated. Original change's description: > Default to dlopening the PipeWire. > > Reuse the existing infra from Chromium to do that. Additionally the > target_gen_dir needs to the added to the include directories, otherwise > the Chromium build will fail as it won't find the generated stubs. Also the > pw_properties_new() was replaced with pw_properties_new_string() as it doesn't > require a variadic parameter because the //tools/generate_stubs/generate_stubs.py > doesn't work with them correctly. With all these changes in place the PipeWire > support is enabled when compiling on Linux. > > Bug: chromium:682122 > Change-Id: I3bbc5efaecd9a08e20cbcf998b2cb534224eae7d > Reviewed-on: https://webrtc-review.googlesource.com/c/111081 > Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> > Reviewed-by: Brave Yao <braveyao@webrtc.org> > Commit-Queue: Tomáš Popela <tomas.popela@gmail.com> > Cr-Commit-Position: refs/heads/master@{#25720} TBR=phoglund@webrtc.org,mbonadei@webrtc.org,braveyao@webrtc.org,tomas.popela@gmail.com Change-Id: Iec20b07cb1cff7d57f8114ac6ec2d0d250e61214 No-Try: true Bug: chromium:682122 Reviewed-on: https://webrtc-review.googlesource.com/c/111584 Reviewed-by: Oleh Prypin <oprypin@webrtc.org> Commit-Queue: Oleh Prypin <oprypin@webrtc.org> Cr-Commit-Position: refs/heads/master@{#25722}
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.
Authoritative list of directories that contain the native API header files.