Re: [boost] bcp update, was: The boost component dependencies blues

Subject: Re: [boost] bcp update, was: The boost component dependencies blues
From: John Maddock (john_at_[hidden])
Date: 2009-12-16 13:32:18

>> Can you tell me specifically which headers you're #including so I can
>> investigate here?
>
> I believe the entire Boost.Python API is accessible through
> boost/python.hpp, so this is what I'm including. (I expect that if there
> are Boost.Python headers which are not included in the boost/python.hpp
> 'hub', it's probably an oversight. I may still need them, at some point.

OK, there's an update in Boost.Trunk to bcp so that it only considers 
library source files to be a dependency if a header declares something 
that's defined in the source.

As a result using bcp on python.hpp pulls in a lot less.... but:

Serialization still gets pulled in - you may know that you're not using that 
particular feature, but as it's #included by the python source you're going 
to get it anyway.
MPI still gets pulled in - this is an artifact of some recent changes to 
boost.graph (which is used by python) to optionally make use of the parallel 
graph lib depending upon some #define.  You may know that you're not using 
this feature, but you *might* be, so it gets pulled in.

HTH, John.