Doxyfile 6.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153
  1. #
  2. # ngIRCd -- The Next Generation IRC Daemon
  3. # Copyright (c)2001-2005 Alexander Barton (alex@barton.de)
  4. #
  5. # This program is free software; you can redistribute it and/or modify
  6. # it under the terms of the GNU General Public License as published by
  7. # the Free Software Foundation; either version 2 of the License, or
  8. # (at your option) any later version.
  9. # Please read the file COPYING, README and AUTHORS for more information.
  10. #
  11. # $Id: Doxyfile,v 1.2 2005/07/23 00:48:38 alex Exp $
  12. #
  13. # This file describes the settings to be used by the documentation system
  14. # doxygen (www.doxygen.org) for ngIRCd.
  15. #---------------------------------------------------------------------------
  16. # Project related configuration options
  17. #---------------------------------------------------------------------------
  18. # The PROJECT_NAME tag is a single word (or a sequence of words surrounded
  19. # by quotes) that should identify the project.
  20. PROJECT_NAME = ngIRCd
  21. # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
  22. # base path where the generated documentation will be put.
  23. # If a relative path is entered, it will be relative to the location
  24. # where doxygen was started. If left blank the current directory will be used.
  25. OUTPUT_DIRECTORY = .
  26. # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
  27. # can be used to strip a user-defined part of the path. Stripping is
  28. # only done if one of the specified strings matches the left-hand part of
  29. # the path. The tag can be used to show relative paths in the file list.
  30. # If left blank the directory from which doxygen is run is used as the
  31. # path to strip.
  32. STRIP_FROM_PATH = ../..
  33. # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
  34. # will interpret the first line (until the first dot) of a JavaDoc-style
  35. # comment as the brief description. If set to NO, the JavaDoc
  36. # comments will behave just like the Qt-style comments (thus requiring an
  37. # explicit @brief command for a brief description.
  38. JAVADOC_AUTOBRIEF = YES
  39. # If the DETAILS_AT_TOP tag is set to YES then Doxygen
  40. # will output the detailed description near the top, like JavaDoc.
  41. # If set to NO, the detailed description appears after the member
  42. # documentation.
  43. DETAILS_AT_TOP = NO
  44. # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
  45. # sources only. Doxygen will then generate output that is more tailored for C.
  46. # For instance, some of the names that are used will be different. The list
  47. # of all members will be omitted, etc.
  48. OPTIMIZE_OUTPUT_FOR_C = YES
  49. #---------------------------------------------------------------------------
  50. # Build related configuration options
  51. #---------------------------------------------------------------------------
  52. # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
  53. # documentation are documented, even if no documentation was available.
  54. # Private class members and static file members will be hidden unless
  55. # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
  56. EXTRACT_ALL = YES
  57. # If the EXTRACT_PRIVATE tag is set to YES all private members of a class
  58. # will be included in the documentation.
  59. EXTRACT_PRIVATE = YES
  60. # If the EXTRACT_STATIC tag is set to YES all static members of a file
  61. # will be included in the documentation.
  62. EXTRACT_STATIC = YES
  63. # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
  64. # defined locally in source files will be included in the documentation.
  65. # If set to NO only classes defined in header files are included.
  66. EXTRACT_LOCAL_CLASSES = YES
  67. #---------------------------------------------------------------------------
  68. # configuration options related to the input files
  69. #---------------------------------------------------------------------------
  70. # The INPUT tag can be used to specify the files and/or directories that
  71. # contain documented source files. You may enter file names like "myfile.cpp"
  72. # or directories like "/usr/src/myproject". Separate the files or directories
  73. # with spaces.
  74. INPUT = ../../src
  75. # The RECURSIVE tag can be used to turn specify whether or not subdirectories
  76. # should be searched for input files as well. Possible values are YES and NO.
  77. # If left blank NO is used.
  78. RECURSIVE = YES
  79. #---------------------------------------------------------------------------
  80. # configuration options related to source browsing
  81. #---------------------------------------------------------------------------
  82. # If the SOURCE_BROWSER tag is set to YES then a list of source files will
  83. # be generated. Documented entities will be cross-referenced with these sources.
  84. # Note: To get rid of all source code in the generated output, make sure also
  85. # VERBATIM_HEADERS is set to NO.
  86. SOURCE_BROWSER = YES
  87. #---------------------------------------------------------------------------
  88. # Output formats
  89. #---------------------------------------------------------------------------
  90. GENERATE_HTML = YES
  91. HTML_OUTPUT = html
  92. HTML_FILE_EXTENSION = .html
  93. HTML_HEADER = header.inc.html
  94. HTML_FOOTER = footer.inc.html
  95. HTML_STYLESHEET = ngircd-doc.css
  96. GENERATE_HTMLHELP = NO
  97. GENERATE_LATEX = NO
  98. GENERATE_RTF = NO
  99. GENERATE_MAN = NO
  100. GENERATE_XML = NO
  101. GENERATE_AUTOGEN_DEF = NO
  102. GENERATE_PERLMOD = NO
  103. #---------------------------------------------------------------------------
  104. # Configuration options related to the preprocessor
  105. #---------------------------------------------------------------------------
  106. # The PREDEFINED tag can be used to specify one or more macro names that
  107. # are defined before the preprocessor is started (similar to the -D option of
  108. # gcc). The argument of the tag is a list of macros of the form: name
  109. # or name=definition (no spaces). If the definition and the = are
  110. # omitted =1 is assumed. To prevent a macro definition from being
  111. # undefined via #undef or recursively expanded use the := operator
  112. # instead of the = operator.
  113. PREDEFINED = CONN_MODULE __client_c__
  114. # -eof-