[MacPorts] #36459: doxygen @1.8.1: graphiz dependency problem?
Eric A. Borisch
eborisch at macports.org
Mon Feb 18 19:55:40 PST 2013
On Mon, Feb 18, 2013 at 6:39 PM, Ryan Schmidt <ryandesign at macports.org>wrote:
> On Feb 18, 2013, at 18:32, Lawrence Velázquez <larryv at macports.org> wrote:
> > On Feb 18, 2013, at 7:19 PM, Ryan Schmidt <ryandesign at macports.org>
> >> On Feb 18, 2013, at 14:26, Lawrence Velázquez <larryv at macports.org>
> >>> Why does doxygen have a dependency on graphviz, anyway? I'm aware that
> Doxygen can use Graphviz if it's available,
> >> The second sentence is the answer to the first.
> > Sure, but as far as I can tell, it's a runtime thing, and Graphviz is
> not *necessary* unless you actually want Doxygen to generate advanced class
> diagrams. And if you want that, you can install graphviz whenever you feel
> > http://www.stack.nl/~dimitri/doxygen/manual/diagrams.html
> > As it stands, installing doxygen forces you to pull in graphviz and its
> huge dependency tree, even if you have no intention of making diagrams.
> What about the ports that declare build dependencies on doxygen? Do any of
> them use this diagramming capability?
FWIW, FreeBSD's port requires graphviz  and many Linux RPMs don't 
... so there's no consensus to be had by looking for what others are doing.
I use doxygen with graphviz, but most of utility exists without it. The
differences between the dependencies with  and without  are striking.
Perhaps a default variant (+diagrams)?
This doesn't address if any other ports depending on doxygen use the dot
capability, but it would be easy enough for those ports to declare the
graphviz requirement themselves. A default doxyfile (doxygen -g output)
currently has HAVE_DOT set to NO, regardless of its presence at build- or
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the macports-dev