microsoft / microsoft/vscode-makefile-tools
Exclude objects and libraries from launch targets
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 242
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
When parsing a link command, sometimes is not obvious if the output is a binary, versus an object or a library. The extension is tracking some special linker switches and file extensions but this is not enough, so we include sometimes more launch targets than what can really be debugged or launched via this extension.
The only solution that ensures only the binaries are listed (regardless of any new compilers/linkers or switches) is a live query of output file attributes to include only executables.
Example: github.com/FidoProject/Fido.git (the dryrun output finds one object launch target)
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 with the link-command parsing and launch-target discovery entry points, using the dry-run output from FidoProject/Fido.git as the reproduction case. Confirm how object and library outputs are identified, then verify that only executable binaries remain listed as launch targets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- build-system, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100