teach vendor-libwebrtc.py how to exclude specific files when vendoring
Categories
(Core :: WebRTC, task, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox112 | --- | fixed |
People
(Reporter: mjf, Assigned: mjf)
Details
Attachments
(1 file, 3 obsolete files)
In Bug 1654112, we deleted a group of android java files that cause build issues are unused. However, having those files deleted in our github patch stack causes frequent rebase conflicts when upstream touches any of the files.
By teaching the vendoring script how to exclude specific files, we can remove the patch in our github patch stack that removes those files (avoid rebase conflicts) while continuing to exclude them from our build.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 1•2 years ago
|
||
Assignee | ||
Comment 2•2 years ago
|
||
Note, because libwebrtc has changed some of these files since we removed them for
Bug 1654112, these are restoring to the our current pull of libwebrtc (at the moment,
v108), not simply reversing the deletion in Bug 1654112.
Assignee | ||
Comment 3•2 years ago
|
||
They were generated from 4c49190ac9cb96033a0ed990816351b2d40fd47f
If you're playing along at home, these files can be regenerated
by following these steps:
git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git
export PATH=pwd
/depot_tools:$PATH
mkdir webrtc_android
cd webrtc_android
fetch --nohooks --no-history webrtc_android
( cd src ; ./build/install-build-deps.sh )
gclient runhooks
cd src
gn gen out/Debug --args='target_os="android" target_cpu="arm"'
autoninja -C out/Debug
After the build completes (lengthy), you will find the files under:
out/Debug/gen/sdk/android/peerconnection_java/generated_java/input_srcjars/org/webrtc
Depends on D170704
Assignee | ||
Comment 4•2 years ago
|
||
Depends on D170705
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 5•2 years ago
|
||
In the past, we have deleted a group of unused java files in our github patch stack.
That causes rebase conflicts when upstream edits any of those java files. Teaching
our vendoring script how to exclude those files will allow us to remove that patch
from our patch stack (avoid rebase conflicts) while also not including them in our
builds.
Comment 7•2 years ago
|
||
bugherder |
Description
•