Data channel build target
Reported by julian.b...@gmail.com, Oct 3 2014
This is a follow-up to: https://news.ycombinator.com/item?id=8401957 It would be useful to have a build target that builds the WebRTC data channel API without the media components (voice, video, etc). A use case for this would be a game server that wants to use WebRTC data channels for messaging.
Oct 6 2014,
Triage to pthatcher@
Oct 7 2014,
Should be possible (with some munging, perhaps) using HAVE_WEBRTC_VOICE=0 and HAVE_WEBRTC_VIDEO=0.
Oct 14 2014,
Apr 9 2015,
Any hints for how to achieve this in the meantime while we wait for a proper target? I removed HAVE_WEBRTC_VOICE and HAVE_WEBRTC_VIDEO from common.gypi, but the build system still tries to build some video-related-looking objects before finally failing at libjingle_media.webrtcvideocapturerfactory.o
Jul 29 2015,
Any updates? This would be enormously useful for WebTorrent.
Apr 5 2016,
Huge +1 on this one for me! Please do it! Thanks!
Jan 30 2017,
Fredrik, will the SlimWebRTC work address this use case?
Jan 31 2017,
I've been unaware of this specific need so the priorities for SlimWebRTC have focused first on making the code which depends on external libs pluggable (first codecs, then the network stack). Besides the dependency issue, that will also substantially reduce binary size. With SlimWebRTC we're restructuring the code so there won't be a need to create specific build targets and set up compiler flags in order to include/exclude certain functionality. Instead the set of build targets will be a more fine grained toolbox from which individual pieces can be picked and plugged together. See: https://bugs.chromium.org/p/webrtc/issues/detail?id=5716
Jan 31 2017,
May 4 2018,
There's a data channel only target for Android: https://cs.chromium.org/chromium/src/third_party/webrtc/sdk/android/BUILD.gn?type=cs&q=datachannelonly&sq=package:chromium&l=658 This ships WebRTC with data channels but not codecs. If your use case is outside Android, there is also work ongoing to make software codecs optional, so that will save you some binary size even if you don't use the datachannel-only target (not as much as a data-channel-only target would, but still a substantial saving). Marking as (partially) fixed; protest if there's anything significant we're not addressing.
Sign in to add a comment