| Summary: | -DNO_DEBUG despite debug configuration | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Sven Schmidt <sschmidt> |
| Component: | Build tools: QMake | Assignee: | KDevelop Developers <kdevelop-devel> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | 3.0.0b1 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Sven Schmidt
2003-11-06 11:21:24 UTC
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. |