[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    kdesupport/qt-dbus
From:       Brad Hards <bradh () frogmouth ! net>
Date:       2006-06-04 12:23:16
Message-ID: 1149423796.033702.4302.nullmailer () svn ! kde ! org
[Download RAW message or body]

SVN commit 548003 by bhards:

Start the conversion to Doxygen. With this, it actually
does generate some docs. There are still a ton of errors,
and I have some fixes still to merge.


 M  +9 -9      Doxyfile  
 A             qt.tag  


--- trunk/kdesupport/qt-dbus/Doxyfile #548002:548003
@@ -23,14 +23,14 @@
 # This could be handy for archiving the generated documentation or 
 # if some version control system is used.
 
-PROJECT_NUMBER         = 0.60
+PROJECT_NUMBER         = 0.62
 
 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) 
 # base path where the generated documentation will be put. 
 # If a relative path is entered, it will be relative to the location 
 # where doxygen was started. If left blank the current directory will be used.
 
-OUTPUT_DIRECTORY       = ../doc/api
+OUTPUT_DIRECTORY       = doc/api
 
 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 
 # 4096 sub-directories (in 2 levels) under the output directory of each output 
@@ -287,7 +287,7 @@
 # to NO (the default) then the documentation will be excluded. 
 # Set it to YES to include the internal documentation.
 
-INTERNAL_DOCS          = NO
+INTERNAL_DOCS          = YES
 
 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate 
 # file names in lower-case letters. If set to YES upper-case letters are also 
@@ -459,7 +459,7 @@
 # directories like "/usr/src/myproject". Separate the files or directories 
 # with spaces.
 
-INPUT                  = .
+INPUT                  = src
 
 # If the value of the INPUT tag contains directories, you can use the 
 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
@@ -512,14 +512,13 @@
                          magic \
                          NOTES \
                          TODO \
-                         THANKS \
-                         *_p.h
+                         THANKS
 
 # The EXAMPLE_PATH tag can be used to specify one or more files or 
 # directories that contain example code fragments that are included (see 
 # the \include command).
 
-EXAMPLE_PATH           = 
+EXAMPLE_PATH           = examples
 
 # If the value of the EXAMPLE_PATH tag contains directories, you can use the 
 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
@@ -1029,7 +1028,8 @@
                          DOXYGEN_SHOULD_SKIP_THIS \
                          _DBUS_DEFINE_GLOBAL_LOCK(name)= \
                          _DBUS_GNUC_PRINTF(from,to)= \
-			 Q_DECLARE_FLAGS(flags,theenum)=
+			 Q_DECLARE_FLAGS(flags,theenum)= \
+			 Q_QDOC
 
 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then 
 # this tag can be used to specify a list of macro names that should be expanded. 
@@ -1065,7 +1065,7 @@
 # If a tag file is not located in the directory in which doxygen 
 # is run, you must also specify the path to the tagfile here.
 
-TAGFILES               = /home/tjmaciei/troll/qt-4.1/doc/qt.tag=http://doc.trolltech.com/4.1
+TAGFILES               = ./qt.tag=http://doc.trolltech.com/4.1
 
 # When a file name is specified after GENERATE_TAGFILE, doxygen will create 
 # a tag file that is based on the input files it reads.
[prev in list] [next in list] [prev in thread] [next in thread]