On 30/05/2017 16:06, Vinnie Falco via Boost wrote:
On Tue, May 30, 2017 at 7:58 AM, Niall Douglas via Boost
wrote: - No cmake, just bjam
Wait, what? Why would we want to remove functionality that already exists? I like the CMake script since it generates a Visual Studio project file (.vcxproj). Please don't take this away, its helpful.
Standalone Outcome would remain cmake based. I have no love nor use case for bjam personally. (the bigger answer is that the cmake build support is entirely implemented by the boost-lite git submodule because it's a universal build system for a distributed collection of standards aspiring libraries. The CMakeLists in the Outcome root is just a set of parameters for that universal build system. As some people consider git submodules to be a showstopper, that makes impossible cmake build support in the Boost.Outcome script generated repo because the submodule with the cmake build support must be removed) Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/