microsoft / microsoft/vscode-cmake-tools
Implement STDIN support when running cmake or scripts
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.7k
- Forks
- 546
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 32
Description
### FetchContent with ssh key
Hi,
I'm using a the `FetchContent_Declare` to clone in some code. This code I access using ssh and git.
If I simply run `cmake CMakeLists.txt` the terminal will ask for my passphrase to download the content. But if I click build in VSCode there is nothing happening at the moment it should ask for the passphrase. It is just stuck forever.
### Platform and Versions
- **Operating System**: Kali Linux in WSL2
- **CMake Version**: 3.18.4
- **VSCode Version**: 1.57.1
- **CMake Tools Extension Version**: 1.7.3
- **Compiler/Toolchain**: x86_64-linux-gnu-gcc-10
Thanks!
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
Reproduce the VS Code build flow for a CMake project using FetchContent with an SSH-protected Git dependency, comparing it with a direct cmake invocation. Start by tracing how CMake Tools launches cmake or scripts and whether standard input is available; done means the SSH passphrase prompt can be received during the VS Code build rather than leaving it stuck.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, vscode
- Domain
- build-system, developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100