microsoft / microsoft/vscode-makefile-tools
Support special syntax for compilation and launch
Open
Nobody has claimed this yet.
enhancement
Feature: accuracy
Feature: Parsers
- Dominant language
- TypeScript
- Stars
- 242
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
Will split later into more items if needed. Dumping all here for now.
Compilation
- cl.exe: /DMyDefine1=Val1,MyDefine2=Val2
- wrappers (cl.cmd)
- cl, lib and link: @file.rsp (response files)
- account for unusual or very old source file extensions (.c++, .C). hpp?
- conflicts analysis for switches that impact IntelliSense: /TC with /TP, /D and /U
Launch
- binary target invoked via "cmd -c", "start cmd", "source", "bash", conditioned by "@if (not) exist" ... etc ...
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 separating the compilation requirements from the launch requirements in this issue, then inspect the extension's handling of cl.exe, cl.cmd, response files, source extensions, and launch commands such as bash and cmd. Define smaller issues with specific entry points and tests; done should mean each selected syntax case is handled and its IntelliSense or launch behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, cpp, typescript, vscode
- Domain
- build-system, developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 22/100