Media/WebRTC/libwebrtc Update Process: Difference between revisions

Media/WebRTC/libwebrtc Update Process (view source)

Revision as of 20:12, 30 June 2023

47 bytes removed , 30 June 2023

Reorg the update steps using bulleted items so that clarifying comments can be adjacent to the relevant step

Mfroman

119

edits

@@ Line 16: / Line 16: @@
 === Update steps ===
- # Start from the elm checkout
+* Start from the elm checkout
   cd elm
- # Update the default config file for the next upstream milestone
+* Update the default config file for the next upstream milestone
   bash dom/media/webrtc/third_party_build/update_default_config.sh
- # Prepare the github repo
+* Prepare the git repository - Running <code>prep-repo.sh</code> will display instructions on how to add recent moz-central changes made in <code>third_party/libwebrtc</code> to the top of the patch stack in our git repository.  This is expected and necessary for successfully vendoring changes into <code>third_party/libwebrtc</code>.
   bash dom/media/webrtc/third_party_build/prep_repo.sh
- # Prepare no-op tracking files for cherry-pick commits
+* Prepare no-op tracking files for cherry-pick commits
   bash dom/media/webrtc/third_party_build/build_no_op_commits.sh
- # Save the newly updated patch-stack - run this in a bash shell
+* Save the newly updated patch-stack - run this in a bash shell
   (source dom/media/webrtc/third_party_build/use_config_env.sh ; \
    ./mach python dom/media/webrtc/third_party_build/save_patch_stack.py \
@@ Line 35: / Line 35: @@
    --separate-commit-bug-number $MOZ_FASTFORWARD_BUG
   )
- # bootstrap and sanity build
+* bootstrap and sanity build
   ./mach --no-interactive bootstrap --application-choice=browser && ./mach build
- # Run loop-ff.sh
+* Run loop-ff.sh
   bash dom/media/webrtc/third_party_build/loop-ff.sh
-Running <code>prep-repo.sh</code> with a fresh github clone of moz-libwebrtc will likely display instructions on how to add recent moz-central changes made in <code>third_party/libwebrtc</code> to the top of the patch stack in github.  This is expected and necessary for successfully vendoring changes into <code>third_party/libwebrtc</code>.
 === Reacting to loop-ff.sh ===