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.
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 aFindProtozero.cmakefile, it would generate aprotozere-config.cmakefile upon install.