Lines Matching +full:ship +full:- +full:to

7 --------------|-------------------------
12 [disclaimer](#legacy-disclaimer) below.
15 -------------------------------------------|--------------------------
37 changes, such changes will be announced in advance to
38 [discuss-webrtc@googlegroups.com][discuss-webrtc], and a migration
41 [discuss-webrtc]: https://groups.google.com/forum/#!forum/discuss-webrtc
46 ## <a name="legacy-disclaimer"></a>The legacy API directories contain some things you shouldn&rsquo…
48 The legacy API directories, in addition to things that genuinely
50 part of the API. We are in the process of moving the good stuff to the
56 don&rsquo;t grow too attached to them.
69 you to enable or disable parts of WebRTC at compile time.
71 Be sure to set them the same way in all translation units that include WebRTC
75 If you want to ship your own set of SSL certificates and inject them into WebRTC
76 PeerConnections, you will probably want to avoid to compile and ship WebRTC's
81 argument `rtc_builtin_ssl_root_certificates` to false and GN will define the
85 If you want to provide your own implementation of `webrtc::field_trial` functions
86 (more info [here][field_trial_h]) you will have to exclude WebRTC's default
91 argument `rtc_exclude_field_trial_default` to true and GN will define the
97 If you want to provide your own implementation of `webrtc::metrics` functions
98 (more info [here][metrics_h]) you will have to exclude WebRTC's default
103 argument `rtc_exclude_metrics_default` to true and GN will define the
110 always used. If you wish to exclude it from the build in order to preserve
113 argument `rtc_exclude_transient_suppressor` to true and GN will define the macro