|Re: Eclipse vs make: which takes longer to "do nothing"? [message #900488 is a reply to message #899895]
||Tue, 07 August 2012 09:39
| Axel Mueller
Registered: July 2009
a) eclipse dumps output to a "Console View" which is very slow
b) eclipse parses the output, which is very slow
Yes, both are slow (but you get a list of errors/warnings!)
c) [your idea here]
Because Eclipse does not know which binaries were changed/created during the external build it has to scan the entire workspace. You can limit the search scope in Project Properties->C/C++ General_>Paths and Symbols->Output location
Q2: Eclipse supposedly is using the command "/usr/bin/gmake -j4" to perform the build. Why when I type this command in an xterm, I do not see the same output as Eclipse shows in the "Console View"?
a) Eclipse does not use the listed "build command" to perform the build. It uses a bunch of secret stuff.
Eclipse does exactly what you tell it! For me it seems that you called make in different directories. Therefore different Makefiles are actually build!
Before you ask
- search this forum
- see the FAQ http://wiki.eclipse.org/CDT/User/FAQ
Powered by FUDForum
. Page generated in 0.15442 seconds