Dub dependency error message confusing: says wrong compiler when it's a build type mismatch
Open
Nobody has claimed this yet.
dependencies
language:D
- Dominant language
- Python
- Stars
- 6.6k
- Forks
- 1.9k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 33
Description
An error message like this:
ERROR: wayland:client found but it wasn't compiled with ldc
can happen because e.g. we're building a debug project, but the library in dub was built only in release mode, i.e. _find_right_lib_path doesn't find the right entry in listdir because buildType is different, not because the compiler is different.
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 locating _find_right_lib_path and reproduce the lookup with a debug project and a release-only Dub library. Trace the error construction and update the message so a build-type mismatch is distinguished from a compiler mismatch; done means the reported cause matches the failed lookup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100