microsoft / microsoft/vscode-cmake-tools
[feature request] Support for module systems (to work with remote extension)
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
There is already a closed issue with the same request #526, however the solution is not applicable when using cmake tools with the remote extension. The solution was to load a proper environment before starting vscode (which will inherit the environment).
Feel free to close this issue in favor of #526.
With the ssh remote extension, the `cmake` command will always be executed on the default (login) environment.
### Expected:
A possible implementation is suggested in #526.
### Hacky workaround
For now we workaround this issue by pointing cmake tools to a wrapper script which loads the desired environment before calling the actual cmake binary.
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
Start by comparing this request with closed issue #526 and examining how CMake Tools invokes `cmake` through the VS Code SSH remote extension. Reproduce the default login-environment behavior and define done as allowing the command to load the desired module environment without requiring a wrapper script.
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
- 25/100