microsoft / microsoft/vscode-cmake-tools
[FR] Support module map files
- Dominant language
- TypeScript
- Stars
- 1.7k
- Forks
- 546
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 32
Description
### Brief Issue Summary
Support exposing the contents of module maps created by CMake to LSP engines.
### CMake Tools Diagnostics
_No response_
### Debug Log
_No response_
### Additional Information
CMake creates module map files which holds module mapping of translation units to used module files on disk. This information should be exposed to LSP engines without user intervention as examplified [here](https://github.com/microsoft/vscode-cpptools/issues/6302#issuecomment-2182414789) @bobbrow mentioned that this part of the integration is the onus of CMakeTools, not CppTools.
Contributor guide
Research direction
The issue names no source files or tests. Start by reading how CMake generates module map files and how CMake Tools currently communicates with LSP engines. Done means module map contents are exposed to LSP engines without user intervention, with coverage for the integration behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, typescript
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100