From: Emil Dotchevski (emildotchevski_at_[hidden])
Date: 2006-03-25 22:20:05
I second this message.
Though I have no experience with v1, I also often find myself having to
duplicate requirements and usage requirements, and this I agree is prone to
However, I think the concepts are different and should be kept separated; I
think that the ideal solution would be if there was a way to write my own
wrapper which duplicates them for me, however I don't know jam or bjam well
enough to write this or even to tell whether it's possible or not... :|
----- Original Message -----
From: "Rene Rivera" <grafik.list_at_[hidden]>
To: "Boost.Build developer's and user's list" <boost-build_at_[hidden]>
Sent: Saturday, March 25, 2006 12:44 PM
Subject: [Boost-build] [bbv2] RFC: Repeated usage requirements.
> 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
> -- 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
> Unsubscribe & other changes:
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