Open aemonge opened 1 year ago
Hey @aemonge I think you have specified the value of CMAKE_MAKE_PROGRAM
incorrectly here. The typical build flow for this software is that we use CMake to find build dependencies and generate makefiles, which then hands off the building of the software to a program like GNU Make. The error happening here is that you have provided CMake in place of GNU Make.
Normally, we would expect to find the make program in the $PATH
environment variable, and the fact that it was not found points to a lack of build tools in the environment.
Furthermore, Arch Linux is not a currently supported Linux distribution, so I am afraid that you are also in uncharted territory here. I believe that the software should be buildable on Arch, but we don't have any experience or documentation on hand to draw from.
Hi @oskirby ,
Thanks a lot for the support. I know Arch is a bit different, but performance wise it excels (ask steam and the steam deck), so it would be great if mozilla can do more effort in this sense.
I'll keep this thread open for me, right now I need to update the packages; and that would take a bit more time for me to do so. As soon as a I find a solution, I'll post it here for anyone else looking for Arch support :)
Hey @oskirby , any ideas on how to solve this error:
Using Qt version 6.4.0
-- Found OpenSSL: /usr/lib/libcrypto.so (found version "1.1.1q")
-- Found PkgConfig: /usr/bin/pkg-config (found version "1.8.0")
-- Checking for module 'libsecret-1'
-- Found libsecret-1, version 0.20.5
Building sentry for Linux
-- Checking for module 'libsecret-1'
-- Found libsecret-1, version 0.20.5
-- Checking for module 'libcap'
-- Found libcap, version 2.66
-- Checking for module 'systemd'
-- Found systemd, version 251
CMake Error at src/CMakeLists.txt:66 (qt6_add_qml_module):
Unknown CMake command "qt6_add_qml_module".
Describe the bug When trying to install the VPN with a arch linux (steam deck), i'm getting the following error after instlled the QT library:
which I've fixed with the following, but got another error
┆Issue is synchronized with this Jira Bug