24
edits
Media/WebRTC/libwebrtc Update Process: Difference between revisions
Media/WebRTC/libwebrtc Update Process (view source)
Revision as of 16:03, 29 June 2023
, 29 June 2023Call out tip about tip::tip
(clarify when to run the save_patch_stack script) |
(Call out tip about tip::tip) |
||
| Line 84: | Line 84: | ||
* Stopping the loop-ff.sh manually is best done when in the <code>Test build</code> phase using Ctrl-c. | * Stopping the loop-ff.sh manually is best done when in the <code>Test build</code> phase using Ctrl-c. | ||
* [[libwebrtc GYP generated Java files|GYP generated Java files]] | * [[libwebrtc GYP generated Java files|GYP generated Java files]] | ||
* If you are requested to run <code>extract-for-git.py</code>, note that <code>loop-ff.sh</code> offers some information in initial vendoring that is is useful later, but not repeated in <code>verify_vendoring.sh</code>. Specifically, the tip about <code>tip::tip</code>: | |||
If you have previously run loop-ff.sh successfully, there may be a new | |||
change to third_party/libwebrtc that should be extracted and added to | |||
the patch stack in github. It may be as easy as running: | |||
./mach python dom/media/webrtc/third_party_build/extract-for-git.py tip::tip | |||
mv mailbox.patch /Users/jan-ivar/moz/elm/.moz-fast-forward/moz-libwebrtc | |||
(cd /Users/jan-ivar/moz/elm/.moz-fast-forward/moz-libwebrtc && \ | |||
git am mailbox.patch) | |||