4 ms·
We did end up using libwebrtc but we had to strip a lot of the dependencies and also update it use system services instead where appropriate.
by om2 9y ago
We did end up using libwebrtc but we had to strip a lot of the dependencies and also update it use system services instead where appropriate.
- dbrgn 9y agoThat means you're aiming for WebRTC 1.0, not for ORTC, right?
- om2 9y agoFor now, yes. Our main goal in the short term is interop, since we are a little late to this party.
- Matthias247 9y agoThanks for the info. One more question on that: Do you think it makes sense to rerelease that independently or upstream the changes so that others could also include a more lightweight webrtc library? Or are your changes too far tied to Safari? I guess an optimal solution would need to have some kind of platform abstraction layer which then gets implemented by integrators like Chrome or Safari. Probably a big effort.
- microcolonel 9y agoThere's OpenWebRTC, which is optimized for standalone applications like media servers and proxies. The version in Chromium is also pretty easy to build and run in C/C++ applications on Linux, but requires extra work for an application like Safari.