Overzealous indexer

[gvl2023]

I have a makefile project. Makefiles are generated by cmake with unity builds enabled. The project has separate build/source folders, conceptually it is something like this:

project
  build
    unity.cpp
    unity.cpp.o
    unity.cpp.o.d
    Makefile
  src
    source1.cpp
    source2.cpp

Both build and src are linked to folders outside of workspace. unity.cpp includes both of the source files. Source location is rooted at the project level. Project refresh policy is set to refresh build. If I change source1.cpp and build the project it kicks off the indexer and it looks like it then reindexes the whole project. I have the "auto-update index" enabled but It appears there should be no changes to any of the source files under the build folder as a result of building the project so it's not clear to me why the indexer even starts. Can someone help me understand what is happening? Is there a way to enable debug trace or indexer log?

[jonahgraham]

The answer to your last part first - have a look at How to troubleshoot indexing issues

As for your main question - I am seeing more and more unity builds questions recently and I am not sure if any of the active CDT maintainers have looked at this area yet.

There are also lots of tracing options in CDT's core bundle. See FAQ How do I use the platform debug tracing facility (that link may be a little low level, somewhere there is a better document on how to set it up, but I can't find it right now so hopefully that is a good place to start)

Source location is rooted at the project level.

It seems to me that as the unity files have all the sources again that the source location should be set to src so you don't index unity.cpp.

Project refresh policy is set to refresh build.

What about workspace refresh? Is it off:

[gvl2023]

Workspace is set to refresh on access only. As for setting the source location to src, I think this will prevent the indexer from using discovered -I and -D values as they are kept with the unity files, or rather folders containing them as this is how I set it up. I'll try to get trace working and make sense of what is happening.

[jonahgraham]

Let me know if you need guidance on setting up the tracing options.