No clear directions for integrating WIL into CMake projects
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 3k
- Forks
- 300
- Avg merge
- 19h 12m
- Merged PRs (30d)
- 1
Description
Generally speaking, CMake libraries that are intended for use elsewhere will install an exports file - usually in ${INSTALL_DIR}/cmake/<project>Config.cmake - in order to allow third party CMake projects to locate the library with find_package(<project>). WIL does not appear to provide this CMake configuration file, and so it is unclear how the user is expected to integrate it into other CMake projects, and means that CMake projects that would otherwise use find_package() to pull in their dependencies now need to provide custom logic for WIL.
Now, it appears to me that CMake is not strictly used to package the library itself, but rather to do the packaging and testing tasks. I think the library would be well served with an exported interface library target which we could then pull in much more easily.
Contributor guide
No contributing guide indexed for this repository
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
Inspect the repository's CMake packaging and testing setup first, focusing on how WIL is currently built and installed. Determine the exported interface target and package configuration needed for consumers; the work is done when an external CMake project can locate and use WIL through find_package().
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