29 Jul
2017
29 Jul
'17
2:30 p.m.
On 7/29/2017 5:02 AM, Peter Dimov via Boost wrote:
Louis Dionne wrote:
If we go Paul's way (which is IMHO the right way in the long term), ...
I've given it some thought and I like the BCM approach; BCM should be a library in libs/bcm (if we retain the name).
Perhaps a tool in tools/bcm ?
But I think that Paul's insistence to support the cget workflow, for which nobody at the moment cares but him, is making things more complicated and error-prone than they could be. (The cget workflow is the ability to build and install Boost libraries one by one, independently of one another, without a superproject; this requires them to refer to one another with find_package.)