I'm trying to install maliit-keyboard. Most other distros, including Arch seem to have it in the repo. So I downloaded the PKGBUILD from the Arch repo, replace qt5-feedback with qtfeedback and comment out the language packages from makedepends. When I run "makepkg -s" I get a failure because cmake can not find Qt5::Feedback

`==> Making package: maliit-keyboard 2.3.1-2 (Wed 06 Dec 2023 11:49:12 PM EST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found maliit-keyboard-2.3.1.tar.gz
==> Validating source files with sha256sums...
maliit-keyboard-2.3.1.tar.gz ... Passed
==> Extracting sources...
-> Extracting maliit-keyboard-2.3.1.tar.gz with bsdtar
==> Removing existing $pkgdir/ directory...
==> Starting build()...
-- Could NOT find AnthyUnicode (missing: AnthyUnicode_LIBRARIES AnthyUnicode_INCLUDE_DIRS)
-- Could NOT find Anthy (missing: Anthy_LIBRARIES Anthy_INCLUDE_DIRS)
-- Could NOT find Pinyin (missing: Pinyin_LIBRARIES Pinyin_INCLUDE_DIRS)
-- Could NOT find Chewing (missing: Chewing_LIBRARIES Chewing_INCLUDE_DIRS)
-- Configuring done (0.2s)
CMake Error at CMakeLists.txt:175 (target_link_libraries):
Target "maliit-keyboard-common" links to:

Qt5::Feedback

but the target was not found. Possible reasons include:

* There is a typo in the target name.
* A find_package call is missing for an IMPORTED target.
* An ALIAS target is missing.

-- Generating done (0.2s)
CMake Generate step failed. Build files cannot be regenerated correctly.
==> ERROR: A failure occurred in build().
Aborting...
`

This looks to be a behavior within cmake, or can I add something in PKGBUILD to fix this? Was it erroneous to assume qtfeedback is the proper package to replace qt5-feedback? Is maliit-keyboard already conveniently available in some other format that I missed?

As the error shows, it needs anthy/ibus, that is why it is not in the repo. ibus is pretty much abandoned, but bigger issue is that it needs a huge part of the Gnome desktop.
Trials have been done to add Maliit without ibus, unsuccesfully:
https://github.com/KaOSx/apps/commit/86221750ae6cf0fe09c28fb0a76508f104ebc4dc
You could have saved yourself a lot of time, if checked KaOS git first, instead of looking at another distro 🙂

    demm

    Thank you for the info, but could I?

    A search on github.com "repo:KaOSx/apps maliit" returns no matches, as does the KCP. Conversely, "cura" also returns no matches on either, yet I pulled a PKGBUIILD from the UAR and with a simple replacement of fuse for fuse2 I have a functional cura-slicer. So I pulled from the repo instead of the UAR, but where's the flag that should signal to me "turn back, this way lies madness"?

    And is it the case then at qt5-virtualkeyboard is the only on-screen keyboard option for KaOS at this time?