Subject: Re: [boost] A retrospect on 'CMakeLists.txt' policy review
From: Louis Dionne (ldionne.2_at_[hidden])
Date: 2016-06-02 21:24:09
> On 3/06/2016 13:26, Louis Dionne wrote:
> > If I understand correctly, however, then I might be inflexible but
> having a
> > CMake file in the build/ directory is still a major annoyance, as it
> > the usual CMake workflow. The build/ directory is normally used for
> > and as such it contains no source files. This means that we can't put
> > in the .gitignore file, and that we can't simply delete the build/
> > to clean things up. That disturbs the usual CMake workflow, and I don't
> > this is acceptable.
> You can't use (libroot)/build as the cmake output directory anyway,
> since it includes source files (at least jamfiles, if nothing else) --
> and since cmake lacks the ability to clean its output, you have to
> delete the directory to do so.
I'm only considering Hana, which is a header-only library. So as Steven
there's no build/ directory by default. I make no claim whatsoever as to how
things should be done in the event of a library with more than headers.
-- View this message in context: http://boost.2283326.n4.nabble.com/A-retrospect-on-CMakeLists-txt-policy-review-tp4686696p4686746.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