a13be01901
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}
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.
Development
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.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- 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
- Coding style guide
- Code of conduct