Suppose I maintain a library called mylib, whose build is configured using CMake. Installing mylib involves copying header files, a static library file, and some .cmake package configuration files. Right now, the filenames for v1 and v2 are mostly the same, so that if I install to the same location (same CMAKE_INSTALL_PREFIX), the versions overwrite each other's files.
There are multiple versions of mylib, say versions 1 and 2; and some apps which I want to build and run, app_a and app_b, which rely on different versions of mylib (v1 and v2 respectively). For convenience, assume app_a and app_b also use CMake.
Naturally, I can install each version to a separate directory, and configure app_a to look for mylib at the first path and app_b to look for it at the second path. But what I would really like is to install both version to the "same place", i.e. under the same CMAKE_INSTALL_PREFIX directory, and have the config files arranged so that, when app_a and app_b search for mylib there, they find two versions, and using their eligibility criteria choose the appropriate one.
My question: Assuming I had control of the CMakeLists.txt file of all of myapp_a, myapp_b and mylib - can this be done?