prepare for doxygen documentation

diff --git a/Makefile.in b/Makefile.in
index 4cea07cde4c07547a41546e8e1b01ff447bced0c..75d95650d62d0748f5f1602cc50be975004a572b 100644 (file)
--- a/Makefile.in
+++ b/Makefile.in
@@ -77,7 +77,9 @@ realclean: clean docclean
        rm -f configure
 
 docclean:
-       rm -rf doc
+       rm -rf doc/html/
+       rm -rf doc/man/
+       rm -rf doc/latex/
 
 test0: run-test0
        ./run-test0

diff --git a/libdns.doxygen b/libdns.doxygen
index dfbaadda50727cd76809f48c945a1bdad74c64aa..dcacff7a03ed51b3ceadf480191f4980bc2eebf5 100644 (file)
--- a/libdns.doxygen
+++ b/libdns.doxygen
@@ -186,7 +186,7 @@ ALIASES                =
 # For instance, some of the names that are used will be different. The list 
 # of all members will be omitted, etc.
 
-OPTIMIZE_OUTPUT_FOR_C  = NO
+OPTIMIZE_OUTPUT_FOR_C  = YES
 
 # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources 
 # only. Doxygen will then generate output that is more tailored for Java. 
@@ -808,7 +808,7 @@ RTF_EXTENSIONS_FILE    =
 # If the GENERATE_MAN tag is set to YES (the default) Doxygen will 
 # generate man pages
 
-GENERATE_MAN           = NO
+GENERATE_MAN           = YES
 
 # The MAN_OUTPUT tag is used to specify where the man pages will be put. 
 # If a relative path is entered the value of OUTPUT_DIRECTORY will be