Let me think about it - seems there is a need to separate the eps files from install-man target. It's really the dist-docs scripts that needs the eps files.
Shu > On Feb 3, 2015, at 3:52 PM, Ben Pfaff <b...@nicira.com> wrote: > >> On Fri, Jan 30, 2015 at 04:02:40PM -0800, Shu Shen wrote: >> The previous workflow is to convert dot diagrams into .pic format and >> embed into manpages; double borders and arrows were not used in dot but >> introduced in .pic conversion; edge routing in .pic was also worse than >> dot. >> >> The updated workflow specifies directly in dot diagram double >> boarders for "root set" nodes and solid/bold styles and arrows for >> edges. The converted .eps diagram has improved routing. The .eps diagram >> is embedded into PDF using groff PSPIC marco package when converting the >> manpages. PSPIC package is automatically loaded by groff when output to >> PS/PDF. >> >> In addition, 'constraint=false' option is removed from weak >> references to allow positioning of node boxes to avoid overlapping >> between multiple edges between "Mirror" and "Port" in >> ovs-vswitchd.conf.db. >> >> Signed-off-by: Shu Shen <shu.s...@radisys.com> > > OK, now it doesn't generate build errors, but now that I realize what's > going on, I don't know how manpages with dependencies like this get > installed. Where does vswitch.eps go in the file system, and how does > it get there? I see, for example, that "make install" puts vswitch.eps > in /usr/share/man/mane, which can't be right. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
