815b1a6f53
This CL makes it more flexible and easier to include/exclude H264 code when using other build systems because it delegates the decision to remove the code to the preprocessor instead of GN. This CL should be a noop, and for WebRTC/Chromium the GN param `rtc_use_h264` will still be the only thing to change in order to include/exclude H264. Moving code that requires ffmpeg or h264 out of the #ifdef/#endif part should break the build since dependencies are only added if `rtc_use_h264=true`. Bug: webrtc:9213 Change-Id: Ibc04edc2f6b9e51489ffe638d5be4b32959cdca0 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/137430 Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org> Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Reviewed-by: Stefan Holmer <stefan@webrtc.org> Reviewed-by: Erik Språng <sprang@webrtc.org> Cr-Commit-Position: refs/heads/master@{#28055}
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