Package wayland-scanner was not found in the pkg-config search path.
Perhaps you should add the directory containing `wayland-scanner.pc'
to the PKG_CONFIG_PATH environment variable
No package 'wayland-scanner' found
CMake Warning at /usr/share/ECM/find-modules/FindWayland.cmake:132 (message):
  Could not find wayland.xml in
Call Stack (most recent call first):
  /usr/share/cmake/Modules/CMakeFindDependencyMacro.cmake:93 (find_package)
  /usr/share/cmake/Modules/CMakeFindDependencyMacro.cmake:125 (__find_dependency_common)
  /usr/lib/cmake/Qt6/QtPublicDependencyHelpers.cmake:36 (find_dependency)
  /usr/lib/cmake/Qt6WaylandClient/Qt6WaylandClientDependencies.cmake:36 (_qt_internal_find_third_party_dependencies)
  /usr/lib/cmake/Qt6WaylandClient/Qt6WaylandClientConfig.cmake:50 (include)
  /usr/lib/cmake/Qt6/Qt6Config.cmake:263 (find_package)
  CMakeLists.txt:39 (find_package)


CMake Warning at /usr/lib/cmake/Qt6/Qt6Config.cmake:263 (find_package):
  Found package configuration file:

    /usr/lib/cmake/Qt6WaylandClient/Qt6WaylandClientConfig.cmake

  but it set Qt6WaylandClient_FOUND to FALSE so package "Qt6WaylandClient" is
  considered to be NOT FOUND.  Reason given by package:

  Qt6WaylandClient could not be found because dependency Wayland could not be
  found.

  Configuring with --debug-find-pkg=Wayland might reveal details why the
  package was not found.

  Configuring with -DQT_DEBUG_FIND_PACKAGE=ON will print the values of some
  of the path variables that find_package uses to try and find the package.

Call Stack (most recent call first):
  CMakeLists.txt:39 (find_package)


CMake Error at CMakeLists.txt:39 (find_package):
  Found package configuration file:

    /usr/lib/cmake/Qt6/Qt6Config.cmake

  but it set Qt6_FOUND to FALSE so package "Qt6" is considered to be NOT
  FOUND.  Reason given by package:

  Failed to find required Qt component "WaylandClient".

  Expected Config file at
  "/usr/lib/cmake/Qt6WaylandClient/Qt6WaylandClientConfig.cmake" exists



  Configuring with --debug-find-pkg=Qt6WaylandClient might reveal details why
  the package was not found.

  Configuring with -DQT_DEBUG_FIND_PACKAGE=ON will print the values of some
  of the path variables that find_package uses to try and find the package.



Traceback (most recent call last):
  File "/var/pisi/yakuake/actions.py", line 11, in setup
    kde5.configure()
  File "/usr/lib/pisilinux/pisi/actionsapi/kde5.py", line 57, in configure
    -DCMAKE_INSTALL_PREFIX=%s %s" % (libexecdir, qmldir, sysconfdir, plugindir, moduledir, prefix, parameters), installPrefix, sourceDir)
  File "/usr/lib/pisilinux/pisi/actionsapi/cmaketools.py", line 65, in configure
    if system(args):
  File "/usr/lib/pisilinux/pisi/actionsapi/shelltools.py", line 255, in system
    error(_("Command \"%s\" failed, return value was %d.") % (command, retValue))
  File "/usr/lib/pisilinux/pisi/actionsapi/__init__.py", line 27, in error
    raise Error(msg)
pisi.actionsapi.Error: Command "cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_C_FLAGS="-mtune=generic -march=x86-64 -O2 -pipe -fstack-protector -D_FORTIFY_SOURCE=2 -g -fPIC" -DCMAKE_CXX_FLAGS="-mtune=generic -march=x86-64 -O2 -pipe -fstack-protector -D_FORTIFY_SOURCE=2 -g -fPIC" -DCMAKE_LD_FLAGS="-Wl,-O1 -Wl,-z,relro -Wl,--hash-style=gnu -Wl,--as-needed -Wl,--sort-common" -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_BUILD_TYPE=Release -DKDE_INSTALL_LIBEXECDIR=/usr/lib -DCMAKE_INSTALL_LIBDIR=lib -DKDE_INSTALL_USE_QT_SYS_PATHS=ON -DKDE_INSTALL_QMLDIR=/usr/lib/qt5/qml -DKDE_INSTALL_SYSCONFDIR=/etc -DKDE_INSTALL_PLUGINDIR=/usr/lib/qt5/plugins -DECM_MKSPECS_INSTALL_DIR=/usr/lib/qt5/mkspecs/modules -DBUILD_TESTING=OFF -DKDE_INSTALL_LIBDIR=lib -Wno-dev -DCMAKE_INSTALL_PREFIX=/usr .." failed, return value was 1.
Action script error caught.
*** 1 error(s), 0 warning(s)
Program terminated.