From: Rene Rivera (grafik666_at_[hidden])
Date: 2002-04-08 13:23:00
On 2002-04-08 at 09:59 PM, ghost_at_[hidden] (Vladimir Prus) wrote:
>Rene Rivera wrote:
>> >> project (and from project root, maybe?)
>> >> 2. I believe (and I think we've talked about it some time ago), that
>> >> propagation of requirement should be supported. E.g. -- a using
>> ><lib>boost in
>> >> sources will automatically add boost includes.
>> No. Doing that generically would be a problem for me. If we make that the
>> default behaviour I would need a way to prevent those and other kinds of
>> properties from propagating to other targets. It might not be evident to
>> Boost compiling, after all Boost does the sensible thing of having a
>> separate include directory. But I make use of other packages which aren't
>> that sensible. I have to deal with some projects which have different
>> settings, and includes for when building the lib, than when using the
>I case that wasn't evident from my post, I don't mean that requirements
>propagation should be default behavour. It should be some special kind of
>lib my_lib : ...........
> : <export_include>.....
>Since, for ill-behaving libraries, you're likely to write Jamfiles
>it will be possible to decide is exporting include is needed or not.
It wasn't evident from your post :-) Yes it makes sense to me that exporting
things like that is the way to go. Also since it's an orthogonal aspect this
might be better syntax:
lib my_lib : ...
-- grafik - Don't Assume Anything
-- rrivera_at_[hidden] - grafik_at_[hidden]
-- 102708583_at_icq - Grafik666_at_AIM - Grafik_at_[hidden]
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