From: Pedro Ferreira (pedro.ferreira_at_[hidden])
Date: 2003-12-18 05:30:10
> Another solution is to remove the fancy logic which eliminates some
> This will work for me, and simplify code. Also, this is also needed to fix
> the --clean option. It was requested that --clean does not remove targets
> other project, or at least in other project roots. Now it removes
> bjam sees and that's not nice. But to implement right semantic, all
> targets must be seen and processed by top-level code.
> So, this looks like an excellent approach, except for 'stage'.
> exe a : a.cpp ;
> stage dist : a ;
> If 'a' returns all targets, then 'stage' will start to copy response files
> what not. Is it a problem? I think it's not that nice, but OTOH it won't
> break anything. For real uses, it's easy to add <include-type> features to
> stage only EXES (after I commit recent Pedro's patch).
I intend to use <include-type> everywhere so it's not a problem to me.
However, I think it's not very elegant, and even with proper documentation
it may be confusing to the non-initiated...
An option would be to move the "fancy logic" to stage itself, but that would
be losing one chance to simplify the code.
As I said, I can live quite happily with your proposal.
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