Subject: Re: [boost] [EXTERNAL] Request for a "Policy Review" regarding'CMakeLists.txt'
From: Rob Stewart (rstewart_at_[hidden])
Date: 2016-05-20 04:47:40
On May 19, 2016 11:33:25 PM EDT, Peter Dimov <lists_at_[hidden]> wrote:
>Rob Stewart wrote:
>> cget could take the subdirectory as an argument and use it after
>> untarring, etc.
>No, because of its automatic dependency retrieval. Packages need to
>follow an uniform convention.
>Although it could in principle look into $DIR/cmake/ if it doesn't find
>build/ is, however, totally nonstandard for CMakeLists.txt, so it
>make sense for a generic tool to look there. There are libraries that
>their CMakeLists.txt in cmake/, but I don't think that any have it in
>build/, as this seems to be the build directory by CMake convention.
Why can't the tool take an argument that says "also look in this other directory when looking for the 'top-level' CMakeLists.txt"?
(Sent from my portable computation engine)
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk