microsoft / microsoft/vscode-makefile-tools
Problem matchers and relative paths
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 242
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
We need to write a new problem matcher based on msCompile which can handle relative path.
Also, even if gcc handles relative and absolute paths already, make -f or -C moves the base of the build somewhere else than ${workspaceFolder} and we actually need a new problem matcher based on gcc, that would read from a variable that the extension sets when detecting -f or -C.
Also, if a make invokes other make in various different folders, think if we can have a smart problem matcher that would always recognize the base folder for relative path analysis. Most probable we cannot support this scenario.
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 inspecting the extension's problem matcher handling and the variable set when detecting make -f or -C. The issue names no files or tests, and its proposed support for nested makes is unresolved. Done would require a defined scope and a matcher that resolves supported relative paths from the correct build directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- build-system, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100