You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While reading about best practices concerning CMake I've come across an article talking about package information. Since I'm deep down in the source code I realised that it was not there. I'm suggesting that maybe we could add this missing part in the project.
I believe that this is of limited use for CppMicroServices. C++ libraries and their development files are typically built manually by their users (configure && make or vcpkg) or uploaded to a central OS specific packaging system (rpm or deb packages). For the latter, we would need a mentor anyway.
Do you have a need for something else, like a zip or tgz package of the binary artifacts?
Well this was for my quest to understand C++ and CMake. Personally I don't need anything specific, I just tought that this was a relevant point but if it is not necessary I believe your opinion has more weight and I would trust it.
While reading about best practices concerning CMake I've come across an article talking about package information. Since I'm deep down in the source code I realised that it was not there. I'm suggesting that maybe we could add this missing part in the project.
Article link: https://cliutils.gitlab.io/modern-cmake/chapters/install/packaging.html
The text was updated successfully, but these errors were encountered: