If Better Enums would provide a CMake Package, it would be much easier to use by clients.
Don't get me wrong: Copy & Pasting one header file isn't hard, but it is against the Don't Repeat Yourself Principle (DRYP). Currently I implemented a custom (old-style) FindBetterEnums.cmakeCMake Find Module, but that is also a poor man's solution.
I think it would be much cleaner to provide a CMake package together with a proper CMake Installation.
I could provide a clean and modern CMakeLists.txt file for the project via a PR if it is desired (I have a bit of experience with CMake). @rcdailey already provided one, but it haven't been included in the master?
If this issue isn't rejected I would install Better Enum in a way, that #includes would look like the following (see #11):
In issue #24 this has been already discussed.
If Better Enums would provide a CMake Package, it would be much easier to use by clients.
Don't get me wrong: Copy & Pasting one header file isn't hard, but it is against the Don't Repeat Yourself Principle (DRYP). Currently I implemented a custom (old-style)
FindBetterEnums.cmake
CMake Find Module, but that is also a poor man's solution.I think it would be much cleaner to provide a CMake package together with a proper CMake Installation.
I could provide a clean and modern
CMakeLists.txt
file for the project via a PR if it is desired (I have a bit of experience with CMake). @rcdailey already provided one, but it haven't been included in themaster
?If this issue isn't rejected I would install Better Enum in a way, that
#includes
would look like the following (see #11):IMO that would be a little clearer.