QCoreApplication::instance() is NULL
-
Since I don't know if you are using a shadow build, are you using the same names for your static debug release libraries ? Are you putting them in the same folder ?
If so you might be linking to a release version of your lib accidentally which in turn would pull the release Qt libraries.
-
wrote on 13 Jan 2016, 15:16 last edited by pullmoll
After posting to Qt development ML and getting a reply, an even simpler solution is to just
CONFIG -= debug_and_releasein the *.pro files of the staticlib submodules. I don't know why, but
debug_and_releaseseems to be a default. My project, developed with QtCreator since Qt4, doesn't define this flag. -
Since I don't know if you are using a shadow build, are you using the same names for your static debug release libraries ? Are you putting them in the same folder ?
If so you might be linking to a release version of your lib accidentally which in turn would pull the release Qt libraries.
wrote on 13 Jan 2016, 15:18 last edited by@SGaist said:
If so you might be linking to a release version of your lib accidentally which in turn would pull the release Qt libraries.
I'm using QtCreator and have separate shadow build directories for debug and release. The culprit was the
debug_and_releaseflag inCONFIGwhich I have to remove in the *.pro files... -
Still a bit strange but glad you found a solution :)
21/24