-# Use $(blddir) instead of $(top_builddir) for arguments to "mkcheck"
-# because then the paths will be full pathnames, not relative
-# pathnames. (-Wl,--rpath seems to like this better.)
-check: $(top_builddir)/mkcheck
- chmod +x $(top_builddir)/mkcheck
- $(top_builddir)/mkcheck 0 `pwd` $(top_srcdir)
-
-check-install: $(top_builddir)/mkcheck
- chmod +x $(top_builddir)/mkcheck
- $(top_builddir)/mkcheck 1 `pwd` $(top_srcdir) $(prefix)
+# These two special 'check-script' rules use the bash script 'mkcheck'
+# to do testing. This script is not as portable as the dejagnu test
+# harness, and is thus off by default. It does produce interesting
+# output however, including various performance analysis items like
+# compile time, execution time, and binary size.
+check-script: $(top_builddir)/mkcheck
+ -(chmod + $(top_builddir)/mkcheck; \
+ cd testsuite; \
+ @glibcpp_builddir@/mkcheck 0)
+
+check-script-install: $(top_builddir)/mkcheck
+ -(chmod + $(top_builddir)/mkcheck; \
+ cd testsuite; \
+ @glibcpp_builddir@/mkcheck 1)
+
+# These rules are messy, but are hella worth it.
+doxygen:
+ -(srcdir=`cd ${top_srcdir}; pwd`; \
+ builddir=`pwd`; \
+ /bin/sh ${srcdir}/docs/doxygen/run_doxygen \
+ --mode=user $${srcdir} $${builddir})
+
+doxygen-maint:
+ -(srcdir=`cd ${top_srcdir}; pwd`; \
+ builddir=`pwd`; \
+ /bin/sh ${srcdir}/docs/doxygen/run_doxygen \
+ --mode=maint $${srcdir} $${builddir})
+
+doxygen-man:
+ -(srcdir=`cd ${top_srcdir}; pwd`; \
+ builddir=`pwd`; \
+ /bin/sh ${srcdir}/docs/doxygen/run_doxygen \
+ --mode=man $${srcdir} $${builddir})
+
+.PHONY: doxygen doxygen-maint doxygen-man