You can take a look into the generated Makefile

I solved it, the makefile contains this command as well:

flex MyLanguage.l

and in the OS there is two intalled flex, Qt used the wrong one.

I try with only one and after I added the 3 others to test. But indeed I get back to only one (Tools\mingw\bin) which contains g++.exe yes.

@Yash001 See https://doc.qt.io/qt-5/qtquick-debugging.html
"what is actual text of DQT_QML_DEBUG?" - there is no text.
-DQT_QML_DEBUG sets QT_QML_DEBUG define (such defines can be checked in C/C++ code using #ifdef QT_QML_DEBUG).
QT_QML_DEBUG activates "QML Debugging Infrastructure".

@tansgumus
ah, so the [] part was left and
it missed the actual body ? ( {})
Well these things happens :)

Depending on your Linux distribution you have "pre-prepared" packages to setup a basic development environment like build-essential on Debian.

I'm no expert but as far as i know, there is static and static. First static is static Qt-Libs second static is a real static standalone executable file.

If you want a real standalone executable you have to get a static version of all dependencies ".a" files not ".so". And you have to add some magic to the compiler -static -static-libgcc -static-libstdc++ (add in the Qt source to qtbase/mkspecs/linux-g++/qmake.conf) and if you want to use any kind of networking, you may also need static nss https://github.com/nss-dev/nss (some Linux versions still got static nss avaliable over packed managers).

And even if you don't use networking in your app, some other libs may include networking even if you don't use it in your code directly.

Good luck! :)

@SGaist said:

mkspecs/device/linux-rasp-pi2-g++

Shouldn't it maybe be mkspecs/device/linux-rasp-pi-g++ (without the 2)?
In his makefile there is this line:

INCPATH = -I../threadtest -I. -I/usr/local/qt5/mkspecs/devices/linux-rasp-pi-g++

Ok, just solved it through trial and error.

Had a messy QEventLoop and another place, which, however, was used during auth parsing.
Now it looks like this:

QNetworkAccessManager nam; QEventLoop loop; connect(&nam, &QNetworkAccessManager::finished, this, &RestConn::processReply); nam.get(*request); loop.connect(&nam, SIGNAL(finished(QNetworkReply*)),&loop, SLOT(quit())); loop.exec(QEventLoop::AllEvents);

And before - in the error case - the last two lines did not follow in correct order as they were:

// This order is not correct loop.exec(QEventLoop::AllEvents); loop.connect(&nam, SIGNAL(finished(QNetworkReply*)),&loop, SLOT(quit()));

Thanks to all anyway.