Peter Dimov-2 wrote
and see what tends to predominate - it's the same few libraries over and over. This is not a general problem.
I agree. That is I see it as mostly as problem specific to the serialization library as an optional component that other libraries provide access to. Our dependency concept (and our headers) don't really capture the "optional" aspect to this. In any case, I think a solution more or less specific to the serialization library would suffice. Of course I don't want something overly disruptive since I'm the one who has to deal with it. Also I don't want something overly general that everyone has to deal with even though the shouldn't have to. Robert Ramey -- View this message in context: http://boost.2283326.n4.nabble.com/To-split-or-not-to-split-or-something-els... Sent from the Boost - Dev mailing list archive at Nabble.com.