FR: Add ability to generate clang indexstore files for CC builds

[brentleyjones]

Description of the feature request:

Allow (probably via a feature) the ability for C/C++/Obj-C files to generate clang indexstore files (-index-store-path) for each source file. This is similar to the #15191 request.

What underlying problem are you trying to solve with this feature?

I have an IDE integration (Xcode) use case where I want -index-store-path index_store_path to be applied to each C/C++/Obj-C compilation, as the IDE consumes these files for indexing. These files need to be fetched from cache as well, so they need to be a declared output.

Which operating system are you running Bazel on?

No response

What is the output of bazel info release?

No response

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse master; git rev-parse HEAD ?

No response

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

I'm willing to contribute this change, if it will be accepted.

[brentleyjones]

cc @DavidGoldman

[DavidGoldman]

This seems like a reasonable FR, but a couple of things:

• Not all toolchains will support this (only Apple Clang can)
• I wonder if a tree artifact or zip file is better to store the indexstore output, if you go the route where each TU has its own index store, there can be a lot of duplicate record files making the indexstore output fairly large

[brentleyjones]

I plan on working on this in the near term.

[github-actions]

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 90 days unless any other activity occurs. If you think this issue is still relevant and should stay open, please post any comment here and the issue will no longer be marked as stale.