New comment by Johnnynator on void-packages repository

https://github.com/void-linux/void-packages/pull/30918#issuecomment-842396767

Comment:
> I am not sure cross-compilation is possible :(
> QtWaylandScanner_EXECUTABLE is in qt5-wayland-devel. If that is placed in the hostmakedepends array, the configuration step works, but build fails because there is an arch mishmatch when wayland-scanner tries to compile a file:
> 
> ```
> 105/280] Automatic MOC for target systemclipboard
> [106/280] Generating wayland-wlr-data-control-unstable-v1-client-protocol.h
> FAILED: src/platform/x11/systemclipboard/wayland-wlr-data-control-unstable-v1-client-protocol.h 
> cd /builddir/CopyQ-4.1.0/build/src/platform/x11/systemclipboard && /usr/aarch64-linux-musl/usr/bin/wayland-scanner client-header /builddir/CopyQ-4.1.0/src/platform/x11/systemclipboard/wlr-data-control-unstable-v1.xml /builddir/CopyQ-4.1.0/build/src/platform/x11/systemclipboard/wayland-wlr-data-control-unstable-v1-client-protocol.h
> /bin/sh: line 1: /usr/aarch64-linux-musl/usr/bin/wayland-scanner: cannot execute binary file: Exec format error
> ninja: build stopped: subcommand failed.
> => ERROR: CopyQ-4.1.0_1: do_build: '${make_cmd} ${makejobs} ${make_build_args} ${make_build_target}' exited with 1
> => ERROR:   in do_build() at common/build-style/cmake.sh:82
> ```

You also need `wayland-devel` in hostmakepends. (and maybe also `-DWaylandScanner_EXECUTABLE=/usr/bin/wayland-scanner` in configure_args)