Use `CMAKE_PREFIX_PATH` in addition to individual `<dep>_DIR`
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 27
- Forks
- 11
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 23
Description
Summary
Make use of CMAKE_PREFIX_PATH for all dependency paths.
Rationale
CMAKE_PREFIX_PATH provides a standardized centralized list of dependency paths for CMake's built-in find_* tools. It's also nice for users who are used to the convention to use this variable instead of worrying about which other variables to specify.
Description
Any path variables used for dependency finding should be appended to this list and this should be the default used for "finding".
Additional information
See https://cmake.org/cmake/help/v3.22/variable/CMAKE_PREFIX_PATH.html
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 the CMake dependency-finding logic and the individual _DIR path variables. Read the CMAKE_PREFIX_PATH documentation linked in the issue, then trace each dependency lookup to determine where paths are assembled. Done means all dependency paths participate in CMAKE_PREFIX_PATH while the existing individual variables remain supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100