CompileInfo folder place of -Y COMPILE_INFO and clangd --compile-commands-dir

[YangGangUEFI]

Related commit: 4ad7ea9

Refer to the code/commit, compile information file will write into <Build>/<BuildTarget>/<ToolChain>/CompileInfo folder.

When use clangd extension in VSCODE
There have some question:

1. When setting clangd.arguments --compile-commands-dir in VSCODE's setting.json , it seems that you must set the directory containing the compile_commands.json file on the root directory, so --compile-commands-dir does not seem to be able to use a certain fixed path for different BuildTarget or ToolChain. If there have some other way to use a fixed path for --compile-commands-dir?

For question 1., I tried to use compile_info_folder = Path(Wa.WorkspaceDir).joinpath("Build", "CompileInfo") to put it into a fixed path, but it changed the behavior of the current code, which seems not good😢.

Another way, set a path MACRO like EDK2_COMPILE_INFO_PATH?(Not tried)

[YangGangUEFI]

Solution:

Use https://github.com/intel/Edk2Code/ with EDK2: Rebuild index database cmd and configure VSCODE setting.json with:

    "clangd.arguments": [
        "--background-index",
        "--compile-commands-dir=${workspaceFolder}/.edkCode/"
    ],

[YangGangUEFI]

Close this discussion as main question solved.

But leave another little questions:

1. Workspace use subst X: . before build and ·subst /D X:after build need manual config subst X: .` again.(Maybe can auto map by current workspace/opened folder?)

2. Code jump to absolute path other than relative path.

3. Workspace without compile_commands.json.(Maybe need .clangd config file)

[YangGangUEFI]

1. maybe can do a path mapping(then update json file) in vscode extension
2. i think it is relate to folder path case-sensitive when vscode open file(maybe workspace path in compile_commands.json need update, now we changed the workspace folder path to lowercase always, but the file path is case-preserving in Windows)