revert mozilla changes to mouse_cursor_monitor_pipewire.{h|cc} made in Bug 1816431
Categories
(Core :: WebRTC, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox112 | --- | fixed |
People
(Reporter: mjf, Assigned: mjf)
References
(Blocks 1 open bug)
Details
Attachments
(4 files)
The changes made to mouse_cursor_monitor_pipewire.{h|cc} made in Bug 1816431 were a result of a build error cause by a conflict between two headers:
X11/Xlib.h
third_party/libwebrtc/third_party/abseil-cpp/absl/functional/internal/any_invocable.h.
Those changes become unnecessary if third_party/libwebrtc/modules/desktop_capture/mouse_cursor_monitor_linux.cc
is added to the non-unified build list in dom/media/webrtc/third_party_build/gn-configs/webrtc.json
Fixing this will avoid further growing our github patch-stack on top of upstream libwebrtc.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 1•2 years ago
|
||
Bug 1816431 made changes to mouse_cursor_monitor_pipewire.{cc|h} to avoid a build
error due to a conflict between these two includes:
X11/Xlib.h
third_party/libwebrtc/third_party/abseil-cpp/absl/functional/internal/any_invocable.h.
Adding third_party/libwebrtc/modules/desktop_capture/mouse_cursor_monitor_linux.cc
to the non-unified build list will allow us to revert those changes to avoid
modifications to upstream libwebrtc.
Assignee | ||
Comment 2•2 years ago
|
||
Depends on D170508
Assignee | ||
Comment 3•2 years ago
|
||
These files can be reverted to their original content from upstream
with third_party/libwebrtc/modules/desktop_capture/mouse_cursor_monitor_linux.cc
no longer included in the unified build.
Depends on D170509
Assignee | ||
Comment 4•2 years ago
|
||
Assignee | ||
Comment 5•2 years ago
|
||
Grulja, would you mind testing one of the builds from the try run in comment 4 above to make sure my change has not broken your fix from Bug 1816431?
Assignee | ||
Comment 6•2 years ago
|
||
Depends on D170510
Comment 7•2 years ago
|
||
(In reply to Michael Froman [:mjf] from comment #5)
Grulja, would you mind testing one of the builds from the try run in comment 4 above to make sure my change has not broken your fix from Bug 1816431?
Yes, it seems to work.
Assignee | ||
Comment 8•2 years ago
|
||
(In reply to grulja from comment #7)
(In reply to Michael Froman [:mjf] from comment #5)
Grulja, would you mind testing one of the builds from the try run in comment 4 above to make sure my change has not broken your fix from Bug 1816431?
Yes, it seems to work.
Thank you!
Comment 9•2 years ago
|
||
:stransky, I noticed that there is a pipewire metabug. For the purposes of visibility or tracking should we be marking bugs that alter the pipewire code as blocking?
Updated•2 years ago
|
Comment 10•2 years ago
|
||
(In reply to Nico Grunbaum [:ng, @chew:mozilla.org] from comment #9)
:stransky, I noticed that there is a pipewire metabug. For the purposes of visibility or tracking should we be marking bugs that alter the pipewire code as blocking?
Sure.
Comment 11•2 years ago
|
||
Comment 12•2 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/6f2d46b0149f
https://hg.mozilla.org/mozilla-central/rev/502d213e5b41
https://hg.mozilla.org/mozilla-central/rev/73c40683d9de
https://hg.mozilla.org/mozilla-central/rev/b137aae3b7c5
Description
•