Summary: | gideon shows compiler errors in an endless loop | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Sven Schmidt <sschmidt> |
Component: | Build tools: QMake | Assignee: | KDevelop-Devel List <kdevelop-devel> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 3.0.0a4 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Sven Schmidt
2003-01-22 12:30:15 UTC
Can you retest this with current Gideon from CVS This still happens with Alpha-4, but only if QTDIR isn't set correctly. This seams Trollproject related and not outputview Still in CVS. Again, assuming QTDIR isn't set. Checking the make option "Abort on first error" could be seen as a workaround as this keeps it from happening. But interestingly, issuing "make -k" to the generated project from the commandline (with QTDIR not set) - independent from kdevelop - also creates this loop! So I guess the question is if this is a problem created with the qmake template or a bug in qmake? I just tried it with a .pro file not touched by KDevelop (namely the cdcat.pro from the http://cdcat.sf.net/ project) unset QTDIR, run qmake cdcat.pro and then make -k -> LOOP! This isn't our fault. I don't think it is worth trying to work around either. This looks like a QMAKE (Trolltech) bug. Closing as wontfix We should at least output a warning to the user, if QTDIR is not set. As some distributions unset QTDIR in startkde, everything works fine when running kdevelop from konsole but breaks down when starting kdevelop from the startmenu. This behaviour is really irritating to the user. |