Skip to content

Installation and Deployment

Your Qt just doesn't want to build? Your compiler can't find the libs? Here's where you find comfort and understanding. And help.
9.7k Topics 50.8k Posts
QtWS25 Last Chance
  • 1 Votes
    6 Posts
    280 Views
    Hi @SlySven, perhaps the issue has been resolved already? I just did a complete run of 146 builds, and they all passed correctly. You can see the builds here. That said, on Ubuntu (only) I don't rely on install-qt-action to install Python, so perhaps that gets around the issue you mentioned? eg, I do this for Ubuntu runners (not macOs nor Windows): - uses: actions/setup-python@v5 with: python-version: '>=3.9' - uses: jurplel/install-qt-action@v4 with: ... setup-python: false Cheers.
  • 0 Votes
    2 Posts
    47 Views
    Hi @qtSucks, So why does it say it has found the package, then state wayland_found is set to false? It doesn't say it has found the package, it says it has found the Find Module. They way CMake find_package works is like so: when you request a package, CMake looks for a Find Module. once found, CMake executes the Find Module to locate the actual package. the Find Module sets variables (eg Wayland_FOUND) to indicate if Find Module found the package you're looking for (and where the libs are, etc). So here: find_package considered the following paths for FindWayland.cmake: ... The file was found at ... CMake is telling that the it found a Find Module at that location. CMake then should have evaluated the module, and that module reported that it can't find one or more of the libs you requested (ie set Wayland_FOUND to false). It might help if you show the output that came after your snippet above. Cheers.
  • 0 Votes
    2 Posts
    52 Views
    Hi, just a guess but try to reset the Scale to 100% (in Settings, System, Display)
  • Which Qt version is required for Win10/Win7

    Unsolved 8 Apr 2025, 07:41
    0 Votes
    6 Posts
    203 Views
    I would guess Qt6.x compiles fine with 32bits but it's not tested in the CI so officially unsupported.
  • Moving license to new system

    Unsolved 7 Apr 2025, 20:26
    0 Votes
    2 Posts
    93 Views
    @Steve-ONeill Shouldn't you install Qt on the new laptop anyway? Or how are you "transferring"?
  • 0 Votes
    8 Posts
    358 Views
    @Noobish If you want to be clean: target_link_libraries(fooserver Qt${QT_VERSION_MAJOR}::Core Qt${QT_VERSION_MAJOR}::Network)
  • 0 Votes
    4 Posts
    209 Views
    @Nguyen-Thang-Phong make sure to call perl init-repository in QT main repo. Make sure everywhere are similar branches. for QT i build like this in D:\qt\qt_test_s\qt5\qt5-build i create script and run it for STATIC QT (to make dynamic build you need to remove flag -static from configure call. call "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvarsall.bat" x86 10.0.17763.0 SET _ROOT=D:\qt\qt_test\qt5\ SET PATH=%_ROOT%\qtbase\bin;%_ROOT%\gnuwin32\bin;%PATH% SET PATH=%_ROOT%\qtrepotools\bin;%PATH% SET _ROOT= call ..\configure -prefix %CD%\qtbase -static -opensource -confirm-license -platform win32-msvc2017 -release ^ -nomake examples -nomake tests -skip qtwebengine -no-openssl -opengl desktop && -developer-build ^ call nmake module-qtbase module-qtdeclarative module-qttools module-qttranslations module-qtwinextras && ^ call nmake install After build is successful I create new script in D:\qt\qt_test_s\installer-framework to build installer framework Make sure installer framework is in correct branch also. You can take a look in installer-framework\INSTALL minimal required version of QT to build IF call "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvarsall.bat" x86 10.0.17763.0 SET QTDIR=D:\qt\qt_test_s\qt5\qt5-build\qtbase SET QTDIR_LIB=%QTDIR%\lib SET PATH=%QTDIR%\bin;%QTDIR%\..\..\gnuwin32\bin;%QTDIR_LIB%;D:\qt\qt_test_s\installer-framework\lib;%PATH% call qmake.exe && ^ call nmake && ^ call nmake install
  • 0 Votes
    1 Posts
    121 Views
    No one has replied
  • qDebug repeating output

    Unsolved 3 Apr 2025, 17:13
    0 Votes
    10 Posts
    413 Views
    @JonB Xcode is the macOS IDE offering for development for ANY Apple OS. I have been using it, on and off, since 2006 without too much in the way of problems but Xcode has changed a lot since I last used it in 2021 hence my rustiness. :-)
  • License for QT Open Source

    Unsolved 3 Apr 2025, 05:53
    0 Votes
    7 Posts
    203 Views
    The code of the installer framework is under the GPLv3. Any changes you do to the installer framework also need to be under the same license. However, any apps that are put into the installer can have any license. The GPL does not apply to the apps.
  • configure the build: -Wno-dev: what to do with it?

    Unsolved 2 Apr 2025, 16:21
    0 Votes
    9 Posts
    247 Views
    @Christian-Ehrlicher Well, I tried the obvious, i.e. adding the option -Wno-dev to the two lines with 'cmake' in the configure script. That didn't work. Hopefully, somebody who understands Qt's cmake-building can do it.
  • Installation issues

    Unsolved 2 Apr 2025, 11:31
    0 Votes
    2 Posts
    96 Views
    @Muhammad-Zeeshan Try another mirror like shown here: https://wiki.qt.io/Online_Installer_4.x
  • This topic is deleted!

    Unsolved 2 Apr 2025, 21:17
    0 Votes
    1 Posts
    3 Views
    No one has replied
  • How to using GIF image for QT ?

    Unsolved 31 Mar 2025, 08:01
    0 Votes
    23 Posts
    2k Views
    @Christian-Ehrlicher @JonB @JoeCFD I have tried the solution, but not GIF image format to work.
  • 0 Votes
    3 Posts
    119 Views
    It's the windows path limiting to 260 characters.
  • 0 Votes
    2 Posts
    128 Views
    P.S. an idea how to get the config to active the Qt Wayland driver for raspberry pi? Or does it do this only when building the target qt targeted at the pi? I can't find any documentation about put what option to put into configure or qt-configure-module it pure luck of finding a forum post and looking at others options so if anyone has any documentation for this it would be great. Qt Wayland Drivers: EGL .................................... yes Raspberry Pi ........................... no
  • 0 Votes
    1 Posts
    57 Views
    No one has replied
  • Cross compile build fails with qgrayraster.c

    Unsolved 29 Mar 2025, 07:25
    0 Votes
    3 Posts
    118 Views
    That's some good tips with the -E option thanks I had never considered using that. Yep my suspicious was an include directory but just wasn't sure on the approach you have given me some ideas thanks. What do you think about the no errors on configure but lots FAILED in a the CMakeConfigureLog.yaml? To me it seems off to give no error but then the log file shows errors. I am not lookign for a solution to why they faild but more why have errors but have a successful config. They seem to be tests which I suppose can be non required especially on a development branch. E.g. ` kind: "try_compile-v1" backtrace: - "/usr/share/cmake-3.28/Modules/Internal/CheckSourceCompiles.cmake:101 (try_compile)" - "/usr/share/cmake-3.28/Modules/CheckCXXSourceCompiles.cmake:52 (cmake_check_source_compiles)" - "cmake/QtFeature.cmake:968 (check_cxx_source_compiles)" - "configure.cmake:207 (qt_config_compile_test)" - "cmake/QtBaseGlobalTargets.cmake:83 (include)" - "CMakeLists.txt:125 (include)" directories: source: "/home/tommy/projects/rPi4_OS/crossCompile/qt6/qtpi-build2/CMakeFiles/CMakeScratch/TryCompile-zWMx1V" binary: "/home/tommy/projects/rPi4_OS/crossCompile/qt6/qtpi-build2/CMakeFiles/CMakeScratch/TryCompile-zWMx1V" cmakeVariables: CMAKE_CXX_FLAGS: " -I/home/tommy/projects/rPi4_OS/crossCompile/toolchain/aarch64--glibc--stable-2021.11-1/aarch64-buildroot-linux-gnu/sysroot/usr/include" CMAKE_CXX_FLAGS_DEBUG: "-g" CMAKE_EXE_LINKER_FLAGS: "-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed" CMAKE_MODULE_PATH: "/home/tommy/projects/rPi4_OS/crossCompile/qt6/qtbase/cmake;/home/tommy/projects/rPi4_OS/crossCompile/qt6/qtbase/cmake/3rdparty/extra-cmake-modules/find-modules;/home/tommy/projects/rPi4_OS/crossCompile/qt6/qtbase/cmake/3rdparty/kwin;/home/tommy/projects/rPi4_OS/crossCompile/qt6/qtbase/cmake/platforms" CMAKE_POSITION_INDEPENDENT_CODE: "ON" CMAKE_SYSROOT: "/home/tommy/projects/rPi4_OS/crossCompile/toolchain/aarch64--glibc--stable-2021.11-1/aarch64-buildroot-linux-gnu/sysroot" buildResult: variable: "HAVE_reduce_relocations" cached: true stdout: | Change Dir: '/home/tommy/projects/rPi4_OS/crossCompile/qt6/qtpi-build2/CMakeFiles/CMakeScratch/TryCompile-zWMx1V' Run Build Command(s): /usr/bin/ninja -v cmTC_84697 [1/2] /home/tommy/projects/rPi4_OS/crossCompile/toolchain/aarch64--glibc--stable-2021.11-1/bin/aarch64-linux-g++ --sysroot=/home/tommy/projects/rPi4_OS/crossCompile/toolchain/aarch64--glibc--stable-2021.11-1/aarch64-buildroot-linux-gnu/sysroot -DHAVE_reduce_relocations -I/home/tommy/projects/rPi4_OS/crossCompile/toolchain/aarch64--glibc--stable-2021.11-1/aarch64-buildroot-linux-gnu/sysroot/usr/include -std=gnu++17 -fPIE -o CMakeFiles/cmTC_84697.dir/src.cxx.o -c /home/tommy/projects/rPi4_OS/crossCompile/qt6/qtpi-build2/CMakeFiles/CMakeScratch/TryCompile-zWMx1V/src.cxx FAILED: CMakeFiles/cmTC_84697.dir/src.cxx.o /home/tommy/projects/rPi4_OS/crossCompile/toolchain/aarch64--glibc--stable-2021.11-1/bin/aarch64-linux-g++ --sysroot=/home/tommy/projects/rPi4_OS/crossCompile/toolchain/aarch64--glibc--stable-2021.11-1/aarch64-buildroot-linux-gnu/sysroot -DHAVE_reduce_relocations -I/home/tommy/projects/rPi4_OS/crossCompile/toolchain/aarch64--glibc--stable-2021.11-1/aarch64-buildroot-linux-gnu/sysroot/usr/include -std=gnu++17 -fPIE -o CMakeFiles/cmTC_84697.dir/src.cxx.o -c /home/tommy/projects/rPi4_OS/crossCompile/qt6/qtpi-build2/CMakeFiles/CMakeScratch/TryCompile-zWMx1V/src.cxx /home/tommy/projects/rPi4_OS/crossCompile/qt6/qtpi-build2/CMakeFiles/CMakeScratch/TryCompile-zWMx1V/src.cxx:2:4: error: #error Symbolic function binding on this architecture may be broken, disabling it (see QTBUG-36129). 2 | # error Symbolic function binding on this architecture may be broken, disabling it (see QTBUG-36129). | ^~~~~ ninja: build stopped: subcommand failed. exitCode: 1 `
  • Qt 6.5.1 Program execution

    Unsolved 1 Jun 2023, 16:10
    0 Votes
    8 Posts
    5k Views
    I caught the same problem with my Ubuntu 20.04 and Qt 6.7.1. I fixed it. You need to get the latest libwayland and build it. I hope the next instructions helps you: Download the source code from https://gitlab.freedesktop.org/wayland/wayland and checkout the latest version (in my case, it was 1.23.1) Build with instructions from README.txt with PREFIX (the path to the library is in your system). Create /etc/ld.so.conf.d/wayland.conf and put in it the path to your new wayland libs (in my case: /opt/wayland/lib64) Do sudo ldconfig I hope it helps.
  • 0 Votes
    1 Posts
    58 Views
    No one has replied