On Sat, Dec 12, 2009 at 7:33 AM, Stefan Seefeld <seefeld@sympatico.ca> wrote:
I'm not sure what the best place is for this question, but since it is symptomatic for a general theme (which I have complained about a lot in the past), I'll write it here:
I'm trying to generate a boost subset that allows me to build boost.python and its dependencies into my own package. To do that, I ran "bcp python ...". I'm surprised to find all these components in the generated source tree:
date_time, graph, mpi, regex, serialization, test, thread.
And that's only compiled components (content of lib/). There are many more header-only components (i.e. subdirectories under boost/), such as spirit, variant, property_map, property_tree, dynamic_bitset.
Is this really a minimal subset to use boost.python ? I can't quite believe it. In particular, what is boost.mpi doing there, and what boost.serialization (and boost.spirit) ?
I'm going to great length to be able to use boost in a production environment, but I have to admit that this is quite unacceptable. :-(
Correct. Boost.Python includes a lot of things to properly convert from a large amount of Python types properly as well as for the type registry. I am actually surprised it does not include more...