Re: [boost] A retrospect on 'CMakeLists.txt' policy review

Subject: Re: [boost] A retrospect on 'CMakeLists.txt' policy review
From: David Sankel (camior_at_[hidden])
Date: 2016-06-03 12:09:23

On Fri, Jun 3, 2016 at 9:31 AM, Rene Rivera <grafikrobot_at_[hidden]> wrote:

> On Fri, Jun 3, 2016 at 10:21 AM, Paul Fultz II <pfultz2_at_[hidden]> wrote:
>
> >
> > > On Jun 2, 2016, at 8:50 PM, Steven Watanabe <watanabesj_at_[hidden]>
> > wrote:
> > >
> > >  All of these arguments depend solely on the
> > > existence of build/, regardless of whether
> > > it contains a CMakeLists.txt or not.  For separately
> > > compiled libraries, build/ *must* exist because
> > > that's the layout that we've chosen for Boost.Build.
> >
> > Thats the layout for Boost.Build, but what about cmake?
>
>
> It's not a Boost Build layout.. It's a "Boost C++ Libraries" layout. It's
> what the community of library authors decided as a directory layout for
> libraries. We are free to change it after discussions, consensus, etc. But
> probably not a discussion for this thread ;-)

Yes, lets not go there.