Skip to content

compile_commands.json should not contain unresolved variables #6

Description

@lukka

When generating compile_commands.json for the Terminal repository (OpenConsole.slnx), some entries contain unresolved MSBuild variables such as $(OpenConsoleDir).

Example:

{
  "file": ".../src/cascadia/UnitTests_TerminalCore/ScreenSizeLimitsTest.cpp",
  "arguments": [
    "...",
    "/I[REDACTED]\\src\\cascadia\\UnitTests_TerminalCore\\\"$(OpenConsoleDir)\\src\\cascadia\\TerminalControl\\Generated Files\\\""
  ]
}

compile_commands.json is expected to contain concrete, fully resolved command lines (command or arguments with directory and file). Tools that consume this database generally expect paths and flags to be fully expanded, so unresolved tokens can break or degrade tooling behavior.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions