Hi, Is the way to extract one specific library ( smart_ptr in my case) from complete BOOST source tree? I need to use only smart_pointers, but undirtunately keeping a full BOOSt treen is too heavy for my CVS server. Are boost libraries heavy interrelated each with another? Regards Stas
Stas Khirman wrote:
Hi,
Is the way to extract one specific library ( smart_ptr in my case) from complete BOOST source tree? I need to use only smart_pointers, but undirtunately keeping a full BOOSt treen is too heavy for my CVS server. Are boost libraries heavy interrelated each with another?
You can not download a single library. You can use CVS access to get whatever directories you like. Once you download a release you can use the bcp tool to just grab a single library and all of its dependencies from the tree and move it someplace place else.
Is the way to extract one specific library ( smart_ptr in my case) from complete BOOST source tree? I need to use only smart_pointers, but undirtunately keeping a full BOOSt treen is too heavy for my CVS server. Are boost libraries heavy interrelated each with another?
Yes, but you can use the bcp tool to extract the subset you want, see http://www.boost.org/tools/bcp/bcp.html If you search the mailing list archives there is a discussion somewhere about why the subset used by shared_ptr is as large as it seems to be (it can be surprising until you realise what's going on). John.
John Maddock wrote:
If you search the mailing list archives there is a discussion somewhere about why the subset used by shared_ptr is as large as it seems to be (it can be surprising until you realise what's going on).
It really shouldn't be. I've made a conscious effort to reduce shared_ptr (and bind) dependencies as much as possible. shared_ptr should even compile with an empty boost/config.hpp on a conforming compiler. But unfortunately the dependencies still manage to get their way back into the code, somehow.
participants (4)
-
Edward Diener -
John Maddock -
Peter Dimov -
Stas Khirman