Version: (using KDE KDE 3.1.3) Installed from: SuSE RPMs Compiler: gcc (GCC) 3.3 20030226 (prerelease) (SuSE Linux) OS: Linux Hi! Despite I chosed the debug configuration in the QMake-Manager, -DNO_DEBUG occurs in the compiler flags. Sven Schmidt
Somewhat hesistant after my last confused venture into qmake land, I'd say he's right. This is what I get in debug and release config: Debug: g++ -c -pipe -Wall -W -g -D_REENTRANT -DQT_THREAD_SUPPORT -DQT_SHARED -DQT_NO_DEBUG Release: g++ -c -pipe -Wall -W -O2 -D_REENTRANT -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -DQT_SHARED In other words, the same -D flags for both settings (just a different order). I can debug the project fine in KDevelop though, so I don't know if the flag matters much.. This was reproduced with a simple "qmake application" project from the KDevelop template.
Wich KDevelop version???????????????????????????????????????? WHY DO PEOPLE ALWAYS FORGET IT!!!!
Note that for a non-kdevelop project, the -DQT_NO_DEBUG does not show up on my machine. It's either getting defined somewhere in the .pro file or perhaps getting picked up from the QMAKESPEC.
-DQT_NO_DEBUG is not related to debugging your applications. It disables some internal warnings inside Qt library.