Fix #4484: compileFile with presets

[Copilot]

This change addresses item #[[put issue number here to generate a link]]

This changes visible behavior

cmake.compileFile could not find compilation information when using presets unless CMAKE_EXPORT_COMPILE_COMMANDS was explicitly set. This causes single-file compilation to fail despite a successful configure.

The following changes are proposed:

• Preset configure arguments: Append -DCMAKE_EXPORT_COMPILE_COMMANDS when neither the preset cache variables nor existing args define it, mirroring kit behavior.
• Changelog: Record the user-visible fix in the 1.23 bug fixes section.

The purpose of this change

Restore single-file compilation with presets by ensuring compile_commands.json is exported when presets do not opt in explicitly.

Other Notes/Information

const hasExportCompileCommands = Object.prototype.hasOwnProperty.call(presetCacheVariables, 'CMAKE_EXPORT_COMPILE_COMMANDS')
    || expandedArgs.some(arg => arg.startsWith('-DCMAKE_EXPORT_COMPILE_COMMANDS'));

if (!hasExportCompileCommands) {
    const exportCompileCommandsValue = util.cmakeify(exportCompileCommandsFile);
    expandedArgs.push(`-DCMAKE_EXPORT_COMPILE_COMMANDS:${exportCompileCommandsValue.type}=${exportCompileCommandsValue.value}`);
}

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• 2wrvsblobprodwus2180.vsblob.vsassets.io
  • Triggering command: /usr/local/bin/node node /usr/local/bin/yarn install (dns block)
• 40vvsblobprodwus2135.vsblob.vsassets.io
  • Triggering command: /usr/local/bin/node node /usr/local/bin/yarn install (dns block)
• b15vsblobprodwus2164.vsblob.vsassets.io
  • Triggering command: /usr/local/bin/node node /usr/local/bin/yarn install (dns block)
• b53vsblobprodwus2154.vsblob.vsassets.io
  • Triggering command: /usr/local/bin/node node /usr/local/bin/yarn install (dns block)
• d94vsblobprodwus2119.vsblob.vsassets.io
  • Triggering command: /usr/local/bin/node node /usr/local/bin/yarn install (dns block)
• k4pvsblobprodwus2140.vsblob.vsassets.io
  • Triggering command: /usr/local/bin/node node /usr/local/bin/yarn install (dns block)
• n6wvsblobprodwus2123.vsblob.vsassets.io
  • Triggering command: /usr/local/bin/node node /usr/local/bin/yarn install (dns block)
• p2tvsblobprodwus2189.vsblob.vsassets.io
  • Triggering command: /usr/local/bin/node node /usr/local/bin/yarn install (dns block)
• v41vsblobprodwus2175.vsblob.vsassets.io
  • Triggering command: /usr/local/bin/node node /usr/local/bin/yarn install (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[Bug] Unable to compile single file with cmake.compileFile command</issue_title>
<issue_description>### Brief Issue Summary

• open vscode, choose preset, configure cmake project
• set a keyboard shortcut to the command cmake extension command cmake.compileFile (in my case ctrl+F7).
• open a cpp file in that configured project
• press shortcut (here ctrl + F7)
  Expected: compiles single file
  Actual: Error popup with "Unable to find compilation information for this file"

CMake Tools Diagnostics

{
  "os": "win32",
  "vscodeVersion": "1.100.3",
  "cmtVersion": "1.20.53",
  "configurations": [
    {
      "folder": "d:\\workspace\\mdes1",
      "cmakeVersion": "4.0.2",
      "configured": true,
      "generator": "Ninja",
      "usesPresets": true,
      "compilers": {
        "C": "C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/cl.exe",
        "CXX": "C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/cl.exe"
      }
    }
  ],
  "cpptoolsIntegration": {
    "isReady": true,
    "hasCodeModel": true,
    "activeBuildType": "RelWithDebInfo",
    "buildTypesSeen": [
      "RelWithDebInfo"
    ],
    "requests": [],
    "responses": [],
    "partialMatches": [],
    "targetCount": 802,
    "executablesCount": 186,
    "librariesCount": 609,
    "targets": []
  },
  "settings": [
    {
      "communicationMode": "automatic",
      "useCMakePresets": "auto",
      "configureOnOpen": true
    }
  ]
}

Debug Log

[main] Saving open files before configure/build
[extension] [2016] cmake.compileFile finished (returned undefined)

Additional Information

No response</issue_description>

<agent_instructions>You are Copilot coding agent acting as a senior maintainer/contributor for the VS Code extension repository microsoft/vscode-cmake-tools.
You are deeply familiar with CMake, CMake Presets, CTest, kit/toolchain selection, VS Code extension APIs, and the architecture of this repo (TypeScript-heavy).
Your job is to resolve the GitHub issue provided below safely and in a maintainable way, matching existing patterns and UX.

SOURCE OF TRUTH

• Implement the requested change by reading and interpreting this issue (and its comments, linked issues/PRs, logs, and repro projects):
  [Bug] Unable to compile single file with cmake.compileFile command #4484 - Bug [Bug] Unable to compile single file with cmake.compileFile command #4484
• If the issue lacks repro steps, you must derive minimal repro steps from the information available and document them in the PR.

NON-NEGOTIABLE PROCESS

1. Triage & understanding (issue-first)

• Read the entire issue thread.
• Extract and write down:
  • expected behavior
  • actual behavior
  • repro steps (or minimal repro you infer)
  • affected OS/toolchains/generators/presets
  • whether it is a regression and from which version/commit (if indicated)
• Identify which CMake Tools feature area is involved (configure/build/test/debug, presets, kits, status bar, tasks, command palette, IntelliSense).

2. Orient yourself in the repo (implementation map)

• Identify the relevant user-facing workflows impacted (configure/build/test/debug, presets, kits, status bar, tasks, command palette).
• Locate the existing implementation areas (commands, configuration/presets handling, test integration, UI, telemetry/logging).
• Identify existing tests and how they are run in CI; prefer extending existing suites over inventing a new harness.

3. Changelog discipline (required)

• Find the project’s changelog / release notes mechanism (e.g., CHANGELOG.md, docs/changelog, “Unreleased” section, or a dedicated changes/ folder).
• Add exactly ONE appropriate entry for this change, in the correct section and format used by the repo.
• The entry must describe user-visible behavior (not internal refactors).
• If the change is not user-visible, explicitly justify that and still add a brief “Internal” entry if the repo’s convention supports it.
• Ensure the changelog entry matches wording/tense/category conventions already used by the repo.

4. Implementation standards

• Follow existing code style, naming, and patterns in this repository.
• Prefer small, readable changes; avoid broad refactors unless clearly necessary to fix the issue correctly.
• Preserve backward compatibility for settings/presets when possible; be careful with defaults and precedence rules.
• Update docs/settings schema/messages if user-facing behavior or configuration changes.
• Logging: use the extension’s existing logging utilities; avoid noisy output and avoid logging secrets/paths unnecessarily.

5. Testing:

• Create a unit test if possible AND practical to validate and test out fix, and ensure it is compatible with all platforms tested: Windows, Linux, and macOS. Ensure that it will not conflict with existing CI settings. If not possible to create a unit test, draft a manual plan for how t...

• Fixes [Bug] Unable to compile single file with cmake.compileFile command #4484

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.