|Debugging the CDT build process [message #1118480]
||Fri, 27 September 2013 12:51
| Mark Thompson
Registered: September 2013
I'm having a couple of issues with the incremental build in Kepler/CDT 8.2.0 (MinGW, Windows 7):
I have a set of projects - one executable, several interdependent static libraries. Dependencies are expressed via Eclipse project references.
The first problem is that, if I perform a build explicitly through the project menu, then immediately run the application (causing an implicit/automatic build), it gets (needlessly?) rebuilt.
The second is that during a build, one of the low level libraries (upon which several of the others depend) is rebuilt up to five times.
Incidentally, this only manifested itself after I upgraded to Kepler (from Indigo) - perhaps one of my project files didn't convert perfectly?
I think what's going on is that the build settings are subtly different - enough for Eclipse to think a rebuild is necessary - though all the commands executed through gcc are the same (modulo ordering). Is there any way to get Eclipse to tell me why it thinks a rebuild is required?
Thanks for your help,
Powered by FUDForum
. Page generated in 0.02107 seconds