Media/WebRTC/libwebrtc Update Process: Difference between revisions

no longer need to separately clone moz-libwebrtc github repo
(add historical note on why we use a rebase script)
(no longer need to separately clone moz-libwebrtc github repo)
Line 5: Line 5:
* Create a new bug for the fast-forward update.  It should depend on the previous fast-forward bug.  [https://bugzilla.mozilla.org/show_bug.cgi?id=1800920 Bug 1800920] is an example.
* Create a new bug for the fast-forward update.  It should depend on the previous fast-forward bug.  [https://bugzilla.mozilla.org/show_bug.cgi?id=1800920 Bug 1800920] is an example.
* Builds are done after vendoring in each commit.  Having a <code>.mozconfig</code> file that enables cache (either sccache or ccache) will improve the performance of the scripts.
* Builds are done after vendoring in each commit.  Having a <code>.mozconfig</code> file that enables cache (either sccache or ccache) will improve the performance of the scripts.
git clone https://github.com/mozilla/libwebrtc moz-libwebrtc
  hg clone --stream ssh://hg.mozilla.org/projects/elm
  hg clone --stream ssh://hg.mozilla.org/projects/elm
  (cd elm && ./mach bootstrap --application-choice=browser && ./mach build)
  (cd elm && ./mach bootstrap --application-choice=browser && ./mach build)
119

edits