microsoft / microsoft/vscode-cmake-tools
`cmake.configureSettings` should not take effect on the remote computer
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.7k
- Forks
- 546
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 32
Description
Brief Issue Summary
cmake.configureSettings in user settings.json will works on both local and remote. But this config may include path or something else which is related to specific computer.
For example, to use vcpkg, CMAKE_TOOLCHAIN_FILE have to be added into. But it will stop configuration on remote. Thus, we cannot guarantee that the remote has an out-of-the-box environment while guaranteeing the local. Unless the local configuration is overwritten on each remote computer.
Therefore, cmake.configureSettings should not take effect on the remote computer.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named in the issue. Start by locating where cmake.configureSettings is handled and how local versus remote sessions are distinguished; done means the setting remains effective locally but is ignored on the remote computer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, typescript
- Domain
- build-system, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100