Subject: Re: [Boost-build] Interface for configuration framework
From: Vladimir Prus (vladimir_at_[hidden])
Date: 2010-03-17 15:42:03
Johan Nilsson wrote:
> "Vladimir Prus" <ghost_at_[hidden]> skrev i meddelandet news:201003171203.13626.ghost_at_cs.msu.su...
>> now that we've more or less decided how named parameters should look, then
>> next question is how the interface for configuration framework should work.
>> To remind, the goal is to perform various checks of environment, and
>> decide what should be built and how based on that -- and, importantly,
>> have a simple and consistent interface for that.
>> Here's how a zeroeth approximation look like:
>> exe long_double_check : has_long_long.cpp ;
>> lib boost_math_tr1l : ...sources... :
>> [ check-target-builds long_double_check : : <build>no ] ;
> I'll defer answering to the remainder of the post for the moment, but would like to answer a quick
> Would it be possible to build and execute e.g. a unit-test target to determine whether the
> meta-target should be built or not?
The current implementation totally does not care about type of target passed
to 'check-target-builds' -- and yes, I think it's good not to require specific
kind of targets -- even if that will mean less accurate diagnostics.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk