New comment by Konata390 on void-packages repository

https://github.com/void-linux/void-packages/pull/35660#issuecomment-1042766278

Comment:
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.