Re: [boost] Request for a "Policy Review" regarding 'CMakeLists.txt'

Subject: Re: [boost] Request for a "Policy Review" regarding 'CMakeLists.txt'
From: Thijs van den Berg (thijs_at_[hidden])
Date: 2016-05-17 10:51:36

On 17 May 2016 at 16:37, Vladimir Prus <vladimir.prus_at_[hidden]> wrote:

> On 17/05/2016 17:11, Thijs van den Berg wrote:
>
> May I ask how often do you edit Jamfiles? It do it somewhat often, and I
>>> do find having them in subdirectory to be a burden.
>>>
>>> My point is that you can keep doing so.. your Jamefiles editing will not
>>>
>> be affected if a CMakeLists.txt  get's added to the root.
>>
>
> Looks like you did not answer this question directly, and accepted my
> statement
> that having build files under 'build' is a burden. Therefore, I assume
> you'll
> have no objections to moving all Jamfiles to root level of their
> corresponding
> components, should guidelines be modified to allow that?
>
>
> That would cause confusion with developers who are accustomed to the
current setup, I don't know of any gain people get from that would
outweights the inflicted confusion by such a change. Having the
CMakeLists.txt  at the root instead of somewhere else *does* have a gain:
it's sticking to conventions that CMake users are accustomed to.

Any bjam conventions discussion, validation historical choices etc is a
separate discussion. This discussion here is if we should pave the way to
facilitate CMake users and do so correctly by sticking to accepted
conventions, and add the CMakeLists.txt to the root or not.