[CMake] protozero targets
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cmake, cpp
- Domain
- build-system
Research direction
Review the repository's CMake files and the requested interface-target and installation behavior. Implement the protozero::protozero target and generated package configuration so consumers can use either add_subdirectory or find_package(protozero REQUIRED), then verify both usage paths.
Written by the indexing model from the issue text.
Description
Currently, the CMake files do not create a target for the protozero library itself.
CMake supports so called interface targets, which are targets which contain only header files but do not build anything.
So instead of making the includes available everywhere, an application that wants to use protozero can link against that target.
(The canonical way would be to call it protozero::protozero).
Would you accept a PR that makes the required changes?
It would then allow to use protozero as via add_subdirectory, or via find_package(protozero REQUIRED), but instead of manually providing a FindProtozero.cmake file, it would generate a protozere-config.cmake file upon install.
- Dominant language
- C++
- Stars
- 381
- Forks
- 82
- PR merge metrics
- No merged PRs in 30d
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.
More from mapbox/protozero
-
`basic_pbf_builder<TBuffer, T>` submessage constructor does not enforce correct parent tag type. Open
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 42/100
All issues in mapbox/protozero
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·