Subject: [boost] The boost component dependencies blues
From: Stefan Seefeld (seefeld_at_[hidden])
Date: 2009-12-12 09:33:37
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. :-(
-- ...ich hab' noch einen Koffer in Berlin...
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk