Boost logo

Boost :

Subject: Re: [boost] [CMake] what to do now?
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2016-04-14 17:17:47

On 2016-04-14 22:00, Edward Diener wrote:
> On 4/14/2016 1:37 PM, Rene Rivera wrote:
>> On Thu, Apr 14, 2016 at 12:33 PM, Louis Dionne <ldionne.2_at_[hidden]>
>> wrote:
>>> Don't overthink it. All I'm saying is that the Boost guidelines
>>> recommend
>>> that
>>> CMakeLists.txt should appear in $some_library/build/CMakeLists.txt,
>>> while I
>>> argue that current practice is to put it in
>>> $some_library/CMakeLists.txt.
>> Just to be clear. It's not a recommendation. It's a requirement.
> Ideally could not one have a CMakeLists.txt file wherever there is
> currently a jamfile ? In the library's 'build' directory to build a
> non-header only library, in the library's 'doc' directory to build the
> docs, in the library's 'test' directory to run the tests etc.

Yes, that is possible and what should be done according to the current
guidelines. It's just not how it's typically done in other projects that
use cmake.

> My personal problem with CMake is, while the language to use it is more
> understandable for me than 'jam', its doc is just as hard for me to
> understand as Boost Build if not even harder <g>. Mastering yet another
> build system which is documented mainly for those who already know what
> it is about is not my idea of programming fun.

Unlike Boost.Build, cmake has built in commands 'cmake --help*' which at
least make it easier to use when you know what you're doing.

Boost list run by bdawes at, gregod at, cpdaniel at, john at