summaryrefslogtreecommitdiff
path: root/devel/doxygen
AgeCommit message (Collapse)AuthorFilesLines
2004-01-20Move WRKSRC definition away from the first paragraph in a Makefile.agc1-2/+2
2003-12-24Adjust dependancies and bump PKGREVISION due to:jmmv1-3/+3
- teTeX 1.0.x packages have been moved to teTeX1* directories. - teTeX 2.0.x packages have been moved to teTeX* directories and their base name has been changed to teTeX (instead of teTeX2).
2003-12-23Depend on either teTeX and teTeX2 (defaulting to the later).jmmv1-2/+3
Fixes PR pkg/23852.
2003-12-03Updated doxygen to 1.3.5martti3-11/+11
* bug fixes
2003-10-05Updated doxygen to 1.3.4martti4-27/+12
* bug fixes
2003-09-03Updated doxygen to 1.3.3martti2-6/+6
- Bug fixes - New features * Added new debug flag "-d Time" which will report the elapsed time for each message printed, and will also show the total running time along with the time spend on external tools such as dot. Note: If you have a project that takes doxygen a long time to process, please send me the output so I get a global idea where to optimize. * New option SUBGROUPING which can be set to NO to have \nosubgrouping for all classes (thanks to Torben Koch for the patch). * Added XML schemas for validating the XML output, and to help writing XSLT files. The generated index.xml now has a complete schema, the compounds not yet. Thanks go to Alexej Humbach for doing a lot of the work. Note that a couple of "id" attributes in the XML output have been changed to "refid", and section tags are now nested. * Included language updates for Traditional Chinese and Japanese.
2003-07-17s/netbsd.org/NetBSD.org/grant1-2/+2
2003-06-16Updated doxygen to 1.3.2martti6-43/+51
* Lots of bug fixes * Language updates
2003-05-09Updated doxygen to 1.3martti7-35/+25
* translation updates * lots of bug fixes
2003-05-06Drop trailing whitespace. Ok'ed by wiz.jmmv1-4/+4
2003-03-29Place WRKSRC where it belongs, to make pkglint happy; ok'ed by wiz.jmmv1-3/+2
2002-12-14REPLACE_PERL's working directory is ${WRKSRC}, so packages needn'tschmonz1-2/+2
prefix REPLACE_PERL definitions with ${WRKSRC}.
2002-10-24Updated doxygen to 1.2.18 (changes unknown).martti8-100/+128
2002-09-13Use ghostscript.mk.jlam1-2/+2
2002-08-18fix installation on systems where '.' is not in root's path.dmcmahill2-1/+14
2002-06-17Use REPLACE_PERL to substitute for the correct version of perl inagc1-2/+3
doc/translator.pl, which has the side effect of allowing the docygen package to be installed properly if you don't have '.' in your path. Bump PKGREVISION.
2002-03-17Use ${PKGNAME_NOREV} in definition of ${WRKSRC}.fredb1-2/+2
2002-03-13Give all packages which depend on "png" a version bump, and updatefredb1-1/+2
all dependencies on packages depending on "png" which contain shared libraries, all for the (imminent) update to the "png" package. [List courtesy of John Darrow, courtesy of "bulk-build".]
2002-01-14Comment out some unneeded code that produced errors, in contrast towiz4-1/+37
what the comment above it claims. Should fix bulk build failure.
2001-11-01Move pkg/ files into package's toplevel directoryzuntum2-1/+1
2001-09-04Really depend on LaTeX and Ghostscript-- it's largely useless without itgroo4-9/+361
(even generating HTML). Install documentation and examples.
2001-09-04Import doxygen-1.2.10:groo5-0/+70
Doxygen is a documentation system for C++, Java, IDL (Corba, Microsoft and KDE-DCOP flavors) and C. It can help you in three ways: 1. It can generate an on-line documentation browser (in HTML) and/or an off-line reference manual (in LaTeX) from a set of documented source files. There is also support for generating output in RTF (MS-Word), PostScript, hyperlinked PDF, compressed HTML, and Unix man pages. The documentation is extracted directly from the sources, which makes it much easier to keep the documentation consistent with the source code. 2. Doxygen can be configured to extract the code structure from undocumented source files. This can be very useful to quickly find your way in large source distributions. The relations between the various elements are be visualized by means of include dependency graphs, inheritance diagrams, and collaboration diagrams, which are all generated automatically. 3. You can even `abuse' doxygen for creating normal documentation