0

I've used the WebRTC DataConnection API in browsers a lot for p2p communication. Now I'd like to do the same within an iOS app.

I live and develop in a remote region with very slow Internet access. So building the webrtc source myself which involves a 6+ GB download to generate the static library is very difficult. I attempted from a different location and because of the complexity of the build process failed and ran out of time to debug.

I found the libjingle_peerconnection cocoa pod, but the static library this provides is over 70MB which seems too large for an iOS app. I'm wondering if it includes libjingle and webrtc video (I just want to use RTCDataChannels) code that isn't necessary?

I just need a prebuilt iOS arm64 library

Lightbeard
  • 4,011
  • 10
  • 49
  • 59
  • I'd think that if you were to check out the source, then deltas across a slow connection would typically be a lot less painful. Back when bandwidth was measured by how fast you could toss potatoes, we'd send out snapshots via fedex'd hard drives, and then use UUCP to copy the diffs across the unbelievably slow connections. Worked well enough. A modern revision control should do compression on the wire and the delta downloads are fairly compact (as long as there aren't a lot of binaries). Assumes the code is in a repository somewhere. – bbum Apr 30 '16 at 18:21
  • The problem is checking out the source - it apparently checks out all of chromium and the tools used are unfamiliar to me at least - depot tools, gclient sync. It's not like we are dealing with git or svn here – Lightbeard Apr 30 '16 at 20:38

1 Answers1

0

I've found a solution that works for my needs which is to use an entirely different iOS WebRTC implementation:

OpenWebRTC which has a great iOS SDK, examples, and pre-built binaries!

Lightbeard
  • 4,011
  • 10
  • 49
  • 59