Boost logo

Boost :

Subject: Re: [boost] Request for a "Policy Review" regarding 'CMakeLists.txt'
From: Raffi Enficiaud (raffi.enficiaud_at_[hidden])
Date: 2016-05-17 17:07:11

Le 17/05/16 à 20:08, Andrey Semashev a écrit :
> On Tuesday, 17 May 2016 21:08:01 MSK Paul Fultz II wrote:
>> On Tuesday, May 17, 2016 at 11:33:38 AM UTC-5, Rene Rivera wrote:
>>> On Tue, May 17, 2016 at 11:29 AM, Paul Fultz II <pfu..._at_[hidden]
>>> <javascript:>> wrote:
>>>> Cmake doesn't impose a layout, and that's the whole point. I clone hana
>>> and
>>>> then call `cmake hana` to build it using cmake. Imposing a layout such
>>> as
>>>> hiding it in some unknown directory just causes confusion.
>>> As a not-cmake-user I don't know what you mean there. What commands do you
>>> invoke, precisely?
>> Something like this:
>> git clone git_at_[hidden]:boostorg/hana.git
>> mkdir build && cd build
>> cmake ../hana/
> And why is it a problem to type this instead:
> cmake ../hana/build
> ?


The nice thing on eg. GitHub is that it interprets and shows the
README.txt/ Library users not having a single clue on how to
build eg. Hana can quickly look at the GitHub page on the front, read
the fist lines of documentation/intro, and compile eg. Hana.

BTW, is there any policy about having a Markdown instead of a
"pure" text file at the root of the library? I transformed (amount of
work close to 0) the README.txt to for boost.test.


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