| "Invoking CDT Builder" takes long time [message #526938] |
Tue, 13 April 2010 14:28  |
 slajerek .
Messages: 20
Registered: April 2010 |
Junior Member |
|
|
I was looking in Google and Bugzilla pages but I wasn't able to find any information on this topic. So I have quite complicated project in C++ extended for long time, I updated settings and added many libraries to the g++ command line, also the makefile is run by "make -j 4". Anyway, it takes a very long time (more than 10 seconds) to start incremental build.
When I perform a very simple change in one file, then Build All, a message "Invoking CDT Builder" is shown, and nothing happens for long time. After that the make and compilation is done very fast. This is very annoying, actually I was thinking to change Eclipse to other workflow system, as this becomes not comfortable, just waiting 15 seconds for compilation after very simple change. Could it be that I have wrong settings somewhere? Why it takes 10 seconds or more for just simple task as running "make -j 4" in shell? If this is problem in Eclipse - what C++ (fast!!) editor you suggest for Linux (besides of classic emacs or vim of course)?
Edit: I realized that I have slightly older version of Eclipse. I'll download and test this behavior in newest release.
Edit2: newest version has the same behavior. It takes ~10 seconds to start incremental build with message "Invoking CDT Builder" (which later on takes <1 second). Would somebody be so kind and explain what exactly "Invoking" is doing for that long time on my 4-core 2.6GHz machine (very complicated computations I suppose), and how to avoid them...
[Updated on: Wed, 14 April 2010 10:15] Report message to a moderator |
|
|
|
| Re: "Invoking CDT Builder" takes long time [message #529043 is a reply to message #526938] |
Thu, 22 April 2010 17:07  |
David Wegener
Messages: 1445
Registered: July 2009 |
Senior Member |
|
|
<slajerek@gmail.com> wrote in message news:hq1v33$d93$1@build.eclipse.org...
>I was looking in Google and Bugzilla pages but I wasn't able to find any
>information on this topic. So I have quite complicated project in C++
>extended for long time, I updated settings and added many libraries to the
>g++ commandline, also the makefile is run by "make -j 4". Anyway, it takes
>a very long time (around 10 seconds) during incremental build.
> When I perform a very simple change in one file, then Build All, a message
> "Invoking CDT Builder" is shown, and nothing happens for long time. After
> that the make and compilation is done very fast. This is very annoying,
> actually I was thinking to change Eclipse to other workflow systems, as
> this becomes not comfortable waiting 15 seconds for compilation after very
> simple change. Could it be that I have wrong settings somewhere? Why it
> takes 10 seconds or more for just simple task as running "make -j 4" in
> shell? If this is problem in Eclipse - what C++ (fast!!) editor you
> suggest for Linux (besides of classic emacs or vim of course)?
Running "make -j 4" isn't necessarily a simple task. For complex projects,
make may need to examine a large number of files to figure out what needs to
be built. It has to go through all the dependencies of the make file to see
what has changed and what targets the changes affect. If the project is
complicated as you say, it is not surprising that it takes several seconds
before you start to see output from the command.
How long does it take to start outputting anything if you run the make
command from outside Eclipse on the command line?
You can turn off "Build Automatically" from the Project menu. This will
prevent the build step from running at each file save. You can manually
invoke Project->Build when you need an actual build.
|
|
|
|
|
| Re: "Invoking CDT Builder" takes long time [message #1779905 is a reply to message #1779892] |
Mon, 15 January 2018 16:27 |
David Vavra
Messages: 1426
Registered: October 2012 |
Senior Member |
|
|
To determine if it is make or Eclipse, change the build command to something like "pwd" and see how long it takes to produce output.
It's unlikely any make option (such as -j 4) will cause Eclipse to delay execution of make.
It's more likely it is make that is taking a long time.
You can test this by adding a target that does nothing but echo a message then make that target.
[Updated on: Mon, 15 January 2018 16:34] Report message to a moderator |
|
|
Powered by
FUDForum. Page generated in 0.02875 seconds
] 
Search
Help
Register
Login
Home
