Skip to main content



      Home
Home » Language IDEs » C / C++ IDE (CDT) » Real-time update of Problems view?
Real-time update of Problems view? [message #137126] Tue, 01 February 2005 09:53 Go to next message
Eclipse UserFriend
Originally posted by: none.nowhere.no

Managed make project: "make clean; make all". This takes a few minutes on
a project I'm working on; lots of code.

When errors are discovered by the GCC compiler, they show up in the
Console view in real time. However, they don't show up in the Problems
view until the entire compilation has completed.

This wastes a lot of time since when I see the first error, I usually
start looking into it while the rest of the build completes.

Any way (or plans) to improve this situation? Should I file this as a bug?

Regards,


/Martin.

PS. Right now I run a silly scheme where I do most editing in Eclipse,
then switch to Emacs for the initial build-edit-build-again cycle where I
kill syntax errors. When things compile, I go back to Eclipse, refresh,
and move on from there. That's a bit tiresome...
Re: Real-time update of Problems view? [message #137841 is a reply to message #137126] Fri, 04 February 2005 12:24 Go to previous message
Eclipse UserFriend
Originally posted by: alain.nowhere.ca

Martin Eskildsen wrote:

> Managed make project: "make clean; make all". This takes a few minutes on
> a project I'm working on; lots of code.

> When errors are discovered by the GCC compiler, they show up in the
> Console view in real time. However, they don't show up in the Problems
> view until the entire compilation has completed.

> This wastes a lot of time since when I see the first error, I usually
> start looking into it while the rest of the build completes.

> Any way (or plans) to improve this situation? Should I file this as a bug?


Not at this point, the is no possible callback when the build starts,
so basically:

= Eclipse starts the build
= all the markers(errors) are removed
= the logs are accumulated for processing
= at the end of the build we refresh the project
since files are modified/created/added outside of Eclipse knowledege
= the accumulated errors are set on the IResource


> PS. Right now I run a silly scheme where I do most editing in Eclipse,
> then switch to Emacs for the initial build-edit-build-again cycle where I
> kill syntax errors. When things compile, I go back to Eclipse, refresh,
> and move on from there. That's a bit tiresome...

eclipse-3.{0,1} as an automatic refresh, you should not have to do refresh
manually, look at the preference page it is probably off by default

Anyway .. good point .. an enhancement pr ??
Previous Topic:Can I debug a DLL by attaching it to an executing process (just as what we do with VC++)
Next Topic:Using variables for setting include paths
Goto Forum:
  


Current Time: Sun Jul 27 13:01:14 EDT 2025

Powered by FUDForum. Page generated in 0.04702 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top