compile_commands.json with different targets for the same source file

[Karim Ashraf Mohamed Hashish (KarimAshraf1995)]

When compile_commands json has more than one entry for different targets that use the same source file, I noticed that the extension chooses the first entry for the active source file.
Is there a way to control which compile commands entry to use when compile_commands.json has more than one target for the same source file ?

[Sean McManus (sean-mcmanus)]

Karim Ashraf Mohamed Hashish (@KarimAshraf1995) I don't believe so (other than moving it to the 1st entry). Can you provide an example of how a compile_commands.json has the same source file configured for different targets? That sounds like scenario we're not handling.

[Karim Ashraf Mohamed Hashish (KarimAshraf1995)]

Hi Sean McManus (@sean-mcmanus)

Here is a minimal example of this scenario

main.cpp

#include <iostream>

void func1()
{
#ifdef TARGET_1
    std::cout << "Target 1" << std::endl;
#elif defined(TARGET_2)
    std::cout << "Target 2" << std::endl;
#else
    std::cout << "Other" << std::endl;
#endif
}

int main()
{
    func1();
    return 0;
}

c_cpp_properties.json

{
    "configurations": [
        {
            "name": "Linux",
            "includePath": [
                "${workspaceFolder}/**"
            ],
            "defines": [],
            "compilerPath": "/bin/g++",
            "cStandard": "c11",
            "cppStandard": "c++17",
            "intelliSenseMode": "linux-gcc-x64",
            "compileCommands": ".vscode/compile_commands.json"
        }
    ],
    "version": 4
}

compile_commands.json

[
    {
        "file": "/home/karim/test/main.cpp",
        "directory": "/home/karim/test/build",
        "arguments": [
            "g++",
            "-c",
            "-o",
            "b.o",
            "-DTARGET_2",
            "/home/karim/test/main.cpp"
        ],
        "output": "/home/karim/test/build/b.o"
    },
    {
        "file": "/home/karim/test/main.cpp",
        "directory": "/home/karim/test/build",
        "arguments": [
            "g++",
            "-c",
            "-o",
            "a.o",
            "-DTARGET_1",
            "/home/karim/test/main.cpp"
        ],
        "output": "/home/karim/test/build/a.o"
    }
]

Note that "output" field is used to distinguish between different processing modes (output file) of the same source file as documented by the Json Compilation Database Specification

[Sean McManus (sean-mcmanus)]

I moved this to a feature request at #10508 .

[Ming-Hsuan-Tu (twmht)]

Sean McManus (@sean-mcmanus)

was this problem solved?