Re: [boost] towards a library dependency list

From: Edward Diener (eddielee_at_[hidden])
Date: 2006-02-11 09:51:28

Hartmut Kaiser wrote:
>  
> John Maddock wrote:
> 
>>> It doesn't, not in its default configuration. Only quick_allocator 
>>> depends on type_traits.
>> Right, and this is one of the problems with robot-derived 
>> dependency lists: 
>> they pick up everything, even things that are rairly used 
>> (workarounds for old compilers etc).
> 
> Using Wave to extract the set of used include files (with a well defined set
> of predefined macros to select the required compiler) would help to overcome
> this issue, IMHO.

Also, the user should be able to add possible implementation-defined 
macros when running bcp under this scenario in order to eliminate parts 
of an implementation which he will never use from the final set.