crickets.... crickets... crickets... That's the response I get from the internet?
Here are some other interesting bits: https://cmake.org/cmake/help/v3.8/manual/cmake-packages.7.html Does not make any reference to configure_package_config_file in https://cmake.org/cmake/help/v3.8/module/CMakePackageConfigHelpers.html But happily goes about telling pkg maintainers to go about and do with config_file what doc on configure_package_config_file says not to do... and that is NOT to use configure_file in the first place at: https://cmake.org/cmake/help/v3.8/manual/cmake-packages.7.html#id16 And then there is INSTALL_DESTINATION in: configure_package_config_file(<input> <output> INSTALL_DESTINATION <path> which gives the pkg maintainer just enough rope to hang themselves with. I mean hey they could (and have) put it just about anywhere like ${CMAKE_INSTALL_PREFIX}/CMake or ${CMAKE_INSTALL_PREFIX}/lib/cmake or ${CMAKE_INSTALL_PREFIX}/lib/cmake/pkgname or ${CMAKE_INSTALL_PREFIX}/lib/cmake/pkgname-<version> or ${CMAKE_INSTALL_PREFIX}/share/pkgname or ${CMAKE_INSTALL_PREFIX}/share/cmake/pkgname or ... well you get the idea. With or without version info. Where IMO configure_package_config_file should require version info and put in "standard directory" whatever that may be. Please someone in internet land tell me I am wrong. I'll await the crickets.
-- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
