Installation and Deployment

Because the amount of blurp that is thrown over you obscures the real messages. I thought that is obvious.

@Christian-Ehrlicher @JonB @JoeCFD
I have tried the solution, but not GIF image format to work.

It's the windows path limiting to 260 characters.

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

I have this problem with remote device. Qt Creator 15.0.1

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

`

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.

Writing this down as I have-just solved this (at least the config part). I am targeting 6.4.2 on rpi4. I had exactly this problem. I am using the toolchain from https://toolchains.bootlin.com/releases_aarch64.html.

I have my sysroot of files copied from my rpi at:
$CROSSCOMPILE/rpi-sysroot
I have the toolchain sysroot at:
$CROSSCOMPILE/toolchain/aarch64--glibc--stable-2021.11-1/aarch64-buildroot-linux-gnu/sysroot

This is effectively the rpath for the linker.

I eventually managed to get a clean config run by coping libGLdispatch.so* from the rpi sysroot to the tool chain sysroot.

For reference in my toolchain.cmake I also have

set(GLESv2_INCLUDE_DIR ${RPISYSROOT}/usr/include/) set(GLESv2_LIBRARY ${RPISYSROOT}/usr/lib/aarch64-linux-gnu/libGLESv2.so)
So many posts from people having issues with this cross compile qt6 and so few answers.
Now on to try and get wayland module to work....

@Einstein38 By using another mirror: https://wiki.qt.io/Online_Installer_4.x

@PublicNameName Why do you want to build Qt by yourself? Just use Qt Online Installer to install Qt for MSVC.

@ikarona Can you help me step by step build source Installer Framework ?

I'm using a rocky9 VM running version 9.5 with QT 5.15.9 installed on the machine. The command "yum whatprovides */xkbcommon-x11.h" lists the packages libxkbcommon-x11-devel.x86_64 and libxkbcommon-x11-devel.i686. After a "sudo yum install libxkbcommon-x11-devel.x86_64" the file /usr/include/xkbcommon/xkbcommon-x11.h is installed.

@dondioci I build the qt installer framework is the same error ?

I'm sorry, but it's been too long ago. There have been so many changes in Qt since then, it very well may work now, but my procedure works correctly, so I haven't been motivated to experiment.

In fact, I don't think I'm even using github for my Qt source files any longer, but am obtaining them through the Qt maintenance tool. So, there are alternatives to my method.

When I selected such a Device:
android9.png
, the program almost started.
There was nothing in the Problems window.
But in the Output window there were warnings and errors:
output1.png
output2.png
.
And the program still did not start:

Oh, yes, I've forgotten that.