Hello Richard, There is a special tool for copy only subset of boost libraries called bcp. It is included in boost distribution in $(BOOST)/tools/bcp. I use it constantly and successfully in my project. bcp can copy only selected libraries from boost along with all dependecies. In my project I even have short python script to automatically build bcp and copy required libraries into project. Regards. RH> It is obvious that the Boost library collection is quite large and RH> growing, and it probably will never decrease. It takes a long time RH> to build the libraries that require building and to copy the headers RH> from one place to another. It would be really nice for me (and for RH> others, I suspect) to be able to request just the subset of RH> libraries that I use. I would like the developers to think of a RH> mechanism to break up the collection into subsets. RH> RH> Of course, there could be one subset that is common to all, and RH> there could be other subsets that are common to a group of RH> libraries. It would make sense to keep the number of subsets small RH> by placing libraries with similar functionality or dependencies into RH> a single subset. If you want to get fancy, you could include a RH> library in multiple subsets. RH> RH> Whatever makes sense should be fine with most users. I just ask you RH> to consider the desirability of restructuring the distributions. RH> RH> _______________________________________________ RH> Unsubscribe & other changes: RH> http://lists.boost.org/mailman/listinfo.cgi/boost -- Vyacheslav E. Andrejev System Architect, Excelsior, LLC