CodeDepencyGraph: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
Instructions to make the code dependency graph on computing division machine woof. | Instructions to make the code dependency graph on computing division machine called woof. | ||
<ol> | <ol> |
Revision as of 16:16, 22 October 2018
Instructions to make the code dependency graph on computing division machine called woof.
- Clean checkout git clone ssh://p-mu2eofflinesoftwaremu2eoffline@cdcvs.fnal.gov/cvs/projects/mu2eofflinesoftwaremu2eoffline/Offline.git
- Remove files that unnecessarily complicate the picture. This includes all modules, which natuallry all sit at the top dependence layer, and a few directories like Sandbox. This does actual file deletes in the release... # Once upon a time I checked that everything would build if we source ~kutschke/LinkLoops/trim.sh
- Create the file that contains the dependency pairs cd Offline time /home/greenc/work/cet-is/sources/cetbuildtools/bin/code-dep-graph -v -o ../trimmed.dot >& ../trimmed.log
- Transitive reduction and create graph # This step issues a warning if 1 or more loops exist. # The loop is neither complete nor super informative tred trimmed.dot | dot -Tpng -o trimmed.png
- Create graph without transitive reduction - impossible to read dot trimmed.dot -Tpng -o trimmed_notred.png