New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 3892 link

Starred by 10 users

Issue metadata

Status: Fixed
Last visit > 30 days ago
Closed: May 2018
NextAction: ----
OS: ----
Pri: 2
Type: Enhancement

Blocked on:
issue 5716

Sign in to add a comment

Data channel build target

Reported by, Oct 3 2014

Issue description

This is a follow-up to:

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.
Project Member

Comment 1 by, Oct 6 2014

Status: Assigned
Triage to pthatcher@
Project Member

Comment 2 by, Oct 7 2014

Should be possible (with some munging, perhaps) using HAVE_WEBRTC_VOICE=0 and HAVE_WEBRTC_VIDEO=0.

Comment 3 by, Oct 14 2014

Labels: Area-Build

Comment 4 by, 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

Comment 5 by, May 19 2015

There's been some excellent discussion about the need for a standalone WebRTC data channel library here:

I didn't know this was on the team's radar. Great news!

Comment 6 by, Jul 29 2015

Any updates? This would be enormously useful for WebTorrent.

Comment 7 by, Apr 5 2016

Huge +1 on this one for me! Please do it!

Project Member

Comment 8 by, Jan 30 2017

Labels: -Type-Bug Type-Enhancement
Fredrik, will the SlimWebRTC work address this use case?
Project Member

Comment 9 by, 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.


Project Member

Comment 10 by, Jan 31 2017

Blockedon: 5716
Project Member

Comment 11 by, May 4 2018

Status: Fixed (was: Assigned)
There's a data channel only target for Android:

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