microsoft / microsoft/vscode-cmake-tools

why vs code build cmake project output Directory auto add auto ${buildType}

Open
#3,962 3 comments 0 reactions 0 assignees View on GitHub
bug Feature: build Feature: settings Feature: UI question
Dominant language
TypeScript
Stars
1.7k
Forks
546
Avg merge
2d 16h
Merged PRs (30d)
32

Description

### Brief Issue Summary

setting.json
`{
"security.workspace.trust.untrustedFiles": "open",
"cmake.configureOnOpen": true,
"cmake.showOptionsMovedNotification": false,
"explorer.confirmPasteNative": false,
"explorer.confirmDelete": false,
"cmake.pinnedCommands": [
"cmake.build"
],
"fittencode.languagePreference.displayPreference": "zh-cn",
"fittencode.languagePreference.commentPreference": "zh-cn",
"editor.largeFileOptimizations": false,
"cmake.buildDirectory": "${workspaceFolder}/out/${buildType}",
"cmake.useCMakePresets": "never",
"cmake.allowCommentsInPresetsFile": true,
"cmake.allowUnsupportedPresetsVersions": true,
"cmake.automaticReconfigure": false,
"cmake.configureOnEdit": false
}`

output.log
`[build] Auto build dll exports
[build] Automatic MOC and UIC for target image_send
[build] rpc_client.vcxproj -> ..\out\Debug\ui\bin\Debug\rpc_client.dll`

output path: "..\out\Debug\ui\bin\Debug\rpc_client.dll"
how to change output path "..\out\Debug\ui\bin\rpc_client.dll" ?

### CMake Tools Diagnostics

_No response_

### Debug Log

_No response_

### Additional Information

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with the reported settings.json, especially cmake.buildDirectory, and compare it with the output.log path for rpc_client.dll. Trace how the CMake Tools configuration produces the duplicated Debug directory, then verify that the generated output ends at ..\out\Debug\ui\bin\rpc_client.dll.

Written by the indexing model from the issue text.

Assessment

Tech stack
cmake, vscode
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.