Re: Building with CMake?

From: Mateusz Loskot (mateusz_at_[hidden])
Date: 2019-10-08 16:28:31

On Tue, 8 Oct 2019 at 17:52, Robert Dailey <rcdailey.lists_at_[hidden]> wrote:
>
> On Tue, Oct 8, 2019 at 10:06 AM Mateusz Loskot via Boost-users
> <boost-users_at_[hidden]> wrote:
> >
> > On Tue, 8 Oct 2019 at 16:30, Robert Dailey via Boost-users
> > <boost-users_at_[hidden]> wrote:
> > >
> > > I see that individual repositories like boostorg/filesystem on Github
> > > have a CMakeLists.txt. But the boostorg/boost super repo doesn't have
> > > a root CMakeLists.txt. Either this doesn't follow standard CMake
> > > structure or there's no way to build with CMake globally instead of
> > > bjam.
> >
> > It is the latter.
>
> Why, then, do the individual libs have CMake support? What's the point
> if you can't build the complete boost library with it?

Boost is a collection of C++ libraries where each library has a fair bit of
freedom of how it is being developed; each has their developers and
maintainers who are free to add any build configuration they like as
local/internal per the library they maintain.

For example, Boost.Beast and Boost.GIL, both header-only libraries,
allow their contributors to build tests and examples using CMake.
So, CMake-lovers should follow instructions specific to those libraries:
https://github.com/boostorg/gil/blob/develop/CONTRIBUTING.md
https://github.com/boostorg/beast#building-tests-and-examples

If you search carefully, you may even find .sln and .vcxproj files
dangling in folders of some libraries. It does not mean you can build
whole Boost by opening the .sln file in VS and hitting Ctrl+Shift+B.

If there is a maintainer of a Boost library who likes Bazel or Premake,
you may see configuration files for those as well.

Best regards,
-- 
Mateusz Loskot, http://mateusz.loskot.net