Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] CDT Build - What does "Updating Project..." actually do ?

While progress monitor displaying this message, Eclipse refreshes project. Actually, Make Builder cannot guess which files in the project were modified during the build session., so it applies refreshLocal to the whole project, which is a time consuming operation for a big project, like in your case. At the first glance there is some space for optimization,. For example, maybe being a low priority operation, refreshing can be done out of the UI thread to avoid user waiting of its completion. But I'm afraid to make any estimations about performance improvement.

cebarne2@xxxxxxxxxxxxxxxxxxx wrote:


Some of our users of the CDT are complaining about poor performance.
there are many contributors to this, but one in particular is a
delay. After the makefile has been built, the build continues to run for
while with the "Updating Project..." message.  What is it doing?  With
of our projects, even if trivial builds, this can take 30 seconds or
(granted, there are a lot of files in the project).

For this particular project, there may be 500 C/C++ files, but only a
handful are used for the build.  There are likely thousands of files
These files are coming from a linked resource.  It is a standard make

If I can determine what is occuring at this time, I can begin to
bottlenecks (is it the network, the CM system, etc?).


Chad Barnes
Rockwell Collins, Inc.

cdt-dev mailing list

Back to the top