So does anyone have any feedback on this setup? If you had ideas, or would like to help update boost libraries, contributions are welcome.
Given the other reply to this describing their boost cmake design, I guess I'd better mention boost-lite's: * 100% cmake3 based (and uses "modern cmake" throughout) with no other tooling needed * Autodiscovers any library with the boost directory layout * Autodiscovers any tests you have and sets them up with ctest * Provides out of the box CI ctest scripting which uploads results to a CDash for your project and updates your github website with the output from doxygen * Automatically uses C++ Modules and precompiled headers where available * Automatically configures clang-tidy, asan, tsan, msan and ubsan sanitiser targets * Automatically matches git SHA in dependent git subrepos in flat dependency configurations * Automatically merges any develop commit passing all tests on all platforms according to CDash into master branch * Automatically packages up your library and publishes it to tarball, vcpkg (with ubuntu launchpad and homebrew in progress right now) * Libraries based on this are 100% standalone, when you clone the git repo or unpack the tarball you are 100% ready to go. Nothing else needed, not even configure and build. No arcane command line programs to run. * 99% compatible with VS2017's new cmake project support (I have some bugs to file with them). It's very close to working perfectly. I wouldn't recommend that anyone else use it yet. It is very much a work in progress, but all the above is working, and you can see it in action in proposed Boost.Outcome. It also has nil documentation. Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/