Robert Ramey wrote:
I like these reports and find them interesting. But one thing would make them much more useful to me. Consider the following scenario:
I have a small app which uses the date_time library. I would like to know what boost modules I need to include. I look on your charts, and see that date-time has a primary dependency on the serialization library. This suggests that I need to include the serialization library in my small app to make it work - which is actually untrue. Now what useful information has your report given me?
The problem of is that my small app includes only those headers from date-time that it actually needs. So a useful dependency report would only follow those headers. So.....
Could I ask for a feature enhancement for these tools (assuming they don't already have it). Could I list a set of source files which would constitute the "root" of the the dependency search.
I've added a --subset-for option to boostdep; you can't give it a list of sources, but you give it a directory containing them, so dist\bin\boostdep --subset-for d:\my_projects\my_app will give you the Boost subset included by the files in d:\my_projects\my_app.