Extension can't be used in with VSCode Workspaces

[samopolacek]

The path to compile_commands,json, in case of a VSCode Workspace, is usually relative to ${fileWorkspaceFoler}, which is not supported by the extension.

[helly25]

You need to set: iwyu.compile_commands in your VSCode user or workspace settings (see https://github.com/helly25/vscode-iwyu/?tab=readme-ov-file#extension-settings). This was unfortunately documented wrong in the README.

You can set it like this:

{
    "iwyu.compile_commands": "${workspaceFolder}/compile_commands.json"
}

Note that ${workspaceFolder}/compile_commands.json is actually the default.

[helly25]

The reason you would still want ${fileWorkspaceFoler} over ${workspaceFoler} is that you are in a very rare case of multi-root-workspace. In all other case you can use the default of ${workspaceFoler}. If you are using CMake or other build-tool that places compile_commands.json under build, then for now you can just change the default in your settings as described in my earlier response.

Let me know if you are in a multi-root-workspace case.

[helly25]

This could maybe work. A rudimentary attempt is implemented in the current state of #10. Could you check if that works for you?

[helly25]

I extracted just the multi-root-workspace work into #12.

[helly25]

@samopolacek: The rudimentary multi-root-workspace support was just published as 0.1.16. Let me know how that works for you. If you find it lacking please reopen the issue.

[samopolacek]

@helly25 Yes, I am in a multi root workspace, hence I used fileWorkspaceFolder. I noticed that the extension started to work and was wondering why - it was #12 . Thank you!

[helly25]

Great to hear. I still need to find more time to debug such cases though before calling it an actual feature.