Closed Bug 1818052 Opened 2 years ago Closed 2 years ago

revert mozilla changes to mouse_cursor_monitor_pipewire.{h|cc} made in Bug 1816431

Categories

(Core :: WebRTC, defect, P2)

defect

Tracking

()

RESOLVED FIXED
112 Branch
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: nobody → mfroman
Severity: -- → S3
Depends on: 1816431
Priority: -- → P2

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.

Depends on D170508

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

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?

Flags: needinfo?(grulja)

(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.

Flags: needinfo?(grulja)

(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!

: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?

Flags: needinfo?(stransky)

(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.

Blocks: pipewire
Flags: needinfo?(stransky)
Pushed by mfroman@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/6f2d46b0149f pt1 - update files in webrtc.json non_unified_sources r=ng,stransky https://hg.mozilla.org/integration/autoland/rev/502d213e5b41 pt2 - moz.build updates r=ng,webrtc-reviewers https://hg.mozilla.org/integration/autoland/rev/73c40683d9de pt3 - revert changes to mouse_cursor_monitor_pipewire.{h|cc} from Bug 1816431 r=ng,stransky,webrtc-reviewers https://hg.mozilla.org/integration/autoland/rev/b137aae3b7c5 pt4 - remove accidentally added blank line in mouse_cursor_monitor_linux.cc from Bug 1816431. r=ng,webrtc-reviewers
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: