Run compiler info collection in the execution root - #8406
Conversation
When the compiler has to resolve paths into the external directory, it has to be executed from the execution root.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request refactors BlazeCWorkspace.java to pass BlazeProjectData instead of WorkspaceRoot to the commit and collectCompilerSettingsInParallel methods. This allows the configuration to use the execution root path from BlazeProjectData rather than the workspace root directory. Additionally, unused imports were removed and minor formatting improvements were made. There are no review comments, so I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
github-actions
Bot
added
product: CLion
github-project-automation
Bot
moved this from Untriaged
to Done
in Bazel IntelliJ Plugin
github-actions
Bot
removed
the
awaiting-review
2 participants
When the compiler has to resolve paths into the external directory, it has to be executed from the execution root.