On Tue, Apr 23, 2019 at 12:41 PM Peter Dimov wrote:
Brad King (from Kitware, who should know) argues that installing separate configuration files for all the libraries is wrong. He says that the preferred practice is to only support the second use, with Boost as the package, and the libraries as components, not accessible as packages on their own. (The discussion is here: https://gitlab.kitware.com/cmake/cmake/issues/19186) [...] I'm having second thoughts though. It looks to me that Brad is right, and that the various library configuration files should be implementation details of a single Boost package (in the CMake sense) and not be user-visible. That is, only support
find_package(Boost COMPONENTS filesystem)
and drop
find_package(boost_filesystem)
I'm in favor of this.
the various library configuration files should be implementation details of a single Boost package
Do they need to live in the library, or is more idiomatic for these too to reside within (and be maintained as part of) a separate sub-module repository that also houses the one CMakeLists.txt? Glen