Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

krfb: add pipewire dependency #35660

Closed
wants to merge 2 commits into from
Closed

krfb: add pipewire dependency #35660

wants to merge 2 commits into from

Conversation

ghost
Copy link

@ghost ghost commented Feb 17, 2022

Testing the changes

  • I tested the changes in this PR: YES

Local build testing

  • I built this PR locally for my native architecture, (x86_64-glibc)

This enables remote desktop functionality in KDE wayland

@ghost
Copy link
Author

ghost commented Feb 17, 2022

Adding qt5-wayland to hostmakedepends makes the cmake error go away, but a new error pops up while compiling:
[1/48] Generating wayland-zkde-screencast-unstable-v1-client-protocol.h FAILED: framebuffers/pipewire/wayland-zkde-screencast-unstable-v1-client-protocol.h /builddir/krfb-21.12.1/build/framebuffers/pipewire/wayland-zkde-screencast-unstable-v1-client-protocol.h cd /builddir/krfb-21.12.1/build/framebuffers/pipewire && /usr/armv7l-linux-gnueabihf/usr/bin/wayland-scanner client-header /usr/armv7l-linux-gnueabihf/usr/share/plasma-wayland-protocols/screencast.xml /builddir/krfb-21.12.1/build/framebuffers/pipewire/wayland-zkde-screencast-unstable-v1-client-protocol.h /bin/sh: line 1: /usr/armv7l-linux-gnueabihf/usr/bin/wayland-scanner: cannot execute binary file: Exec format error
So seems like the cross compiler tries to invoke the wayland-scanner of the host which doesn't work. Adding qt5-wayland to the normal makedepends instead doesn't solve the cmake error though.

@Johnnynator
Copy link
Member

Add -DWaylandScanner_EXECUTABLE=/usr/bin/wayland-scanner to configure_args.

@ghost
Copy link
Author

ghost commented Feb 17, 2022

I don't know what I did, but I can't reproduce my earlier issue anymore. Now I always get this error (with or without the added configure_args):

[1/18] Generating wayland-zkde-screencast-unstable-v1-client-protocol.h FAILED: framebuffers/pipewire/wayland-zkde-screencast-unstable-v1-client-protocol.h /builddir/krfb-21.12.1/build/framebuffers/pipewire/wayland-zkde-screencast-unstable-v1-client-protocol.h cd /builddir/krfb-21.12.1/build/framebuffers/pipewire && /usr/bin/wayland-scanner client-header /usr/armv7l-linux-gnueabihf/usr/share/plasma-wayland-protocols/screencast.xml /builddir/krfb-21.12.1/build/framebuffers/pipewire/wayland-zkde-screencast-unstable-v1-client-protocol.h /bin/sh: line 1: /usr/bin/wayland-scanner: No such file or directory

@Johnnynator
Copy link
Member

You need to add/keep qt5-wayland in hostmakedepends.

@ghost
Copy link
Author

ghost commented Feb 17, 2022

Seems like it didn't work, any other ideas?

Johnnynator pushed a commit to Johnnynator/void-packages that referenced this pull request Feb 17, 2022
@Johnnynator
Copy link
Member

Also needs wayland-devel. I picked you commits and merged them into my kde staging branch together with an update to 21.12.2., so will be in the main repo somewhen this weekend most likely.

Seems to work as good (or bad) as intended by upstream. (Sadly kwin doesn't support keyboard input with pipewire yet)

maciozo pushed a commit to maciozo/void-packages that referenced this pull request Feb 19, 2022
ftrvxmtrx pushed a commit to ftrvxmtrx/void-packages that referenced this pull request Mar 11, 2022
algor512 pushed a commit to algor512/void-packages that referenced this pull request Mar 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant