Or rather `boost_xyz-config.cmake` for each Boost.Xyz. The reason for this is:
* The `-config.cmake` is case-insensitive * it matches the library name(ie find_package(boost_system) and find_library(LIB boost_system)) * It follows the boost guildelines to have all files be lowercase
Sure, anything's fine by me. As long as we settle on something that's blessed by CMake experts (e.g. Stephen Kelly and Daniel Pfeifer), I'm on board.
Although I am not following the proposal. Are you suggesting that the Boost.Build generate these files? Or that we move to cmake to build and test, and we require the libraries to install the config files?
I intentionally left it unspecified how these files would be generated and installed. All that I care (in the scope of this sub-proposal) is that they are installed when Boost is installed, so that I can use the targets from CMake without jumping through hoops or relying on the incomplete FindBoost package provided with CMake. -- View this message in context: http://boost.2283326.n4.nabble.com/Proposal-for-moving-Boost-to-CMake-tp4695... Sent from the Boost - Dev mailing list archive at Nabble.com.