It's not a problem of Qt Creator. The mkspec used for the RPI3 is still valid unless your sysroot comes from a Debian Stretch were they have changed the library name. You need to modify the mkspec under devices that matches the Rpi3

@PatZim said in RaspberryPi2EGLFS tutorial fail at Step 10 "./configure": I am wondering if there is no native solution for Macs As you figured out yourself, I guess it all just comes down to get a cross-compiler for ARM that runs on Mac... But I bet using the VM with Linux is a good approach, given that lots of guides/tutorials are based on such platform

Did you try the this https://bugreports.qt.io/browse/QTBUG-62216 For the pi2 configuration the change should be something like this: -QMAKE_LIBS_EGL = -lEGL -lGLESv2 -QMAKE_LIBS_OPENVG = -lEGL -lOpenVG -lGLESv2 +QMAKE_LIBS_EGL = -lbrcmEGL -lbrcmGLESv2 +QMAKE_LIBS_OPENGL_ES2 = -lbrcmEGL -lbrcmGLESv2 +QMAKE_LIBS_OPENVG = -lbrcmEGL -lbrcmOpenVG -lbrcmGLESv2

I also stuck in that place with error: Project ERROR: Cannot run target compiler '<path>/arm-linux-gnueabihf-g++'. but indeed as @aha_1980 said: @aha_1980 said in Compiling QT on windows for cross compilation with raspberry, fails. Project ERROR: Cannot run target compiler: Maybe you forgot to setup the environment? The best checkout if compiler is accessible is to run in root dir where Qt sources are: // with entry in bashrc $ arm-linux-gnueabihf-g++ --version //or with absolute path: $ /home/<user_name>/<path-to-bin-where-compiler-is-located>/arm-linux-gnueabihf-g++ --version NOTE: replace <user_name> with your's user name, and replace <path-to-bin-where-compiler-is-located> with proper path as stated below. And then we should get info: arm-linux-gnueabihf-g++ (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) 4.8.3 20140303 (prerelease) ... The problem was with path to compiler: paths with "~" don't work, the best is to provide absolute path, for example: /home/<user_name>/<path-to-bin-where-compiler-is-located> // in my case: /home/<user_name>/raspi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin Or add in .bashrc path to compiler by adding at the end of file: export PATH=$PATH:/home/<user_name>/<path-to-bin-where-compiler-is-located> // in my case: export PATH=$PATH:/home/<user_name>/raspi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin Then running configure script we have: with absolute path: $ ./configure <other options> -device-option CROSS_COMPILE=/home/<user_name>/<path-to-bin-where-compiler-is-located>/arm-linux-gnueabihf- <other options> // in my case: $ ./configure <other options> -device-option CROSS_COMPILE=/home/<user_name>/raspi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin/arm-linux-gnueabihf- <other options> with entry in bashrc: $ ./configure <other options> -device-option CROSS_COMPILE=/home/<user_name>/<path-to-bin-where-compiler-is-located>/arm-linux-gnueabihf- <other options> //in my case: $ ./configure <other options> -device-option CROSS_COMPILE=arm-linux-gnueabihf- <other options> Tested on RPi3 (with Raspbian from 2019-09-26) and Qt 5.12.6, on Ubuntu 18.03.4 Cheers!

@moldovan.catalin You can create symbolic link in /opt/vc/lib pointing to these libraries but having old names.

Great ! Happy coding :)

Hi, Where did you get this library from in the first place ?

Old post but I had the same error; I had to build qtdeclarative BEFORE qwebchannel to solve this error.

@Zevero I had the same problem, is there a solution for the mouse click that doesn't work in the web pages.

@Wieland Yes, that seems a better idea, I'll do that, thanks for your help :)

@SGaist Indeed :)

@sneubert said: ~/raspi/sysroot/usr/include Thats correct. Tried to re-run rsync, stdio.h is there finally.

Hi Have you find any solution for this problem ?

@Andrei Sorry for delay. Your solution works perfect :). Thanks for help ;).