I have been using Eclipse for the past two years for an embedded linux project.
I can run my code on a Unbutu host unchanged and, as such, most of my testing on the host. Each project has a Debug configuration for the host and Target-Debug for the embedded linux device, which is built using instrumental cross-compilation.
There are more than 20 projects in my workspace consisting of libraries and executable files that turn to libraries. The problem is that anytime I create an executable, there seems to be no rhyme or reason why eclipse is rebuilding library links. He will almost always create several of them if no changes to the code in the libraries are changed. When he builds libraries, he creates the whole source in them, and not just a few files. In some cases, this will be done even when the target executable is updated and will not be rebuilt. I can clean the executable and then build. Make another assembly right now, and instead of reporting that everything is up to date, it can still create some of the libraries. Build another timeand he can again create the same libraries or in some cases, finally, inform that everything is up to date.
Each build configuration for the executable has an exact library referenced, unlike "active". For example, to configure the Target-Debug executable, I refer to the Target-Debug library assembly on which it depends. When I create executable files, it often happens that the configuration of the “active” assembly selected for libraries is not the same as the executable file that I create, but it does not matter if the assembly configuration of the executable file has specific library layout configurations.
,
. , Debug Target-Debug . , -, Project References ( C/++ General/Paths and Symbols/References).
Helios, Juno Kepler CDT.
, ? , , . , - - eclipse? ...
.