From: Rene Rivera (grafik.list_at_[hidden])
Date: 2006-03-25 15:44:56
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 <*>.
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
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