17 Sep
2014
17 Sep
'14
5:19 p.m.
Robert Ramey wrote:
The definition of "module dependency" is unclear to me.
The definition of module dependency that the report uses is: module X depends on module Y if some header of X's includes some header of Y's where "some header of X's" refers to the headers in libs/X/include. That is, it doesn't track dependencies from libs/X/src or libs/X/test. In other words, if someone tries to *use* X by including some of its headers, he needs (in the general case) to also have Y's headers installed, or the code will not compile.