Version: 3.9.98 (using KDevPlatform 0.9.98) (using 4.3.5 (KDE 4.3.5), 4.3.5-2.fc12 Fedora) Compiler: gcc OS: Linux (x86_64) release 2.6.31.12-174.2.3.fc12.x86_64 Problem: 1) I had gcc 4.4.2 installed. 2) I updated to gcc 4.4.3. 3) After opening my project, all stl statements in the code were marked as problems, because kDevelop couldn't find the stl include files. It was looking in /usr/include/c++/4.4.2, however, everything was now installed in /usr/include/c++/4.4.3 4) Rebuilding with CMake didn't solve it. Even completely removing the CMake build directory and then rebuilding didn't solve it. Eventually closing and reopening kDevelop made it find the correct path.
@david: feel free to mark as wontfix, IMHO its acceptable to have to restart kdevelop when upgrading such a core component as the compiler.
The gcc update occured when kdevelop was *closed*. You can restart kdevelop all you want after the update, but it will keep looking in the old include paths, hence marking half your code as problematic. You have to remove your project's CMake build directory first (a bit like the autotools' make distclean, but then the hard way), and *then* restart kDevelop.
That wasn't clear from your original description. So did building the project from the commandline work after the update and before clearing the builddir?
I realise that my original post was difficult to interpret. It is difficult to retest it now, since I already removed my old builddir. I think that building worked however. This probably means that CMake did notice the change in compiler verision, but that this change (of include paths) did not propagate into kDevelop unless it was restarted.
This would probably work correctly these days, at least for CMake, but in any case there's a more specific bug for this. *** This bug has been marked as a duplicate of bug 229406 ***