Media/WebRTC/libwebrtc Update Process: Difference between revisions

Media/WebRTC/libwebrtc Update Process (view source)

503 bytes removed , 15 June 2023

Now that some steps have been move, we can simplify some of the prereqs.

119

edits

@@ Line 4: / Line 4: @@
 === Prerequisites ===
 * 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.
-* Update the default config file for the next fast-forward operation.  This should be done in a separate bug, but if it has not been done prior, can be done at the beginning of the fast-forward operation as the first commit on elm.
+* Follow the [[Media/WebRTC/libwebrtc_Update_Process#Resetting_Elm|Resetting_Elm]] steps below.
- bash dom/media/webrtc/third_party_build/update_default_config.sh
+* Builds are done after vendoring in each commit.  A minimal, default .mozconfig is provided during the prep_repo step below.
-* After the updated default config lands on mozilla-central, follow the [[Media/WebRTC/libwebrtc_Update_Process#Resetting_Elm|Resetting_Elm]] steps below.
-* 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
- (cd elm && ./mach --no-interactive bootstrap --application-choice=browser && ./mach build)
 === Update steps ===