From: David Abrahams (dave_at_[hidden])
Date: 2006-03-25 21:02:14
Rene Rivera <grafik.list_at_[hidden]> writes:
> I'm porting over my build system from BBv1 to BBv2, and to be nice, I'm
> trying to not hack things up too much. One of the patterns I'm seeing is
> that in writing library targets I end up duplicating many of the
> requirements into the usage-requirements.
> * That seems like a waste of typing resources :-)
> * It's prone to errors when I need to change one of them and forget to
> change the other.
> If it's not already possible to remove that duplication my suggestion
> would be to:
> 1. Allow both kinds of requirements in the requirements section.
> 2. To tag requirements that are both regular requirements and
> usage-requirements with <*>.
> For example:
> lib foo
I like the general idea, but not the syntax. It's too much like a
syntax that meant something completely different in BBv1.
-- Dave Abrahams Boost Consulting www.boost-consulting.com
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