From: Roland Schwarz (roland.schwarz_at_[hidden])
Date: 2007-11-03 08:37:01
Deane Yang wrote:
> Try #2: Have two options:
> Option #1: Do the run but give warning messages when something cannot be
> Option #2: Stop the run and give an error message when something cannot
> be done
I just rewrote the thread Jamfile and it would have been easy to do #1.
The lib author simply needs to put <build>no into the requirements if
he finds, that a certain combination cannot be built.
Current policy however is (as I understand it) to provide the
default, which indeed may lead to surprise.
On the other hand it is no option to just stop the entire build request,
since it still might be possible that other unrelated parts compile
fine under the given requirements.
So I would suggest to give a User understandable "skipped message" and
continue with the build.
Roland aka speedsnail
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