Open Bug 1498302 Opened 6 years ago Updated 2 years ago

Upstream BSD support in webrtc.org

Categories

(Core :: WebRTC: Audio/Video, enhancement, P3)

63 Branch
enhancement

Tracking

()

People

(Reporter: dminor, Unassigned)

References

(Blocks 1 open bug)

Details

We should try to upstream any changes required to build on the BSDs to webrtc.org. They're pretty small.

Chromium upstream rejected BSD patches. Do you expect reference WebRTC to be more friendly?
https://groups.google.com/a/chromium.org/d/msg/chromium-dev/b57hDs8yE4g/5tXefZ74AQAJ

Personally, I can't help due to reference WebRTC being married to Chromium:

  • Submitting patches requires Google Account (to sign CLA, interact with Gerrit) which is imossible to sign up over Tor
  • Standalone WebRTC build requires depot_tools which requires precompiled binaries, building which requires depot_tools
  • Without standalone build only WebRTC bundled in Firefox can be tested which is usually several (Chromium) milestones behind

Unlike Chromium, it's possible webrtc.org may accept the changes. Dan, before Jan (or you) puts any work into preparing a general webrtc.org patch for BSD to propose, can you feel out the webrtc.org people about if they'd accept them?

Flags: needinfo?(dminor)

I'll send an email to our contacts there this morning and report back here if I hear anything. I think it ends up being a small patch now that we're using cubeb for audio.

Flags: needinfo?(dminor)

IIRC it used to be a bunch of ifdefs and some BUILD.gn changes; not a lot of code, true

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.