14 Apr
2016
14 Apr
'16
12:53 a.m.
On Apr 13, 2016, at 7:04 PM, Peter Dimov
wrote: P F wrote:
What I mean by dependency is what is needed to fully build, test, and install the library. I think that is pretty straightforward.
While straightforward, that's not going to be very useful. Any library that uses Boost.Test for its unit tests will bring in all 39 of Test's dependencies. Given that most people are probably not intending to run the tests…
Yes, the test dependencies should only be brought in when the user wants to run the tests as well, which I don’t think is something unreasonable that the user would want to do.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost