On 10/18/2013 12:14 AM, Philip Bennefall wrote:
Thanks, Jens. What you say makes sense. I guess my next question would become, is it perhaps possible to extend bcp to be a little more selective? Since Boost already has a preprocessor implementation, maybe this could be used to follow some macro paths to determine what needs to be included? The user would naturally have to specify some macros that bcp could work with, but this seems to me to be an effective way of making bcp a little more picky when generating its output depending on the user's needs.
Another, perhaps less realistic option, would be if bcp could actually analyze what parts of a certain library the user's code calls upon. For instance, if I never use a smart pointer for a given container we would not need that dependency. This, I realize, is far more involved and might not be at all practical to implement. I'm just throwing the suggestion out there for some discussion.
Hello, I've already done some analysis work on the dependency graph over the last week. See the thread I've just started. I did trace the #include dependencies between repos. Thanks, Steve.