Bug 53261 - gideon shows compiler errors in an endless loop
Summary: gideon shows compiler errors in an endless loop
Status: RESOLVED INTENTIONAL
Alias: None
Product: kdevelop
Classification: Applications
Component: Build tools: QMake (show other bugs)
Version: 3.0.0a4
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KDevelop-Devel List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-01-22 12:30 UTC by Sven Schmidt
Modified: 2003-10-31 12:04 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sven Schmidt 2003-01-22 12:30:15 UTC
Version:            (using KDE KDE 3.0.4)
Installed from:    Compiled From Sources
Compiler:          gcc 3.2 
OS:          Linux

Hi!

As I compiled a qt-Application created with the app-wizard, the compiler-messages were repeated in an endless loop.
I had to kill gideon. Manually compiled (in the console) the compiler messages were shown once.

Sven Schmidt
Comment 1 Amilcar do Carmo Lucas 2003-04-03 14:01:45 UTC
Can you retest this with current Gideon from CVS 
Comment 2 Jens Dagerbo 2003-04-18 15:55:23 UTC
This still happens with Alpha-4, but only if QTDIR isn't set correctly. 
Comment 3 Amilcar do Carmo Lucas 2003-07-01 20:29:37 UTC
This seams Trollproject related and not outputview
Comment 4 Jens Dagerbo 2003-10-29 23:12:33 UTC
Still in CVS. Again, assuming QTDIR isn't set.
Comment 5 Jens Dagerbo 2003-10-29 23:33:04 UTC
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?
Comment 6 Jens Dagerbo 2003-10-30 00:14:06 UTC
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.
Comment 7 Amilcar do Carmo Lucas 2003-10-30 10:40:35 UTC
This looks like a QMAKE (Trolltech) bug. Closing as wontfix
Comment 8 Andreas Koepfle 2003-10-31 12:04:02 UTC
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.