122
edits
Media/WebRTC/libwebrtc Update Process/automation plan: Difference between revisions
Jump to navigation
Jump to search
Media/WebRTC/libwebrtc Update Process/automation plan (view source)
Revision as of 16:56, 20 September 2022
, 20 September 2022add note on sccache or ccache in mozconfig to help with faster builds
(also build after bootstrap) |
(add note on sccache or ccache in mozconfig to help with faster builds) |
||
| Line 233: | Line 233: | ||
* Operational notes | * Operational notes | ||
- Builds are done after vendoring in each commit. Having a .mozconfig file that enables cache (either sccache or ccache) will improve the performance of the scripts. | |||
- 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>. | - 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>. | ||
- | - Two main types of errors will cause <code>loop-ff.sh</code> to exit; the first is a rebase conflict, the second is a build error due to api changes in upstream code. | ||