On Tue, 2017-07-18 at 19:01 +0100, Roger Leigh via Boost-users wrote:
On 18/07/17 14:12, Jon Kalb via Boost-users wrote:
Therefore, we, the Steering Committee, announce to the Boost community our desire and intent to move Boost’s build system to CMake for users and developers alike.
This is great news to hear.
The members of the Steering Committee have been encouraged by the discussions and activity surrounding CMake on the mailing lists over the years and know that many people have voiced visions. We hope that each of you rejoins the discussion to support this initiative and contributes to the common goal of improving Boost’s integration into the broader C++ ecosystem.
I'm one of the maintainers of the CMake Boost support (https://gitlab.kitware.com/cmake/cmake/blob/master/Modules/FindBoost.cmake)
Currently we hardcode all the inter-module library and header dependency information back to Boost 1.33 so that it's possible to call
find_package(Boost COMPONENT filesystem thread)
and have it find the libraries and tell CMake what the dependencies are so it can compile and link with the correct includes and libraries.
With Boost using CMake itself, it would be nice if this information could be provided directly by Boost, so that the dependency information doesn't need to be hardcoded--it can be supplied directly with the build in the form of a ${libdir}/cmake/BoostConfig.cmake script. This would mean we could retire FindBoost.cmake and cease the hardcoding of dependency information for new releases from this point onward. We would need to keep it around for backward compatibility for some time, but users could switch over to the provided configuration pretty seamlessly.
Well, actually, an intial setup for cmake, I have it generate config files for every library here: https://github.com/boost-cmake/boost So then its just a matter of updating `FindBoost` to use these packages.