microsoft / microsoft/vscode-cmake-tools
resolve symbolic links after kit detection
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
All kits are detected under `/bin` which is a symbolic link to `/usr/bin`
### Expected:
Symbolic links to kits get resolved to their absolute path.
### Apparent Behavior:
Selecting clang (or gcc) located at `/bin/clang++` for example ends up in having dependencies to `/bin/../include` which resolves to `/include` in ninja configuration. Therefore ninja thinks everything needs to be rebuild cause `/include` is not existing.
Manually setting the compiler to be under `/usr/bin` solves this.
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
No file or test is named. Start by tracing kit detection and the handling of compiler paths for clang++ or gcc, then reproduce the `/bin` versus `/usr/bin` case with Ninja. Done means a kit selected through `/bin` uses its resolved absolute path and no longer produces the invalid `/include` dependency path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, typescript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100