028248cbd7
In order to implement a WebRTC component in Chromium, WebRTC needs to export some symbols. If RTC_EXPORT relies on COMPONENT_BUILD to mark symbols as exported or imported, it will not be possible to incrementally add RTC_EXPORT because the Chromium build will break (two Chromium components that export a symbol or no component that exports it). By using `rtc_enable_symbol_export` (which makes GN define WEBRTC_ENABLE_SYMBOL_EXPORT), WebRTC will be able to incrementally mark symbols with RTC_EXPORT and flip the value of `rtc_enable_symbol_export` in the Chromium build when everything will be ready. Bug: webrtc:9419 Change-Id: I57ab63c53545c500eaaefd75c112b4674aa7cf19 Reviewed-on: https://webrtc-review.googlesource.com/c/104980 Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org> Reviewed-by: Karl Wiberg <kwiberg@webrtc.org> Reviewed-by: Niels Moller <nisse@webrtc.org> Cr-Commit-Position: refs/heads/master@{#25087}
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