i found what caused the issue:
I accidentally also linked some other code to the application in which
a static initialization of a QNetworkAccessManger happened.
This also explains the different behavior between release and debug mode.
>> QEventLoop: Cannot be used without QApplication
>
> S
On Monday 30 March 2015 22:36:04 raven-worx Software wrote:
> As i said, i get it even when i just compile this piece of code and
> link to Qt binaries (core, gui, widgets, network) and only in release:
>
> int main(int argc, char *argv[])
> {
> QApplication app(argc, argv);
> return a
As i said, i get it even when i just compile this piece of code and
link to Qt binaries (core, gui, widgets, network) and only in release:
int main(int argc, char *argv[])
{
QApplication app(argc, argv);
return app.exec();
}
I guess this is only an issue on Windows.
>> QEventLoop:
> QEventLoop: Cannot be used without QApplication
Says everything.
Show your code.
Regards,
Konstantin
2015-03-30 23:21 GMT+04:00 raven-worx Software :
> Hi,
>
> i get the following print outs to the console and absolutley have no clue
> why:
>
> SHIMVIEW: ShimInfo(Complete)
> QEventLoop: Cann
Hi,
i get the following print outs to the console and absolutley have no clue why:
SHIMVIEW: ShimInfo(Complete)
QEventLoop: Cannot be used without QApplication
QObject::connect: Cannot connect (null)::aboutToQuit() to
QNativeWifiEngine::closeHandle()
But this only happens in RELEASE MODE! DEBU
