Installation and Deployment

Aha! Thanks @jeremy_k
The final answer was qt.*.debug=false. I now see the qDebug() warnings, but not all the annoyinbg QT logs.
So my qtlogging.ini looks like

qt.*=false *.debug=true qt.*.debug=false qt.qpa.xcb.xcberror.warning=false

Thanks again, both of you!

@Scarab said in Static Qt Error: Qt version is not properly installed, please run make install:

"pass the relocatable flag to configure". I don't know how to do that either, there is no configure field in the Qt versions tab

"configure" is the command you execute before you build Qt. You need to pass relocatable flag to configure before you actually build Qt.

I think you just have to keep trying different mirrors. Are you claiming every one of them returns Forbidden? That would be different.

Hi and welcome to devnet,

You should take a look at the content of the tests run by the configure script to see what exactly failed with regard to EGLFS.

The NVIDIA forum might also contain some hints.

Then explicitly call the version of Python you want to use when executing your script.

As for conda VS venv, it highly depends on your goal.
You might also want to consider using something like uv that will help you manage your dependencies and environnement.

Since you are starting fresh, I would recommend testing uv.

Hi,

What does ~file qmake6 return ?

dnf -y update this morning.

Skipped:
qt5-qtbase-5.15.15-1.fc40.x86_64 qt5-qtwebengine-freeworld-5.15.17-1.fc40.x86_64

When configure Qt, did you add the following arguments?
It seems that the package won't be built unless you explicitly use them.
-eglfs -qpa wayland-egl -qpa xcb

Disabling the precompile headers by using the option "-no-pch" resolved this issue.

Fortunately it seems that this bug has been fixed in Qt version 6.8.0

Just comment the line. It worked for me.

@jsulm SURE I will, thanks a lot...

Just comment the line, it worked for me (cstddef file).

I have the same issue but now with Qt6.

OS: Ubuntu 24.0.1 Qt: Creator 6.7.3 Compiler: gcc/g++ 13.2 IDE: MS Visual Studio Code (from snap) Extensions installed in MVSC: ms-vscode.cpptools, twxs.cmake, ms-vscode.cmake-tools, theqtcompany.qt, theqtcompany.qt-cpp-pack and tonka3000.qtvsctools Qt's installation folder: home/Qt/ Qt example's folder: home/Qt/Examples/Qt-6.7.3/widgets/widgets/calculator/

I'm trying to run this example using CMakeLists.txt and c_cpp_properties.json.
c_cpp_properties.json in .vscode:

{ "configurations": [ { "name": "Linux", "includePath": [ "${workspaceFolder}/**", "/home/arantxa/Qt/6.7.3/gcc_64/include/**", "/home/arantxa/Qt/6.7.3/gcc_64/include/QtWidgets/" ], "defines": [], "compilerPath": "/usr/bin/gcc", "cStandard": "c17", "cppStandard": "gnu++17", "intelliSenseMode": "linux-gcc-x64" } ], "version": 4 }

The top-level CMakeLists.txt:

# Copyright (C) 2022 The Qt Company Ltd. # SPDX-License-Identifier: LicenseRef-Qt-Commercial OR BSD-3-Clause cmake_minimum_required(VERSION 3.16) project(calculator LANGUAGES CXX) find_package(Qt6 REQUIRED COMPONENTS Core Gui Widgets) qt_standard_project_setup() qt_add_executable(calculator button.cpp button.h calculator.cpp calculator.h main.cpp ) set_target_properties(calculator PROPERTIES WIN32_EXECUTABLE TRUE MACOSX_BUNDLE TRUE ) target_link_libraries(calculator PRIVATE Qt6::Core Qt6::Gui Qt6::Widgets ) install(TARGETS calculator BUNDLE DESTINATION . RUNTIME DESTINATION ${CMAKE_INSTALL_BINDIR} LIBRARY DESTINATION ${CMAKE_INSTALL_LIBDIR} ) qt_generate_deploy_app_script( TARGET calculator OUTPUT_SCRIPT deploy_script NO_UNSUPPORTED_PLATFORM_ERROR ) install(SCRIPT ${deploy_script})

Everything that is required, every include, is listed! I'm not sure what should I do.

I was able to resolve replacing "/snap/bin/cmake" for:
cmake.cmakePath = /snap/cmake/current/bin/cmake

This is a user-driven forum. For license problems you should contact TQtC directly through your support channel.

Hmm I think the problem was that I didn't run the binary with sudo.

@A-Akshatha said in QT Compilation:

Can we make it compatible with 2017

If you mean 'we' with you - maybe. I doubt you will find other people using this old version with this old compiler.