119
edits
Media/WebRTC/libwebrtc Update Process: Difference between revisions
Media/WebRTC/libwebrtc Update Process (view source)
Revision as of 14:16, 25 April 2023
, 25 April 2023added recommendation to always start with a fresh clone of elm
(no longer need to separately clone moz-libwebrtc github repo) |
(added recommendation to always start with a fresh clone of elm) |
||
| 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. | ||
* Starting with a fresh clone of elm is recommended for each new chromium milestone. | |||
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) | ||