Yes, it is. But Qbs is better (IMHO), and you can use QtCreator && VSCode IDEs. ;) CMake it is pain...

@jsulm many thanks. Yes libgpsmm.h is ok, but the man page you pointed to also references libQgpsmm.

Hi and welcome to devnet, AFAIK, the QtQuick Compiler is a licensed product so you should check with the Qt Company directly. On a side note, it's likely going to be a host tools like qmake or moc so one thing you can try is to copy the one you already have in the binary folder of our self-built Qt.

Because I had the same Issues with the same Tutorial and often came along this discussion while searching for possible solutions, I took the privilege to dig up this old thread. With the help of What would be a pratical example of sysroot and prefix options for Qt and especially the mentioned option, quote:" -no-gcc-sysroot very specific hack for compilers that can't find their own crt inside --sysroot passes sysroot to pkgconfig and others, but not to gcc so that gcc will be called with -L/sysroot/lib/ correctly, but doesn't try to find implicit paths (crt) here. ", I was able to fix the problem.

@CybeX 1:I saw on google that someone else had this error with gcc 4.8. Upgrading solved it. Not saying it will for you. But was the only errors i could find in your log. 2: Sorry I don't know how to solve this. People are compiling for the PI but I never got around to try one so the details of getting it to work is also unknown to me. Update: I have a good eye to https://www.ics.com/blog/configuring-qt-creator-raspberry-pi but no board so didnt try yet.

@micland Yes, you are right. I was somehow lost. I needed to have qmake compiled for x86_64, but what confused me was that this binary was mixed together with other (ARM) binaries. Just to know. After config stage, it is possible to change CC variable in Makefile and get cross compiled qmake in a few minutes. Thank you and Regards !

Good catch ! I missed that one on your configure line. Since you have it working now, please mark the thread as solved using the "Topic Tool" button so that other forum users may know a solution has been found :)