mirror of
https://github.com/kavishdevar/librepods.git
synced 2026-04-26 00:25:50 +03:00
[GH-ISSUE #435] Installation Issue #219
Labels
No labels
android
bug
documentation
enhancement
good first issue
help wanted
linux
pull-request
reverse-engineering
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librepods#219
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Pavel-M-Mihalik on GitHub (Jan 21, 2026).
Original GitHub issue: https://github.com/kavishdevar/librepods/issues/435
I got all the way to "cmake .." but then I received this error:
CMake Error at CMakeLists.txt:7 (find_package):
Found package configuration file:
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 "LinguistTools".
Expected Config file at
"/usr/lib/x86_64-linux-gnu/cmake/Qt6LinguistTools/Qt6LinguistToolsConfig.cmake"
does NOT exist
Configuring with --debug-find-pkg=Qt6LinguistTools 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.
I'm new to Linux (I've only been testing it for a few days), so I have no idea what to do. Can anyone help me, please?
@Brinsleym commented on GitHub (Jan 22, 2026):
This is very likely an issue with your machine not having the correct qt6 dev tools library, rather than an issue with librepods.
Install the
qt6-qttools-develpackage, and try to runcmake ..again. This package is:For fedora:
sudo dnf in qt6-qttools-devel,for ubuntu:
sudo apt-get install qt6-tools-dev.For debian:
sudo apt-get install qt6-tools-dev-toolsHopefully this fixes your problem!
@Bamoyski commented on GitHub (Feb 10, 2026):
I am facing the same issue, did you ever find a fix?