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

you forgot to do source ˜/.bashrc to let this command get activated export PATH=$PATH:/opt/qt5pi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin

@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 ;).