How does the Eclipse CDT indexer cooperate with version control?

I use both Git and ClearCase for different projects. I always wonder how the Eclipse CDT indexer cooperates (or not!) with the underlying version control.

For example, when you “git checkout” another branch, or in ClearCase change your config spec, the entire source tree could change underneath you. The index needs to be refreshed or rebuilt.

  • No index in Eclipse CDT project checked out from SVN
  • Are there any tips/tricks people have? E.g. where to store the workspace, which options to check, which commands to run?

  • Using a single visual studio 2005 solution with multiple source control applications
  • Flexible vs static branching (Git vs Clearcase/Accurev)
  • How do I get Eclipse CDT to ignore files
  • How to get a version tree for a file in git?
  • ClearCase to Git migration
  • What is the best strategy when migrating from ClearCase to SVN?
  • One Solution collect form web for “How does the Eclipse CDT indexer cooperate with version control?”

    One feature you can use is the Scanner Discovery, also described in the FAQ and integrated in Eclipse Juno:

    CDT can parse output of my build and set includes (-I) and macros (-D) per file

    That can be useful when sources changes and the build is triggered again.
    Besides that, it is mainly View-->select Index-->rebuild when a ClearCase view or git working tree changes.
    The ClearCase view.dat or the .git repo metadata are ignored.

    Git Baby is a git and github fan, let's start git clone.