microsoft / microsoft/vscode-cmake-tools

Option to disable !2987

Open
#3,213 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature: build Feature: debug/launch
Dominant language
TypeScript
Stars
1.7k
Forks
546
Avg merge
2d 16h
Merged PRs (30d)
32

Description

### Brief Issue Summary

[!2987](https://github.com/microsoft/vscode-cmake-tools/pull/2987) builds both the build target and the executable when pressing the run button. In my case, this is a breaking change for the extension.

I am using the setup for unittests. The build target most of the times is the coverage target, that builds and runs all tests and creates a coverage report. When I am developing a unittests, I select it as the executable. When I am now pressing the run button, it first runs the coverage target, which takes some time, before running the executable. I would have to select the executable as build target aswell and switch back to the coverage target if needed. This would mean many unnessecary steps, which were not required before this PR.

Is there any way to disable this new feature?

### CMake Tools Diagnostics

_No response_

### Debug Log

_No response_

### Additional Information

_No response_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing pull request !2987 and the run-button flow that now builds both the selected build target and executable. Trace how build and executable selections are handled, then identify the existing configuration path for an opt-out. Done means users can disable the new behavior and run the selected executable without the extra build-target step.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
build-system, developer-experience, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.