> From: Anatoly Burakov [mailto:anatoly.bura...@intel.com] > > As part of the meson build, we can record the dependencies for each > component as we process it, logging them to a file. This file can be > used as input to a number of other scripts and tools, for example, to > graph the dependencies, or to allow higher-level build-config tools to > automatically enable component requirements, etc. > > The first patch of this set separates dependencies inside meson into > optional or mandatory. The second patch of this set generates the basic > dependency tree. The third patch does some processing of that dependency > tree to identify cases where dependencies are being unnecessarily > specified. Reducing these makes it easier to have readable dependency > graphs in future, without affecting the build. > > The following 4 patches are based on the output of the second patch, and > greatly cut down the number of direct dependency links between > components. Even with the cut-down dependencies, the full dependency > graph is nigh-unreadable, so the final patch adds a new script to > generate dependency tree subgraphs, creating dot files for e.g. the > dependencies of a particular component, or a component class such as > mempool drivers. >
For the series, Acked-by: Morten Brørup <m...@smartsharesystems.com>
