There's a problem that randomly occurs ( I guess a race issue), wondering if anyone else suffered from this.
But let me first explain my setup :
* project that builds a static lib
* 4 targets
- gcc debug
- gcc release
- cross compiler debug
- cross compiler release
* virtual target "all" ==> all 4
* include paths are specified on the "project" level
(Very) often when I (re)build "All" the first target (gcc debug) builds fine, and then second (sometimes the third, ..) fails, claiming it can not find a certain include file.
Press build (all) again, and it works.
It seems that during the switch to the next target, the compiler did NOT (YET??) receive the correct include paths [Note : I have never checked the compile log to see how it got actually called, next time I will take a closer look on this].
This is happening already for at least more then 6 months I think.
I use the debugger branch, but it might as well be present on the trunk.