OpenSAML user discussion

[Brent Putman <>]

Thanks Von.  I just updated the bug id with a slightly different 
approach than yours which I think is more inline with the intent of the 
doxygen autotools macros, and also has the added benefit of being much 
simpler code (i.e. less stuff to break...).  Can you test and let me 
know if it works in your environment?  If all is OK, I'll check it in 
for both cpp-xmltooling and cpp-opensaml2 (unless Scott vetoes me).

Also, from looking at the doxygen macros, doxygen itself has a hardcoded 
dependency on Perl - which I can't imagine anyone not having on the 
Unixes, so just pointing it out.

Thanks,
Brent



Von Welch wrote:
> You can see what I came up with:
>
> http://bugzilla.internet2.edu/show_bug.cgi?id=565
>
> Von
>
> On Aug 28, 2006, at 2:11 PM, Brent Putman wrote:
>
> > I just recreated this.  The internal doxygen configure tests result 
> > in all the doxygen targets etc being commented out in the generated 
> > Makefile, which I guess is fine.  The problem lies in the fact the 
> > cpp-xmltooling/Makefile.am unconditionally adds the doxygen-doc 
> > target to all-local:
> >
> > all-local: xmltooling.spec pkginfo doxygen-doc
> >
> > If there is an internal doxygen variable we can key off of to detect 
> > presence/absence of doxygen, or if we can otherwise test it, then I 
> > think it should work to fix the above by conditionally adding the 
> > doxygen-doc target based on that.  I'll take a further look at the 
> > doxygen-supplied macros to see what they do.
> >
> > --Brent
> >
> >
> > Von Welch wrote:
> > > I've already installed doxygen, but I'll see what I can do to recreate.
> > >
> > > BTW, is there a bugzilla for opensaml2 or is this the preferred 
> > > reporting mechanism?
> > >
> > > Von
> > >
> > >
> > > On Aug 28, 2006, at 12:30 PM, Scott Cantor wrote:
> > >
> > > > What happens if you configure with --disable-doxygen-doc ?
> > > >
> > > > It seems like there's a problem, but it probably can be worked 
> > > > around that
> > > > way. The doxygen tests must not be disabling the target, or perhaps 
> > > > the
> > > > tests aren't working at all.
> > > >
> > > > -- Scott