Stefano D'Angelo wrote: > 2008/10/3 Stefano D'Angelo <zanga.mail@xxxxxxxxx>: > >> 2008/10/2 John Calcote <john.calcote@xxxxxxxxx>: >> >>> You may wish to check out my book on Autotools, hosted by Free Software >>> Magazine. In there, I make several references to doxygen, and use code >>> snippets to implement doxygen targets within the sample projects and >>> examples provided in the book. >>> >>> http://www.freesoftwaremagazine.com/books/autotools_a_guide_to_autoconf_automake_libtool >>> >> Well... at first sight the whole thing seems a bit "simplicistic" to >> me, maybe also because I'm generating html, ps, pdf, dvi and man >> output with Doxygen. I'll give it a better look tomorrow maybe. >> > > Ok, read it. I have to congratulate with you for the manual, which > looks way better than the "autobook" (and less outdated of course), > but as said, the proposed solution wouldn't satisfy my needs. > > Other than that, I think you could have used AC_CHECK_PROG instead of > AC_CHECK_PROGS to look for the doxygen binary, since it already does > the -z test on the variable used to store its path, thus you wouldn't > need the AC_PROG_TRY_DOXYGEN macro. Stefano, I apologize for my lack of communication here. I didn't mean to ever imply that my solution was the best one out there. I was simply giving you some more resources to look at for building your generic doxygen solution. I only hope it was helpful. Cheers, John _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
