Subject: Re: [boost] A retrospect on 'CMakeLists.txt' policy review
From: Louis Dionne (ldionne.2_at_[hidden])
Date: 2016-06-02 21:19:54
Steven Watanabe <watanabesj <at> gmail.com> writes:
> On 06/02/2016 07:26 PM, Louis Dionne 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.
I understand that, and would conform if Hana had something to build.
> For header-only libraries, like hana, it's not needed
> and should not exist, making this point moot.
> I just looked at your top-level CMakeLists.txt and it
> seems like it should be acceptable even by the strictest
> possible reading of the requirements. It definitely
> does not belong in build/.
Yay! Then all is fine as far as I'm concerned.
-- View this message in context: http://boost.2283326.n4.nabble.com/A-retrospect-on-CMakeLists-txt-policy-review-tp4686696p4686745.html Sent from the Boost - Dev mailing list archive at Nabble.com.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk