What is the intended use case of the
cmake --install command line option (or the older install target)?
I am wondering because it seems extremely cumbersome and hard to customize compared to CPack. The documentation states:
CMake provides a command-line signature to install an already-generated project binary tree
I interpreted this to mean: Installing a project or library, from the command line, for power users/developers. So that without needed a package I can simply clone, build, and install a program/library.
If this is close to the intended use case, it seems like I should be able to operate on the
COMPONENTS property as a variable and in similar ways as I can within CPack with
I love the ability to have hierarchical projects in CMake, with many layers of depth. But now that I am trying to make a top level library/project installable all those libraries are adding components to my top level install ALL command. CPack allows me to filter and group the components (I am assuming all install commands create nice component names), but
cmake --install becomes almost useless (IMO).