Commit | Line | Data |
---|---|---|
cbc85b6f GE |
1 | # Doxyfile 1.4.7-4 |
2 | ||
3 | # This file describes the settings to be used by the documentation system | |
4 | # doxygen (www.doxygen.org) for a project | |
5 | # | |
6 | # All text after a hash (#) is considered a comment and will be ignored | |
7 | # The format is: | |
8 | # TAG = value [value, ...] | |
9 | # For lists items can also be appended using: | |
10 | # TAG += value [value, ...] | |
11 | # Values that contain spaces should be placed between quotes (" ") | |
12 | ||
13 | #--------------------------------------------------------------------------- | |
14 | # Project related configuration options | |
15 | #--------------------------------------------------------------------------- | |
16 | ||
17 | # The PROJECT_NAME tag is a single word (or a sequence of words surrounded | |
18 | # by quotes) that should identify the project. | |
19 | ||
20 | PROJECT_NAME = @PACKAGE@ | |
21 | ||
22 | # The PROJECT_NUMBER tag can be used to enter a project or revision number. | |
23 | # This could be handy for archiving the generated documentation or | |
24 | # if some version control system is used. | |
25 | ||
26 | PROJECT_NUMBER = @VERSION@ | |
27 | ||
28 | # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) | |
29 | # base path where the generated documentation will be put. | |
30 | # If a relative path is entered, it will be relative to the location | |
31 | # where doxygen was started. If left blank the current directory will be used. | |
32 | ||
33 | OUTPUT_DIRECTORY = | |
34 | ||
35 | # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create | |
36 | # 4096 sub-directories (in 2 levels) under the output directory of each output | |
37 | # format and will distribute the generated files over these directories. | |
38 | # Enabling this option can be useful when feeding doxygen a huge amount of | |
39 | # source files, where putting all generated files in the same directory would | |
40 | # otherwise cause performance problems for the file system. | |
41 | ||
42 | CREATE_SUBDIRS = NO | |
43 | ||
44 | # The OUTPUT_LANGUAGE tag is used to specify the language in which all | |
45 | # documentation generated by doxygen is written. Doxygen will use this | |
46 | # information to generate all constant output in the proper language. | |
47 | # The default language is English, other supported languages are: | |
48 | # Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, | |
49 | # Croatian, Czech, Danish, Dutch, Finnish, French, German, Greek, Hungarian, | |
50 | # Italian, Japanese, Japanese-en (Japanese with English messages), Korean, | |
51 | # Korean-en, Lithuanian, Norwegian, Polish, Portuguese, Romanian, Russian, | |
52 | # Serbian, Slovak, Slovene, Spanish, Swedish, and Ukrainian. | |
53 | ||
54 | OUTPUT_LANGUAGE = English | |
55 | ||
56 | # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will | |
57 | # include brief member descriptions after the members that are listed in | |
58 | # the file and class documentation (similar to JavaDoc). | |
59 | # Set to NO to disable this. | |
60 | ||
61 | BRIEF_MEMBER_DESC = YES | |
62 | ||
63 | # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend | |
64 | # the brief description of a member or function before the detailed description. | |
65 | # Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the | |
66 | # brief descriptions will be completely suppressed. | |
67 | ||
68 | REPEAT_BRIEF = YES | |
69 | ||
70 | # This tag implements a quasi-intelligent brief description abbreviator | |
71 | # that is used to form the text in various listings. Each string | |
72 | # in this list, if found as the leading text of the brief description, will be | |
73 | # stripped from the text and the result after processing the whole list, is | |
74 | # used as the annotated text. Otherwise, the brief description is used as-is. | |
75 | # If left blank, the following values are used ("$name" is automatically | |
76 | # replaced with the name of the entity): "The $name class" "The $name widget" | |
77 | # "The $name file" "is" "provides" "specifies" "contains" | |
78 | # "represents" "a" "an" "the" | |
79 | ||
80 | ABBREVIATE_BRIEF = | |
81 | ||
82 | # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then | |
83 | # Doxygen will generate a detailed section even if there is only a brief | |
84 | # description. | |
85 | ||
86 | ALWAYS_DETAILED_SEC = YES | |
87 | ||
88 | # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all | |
89 | # inherited members of a class in the documentation of that class as if those | |
90 | # members were ordinary class members. Constructors, destructors and assignment | |
91 | # operators of the base classes will not be shown. | |
92 | ||
93 | INLINE_INHERITED_MEMB = YES | |
94 | ||
95 | # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full | |
96 | # path before files name in the file list and in the header files. If set | |
97 | # to NO the shortest path that makes the file name unique will be used. | |
98 | ||
99 | FULL_PATH_NAMES = NO | |
100 | ||
101 | # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag | |
102 | # can be used to strip a user-defined part of the path. Stripping is | |
103 | # only done if one of the specified strings matches the left-hand part of | |
104 | # the path. The tag can be used to show relative paths in the file list. | |
105 | # If left blank the directory from which doxygen is run is used as the | |
106 | # path to strip. | |
107 | ||
108 | STRIP_FROM_PATH = | |
109 | ||
110 | # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of | |
111 | # the path mentioned in the documentation of a class, which tells | |
112 | # the reader which header file to include in order to use a class. | |
113 | # If left blank only the name of the header file containing the class | |
114 | # definition is used. Otherwise one should specify the include paths that | |
115 | # are normally passed to the compiler using the -I flag. | |
116 | ||
117 | STRIP_FROM_INC_PATH = | |
118 | ||
119 | # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter | |
120 | # (but less readable) file names. This can be useful is your file systems | |
121 | # doesn't support long names like on DOS, Mac, or CD-ROM. | |
122 | ||
123 | SHORT_NAMES = NO | |
124 | ||
125 | # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen | |
126 | # will interpret the first line (until the first dot) of a JavaDoc-style | |
127 | # comment as the brief description. If set to NO, the JavaDoc | |
128 | # comments will behave just like the Qt-style comments (thus requiring an | |
129 | # explicit @brief command for a brief description. | |
130 | ||
131 | JAVADOC_AUTOBRIEF = NO | |
132 | ||
133 | # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen | |
134 | # treat a multi-line C++ special comment block (i.e. a block of //! or /// | |
135 | # comments) as a brief description. This used to be the default behaviour. | |
136 | # The new default is to treat a multi-line C++ comment block as a detailed | |
137 | # description. Set this tag to YES if you prefer the old behaviour instead. | |
138 | ||
139 | MULTILINE_CPP_IS_BRIEF = NO | |
140 | ||
141 | # If the DETAILS_AT_TOP tag is set to YES then Doxygen | |
142 | # will output the detailed description near the top, like JavaDoc. | |
143 | # If set to NO, the detailed description appears after the member | |
144 | # documentation. | |
145 | ||
146 | #DETAILS_AT_TOP = NO | |
147 | ||
148 | # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented | |
149 | # member inherits the documentation from any documented member that it | |
150 | # re-implements. | |
151 | ||
152 | INHERIT_DOCS = YES | |
153 | ||
154 | # If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce | |
155 | # a new page for each member. If set to NO, the documentation of a member will | |
156 | # be part of the file/class/namespace that contains it. | |
157 | ||
158 | SEPARATE_MEMBER_PAGES = NO | |
159 | ||
160 | # The TAB_SIZE tag can be used to set the number of spaces in a tab. | |
161 | # Doxygen uses this value to replace tabs by spaces in code fragments. | |
162 | ||
163 | TAB_SIZE = 4 | |
164 | ||
165 | # This tag can be used to specify a number of aliases that acts | |
166 | # as commands in the documentation. An alias has the form "name=value". | |
167 | # For example adding "sideeffect=\par Side Effects:\n" will allow you to | |
168 | # put the command \sideeffect (or @sideeffect) in the documentation, which | |
169 | # will result in a user-defined paragraph with heading "Side Effects:". | |
170 | # You can put \n's in the value part of an alias to insert newlines. | |
171 | ||
172 | ALIASES = | |
4f6228c3 RP |
173 | ALIASES += copyright="\par Copyright\n" |
174 | ALIASES += license="\par License\n" | |
175 | ALIASES += contact="\par Contact\n" | |
cbc85b6f GE |
176 | |
177 | # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C | |
178 | # sources only. Doxygen will then generate output that is more tailored for C. | |
179 | # For instance, some of the names that are used will be different. The list | |
180 | # of all members will be omitted, etc. | |
181 | ||
182 | OPTIMIZE_OUTPUT_FOR_C = NO | |
183 | ||
184 | # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java | |
185 | # sources only. Doxygen will then generate output that is more tailored for Java. | |
186 | # For instance, namespaces will be presented as packages, qualified scopes | |
187 | # will look different, etc. | |
188 | ||
189 | OPTIMIZE_OUTPUT_JAVA = NO | |
190 | ||
191 | # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want to | |
192 | # include (a tag file for) the STL sources as input, then you should | |
193 | # set this tag to YES in order to let doxygen match functions declarations and | |
194 | # definitions whose arguments contain STL classes (e.g. func(std::string); v.s. | |
195 | # func(std::string) {}). This also make the inheritance and collaboration | |
196 | # diagrams that involve STL classes more complete and accurate. | |
197 | ||
198 | BUILTIN_STL_SUPPORT = YES | |
199 | ||
200 | # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC | |
201 | # tag is set to YES, then doxygen will reuse the documentation of the first | |
202 | # member in the group (if any) for the other members of the group. By default | |
203 | # all members of a group must be documented explicitly. | |
204 | ||
205 | DISTRIBUTE_GROUP_DOC = NO | |
206 | ||
207 | # Set the SUBGROUPING tag to YES (the default) to allow class member groups of | |
208 | # the same type (for instance a group of public functions) to be put as a | |
209 | # subgroup of that type (e.g. under the Public Functions section). Set it to | |
210 | # NO to prevent subgrouping. Alternatively, this can be done per class using | |
211 | # the \nosubgrouping command. | |
212 | ||
213 | SUBGROUPING = YES | |
214 | ||
215 | #--------------------------------------------------------------------------- | |
216 | # Build related configuration options | |
217 | #--------------------------------------------------------------------------- | |
218 | ||
219 | # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in | |
220 | # documentation are documented, even if no documentation was available. | |
221 | # Private class members and static file members will be hidden unless | |
222 | # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES | |
223 | ||
224 | EXTRACT_ALL = YES | |
225 | ||
226 | # If the EXTRACT_PRIVATE tag is set to YES all private members of a class | |
227 | # will be included in the documentation. | |
228 | ||
229 | EXTRACT_PRIVATE = YES | |
230 | ||
231 | # If the EXTRACT_STATIC tag is set to YES all static members of a file | |
232 | # will be included in the documentation. | |
233 | ||
234 | EXTRACT_STATIC = YES | |
235 | ||
236 | # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) | |
237 | # defined locally in source files will be included in the documentation. | |
238 | # If set to NO only classes defined in header files are included. | |
239 | ||
240 | EXTRACT_LOCAL_CLASSES = YES | |
241 | ||
242 | # This flag is only useful for Objective-C code. When set to YES local | |
243 | # methods, which are defined in the implementation section but not in | |
244 | # the interface are included in the documentation. | |
245 | # If set to NO (the default) only methods in the interface are included. | |
246 | ||
247 | EXTRACT_LOCAL_METHODS = NO | |
248 | ||
249 | # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all | |
250 | # undocumented members of documented classes, files or namespaces. | |
251 | # If set to NO (the default) these members will be included in the | |
252 | # various overviews, but no documentation section is generated. | |
253 | # This option has no effect if EXTRACT_ALL is enabled. | |
254 | ||
255 | HIDE_UNDOC_MEMBERS = NO | |
256 | ||
257 | # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all | |
258 | # undocumented classes that are normally visible in the class hierarchy. | |
259 | # If set to NO (the default) these classes will be included in the various | |
260 | # overviews. This option has no effect if EXTRACT_ALL is enabled. | |
261 | ||
262 | HIDE_UNDOC_CLASSES = NO | |
263 | ||
264 | # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all | |
265 | # friend (class|struct|union) declarations. | |
266 | # If set to NO (the default) these declarations will be included in the | |
267 | # documentation. | |
268 | ||
269 | HIDE_FRIEND_COMPOUNDS = NO | |
270 | ||
271 | # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any | |
272 | # documentation blocks found inside the body of a function. | |
273 | # If set to NO (the default) these blocks will be appended to the | |
274 | # function's detailed documentation block. | |
275 | ||
276 | HIDE_IN_BODY_DOCS = NO | |
277 | ||
278 | # The INTERNAL_DOCS tag determines if documentation | |
279 | # that is typed after a \internal command is included. If the tag is set | |
280 | # to NO (the default) then the documentation will be excluded. | |
281 | # Set it to YES to include the internal documentation. | |
282 | ||
283 | INTERNAL_DOCS = YES | |
284 | ||
285 | # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate | |
286 | # file names in lower-case letters. If set to YES upper-case letters are also | |
287 | # allowed. This is useful if you have classes or files whose names only differ | |
288 | # in case and if your file system supports case sensitive file names. Windows | |
289 | # and Mac users are advised to set this option to NO. | |
290 | ||
291 | CASE_SENSE_NAMES = YES | |
292 | ||
293 | # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen | |
294 | # will show members with their full class and namespace scopes in the | |
295 | # documentation. If set to YES the scope will be hidden. | |
296 | ||
297 | HIDE_SCOPE_NAMES = NO | |
298 | ||
299 | # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen | |
300 | # will put a list of the files that are included by a file in the documentation | |
301 | # of that file. | |
302 | ||
303 | SHOW_INCLUDE_FILES = YES | |
304 | ||
305 | # If the INLINE_INFO tag is set to YES (the default) then a tag [inline] | |
306 | # is inserted in the documentation for inline members. | |
307 | ||
308 | INLINE_INFO = YES | |
309 | ||
310 | # If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen | |
311 | # will sort the (detailed) documentation of file and class members | |
312 | # alphabetically by member name. If set to NO the members will appear in | |
313 | # declaration order. | |
314 | ||
315 | SORT_MEMBER_DOCS = YES | |
316 | ||
317 | # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the | |
318 | # brief documentation of file, namespace and class members alphabetically | |
319 | # by member name. If set to NO (the default) the members will appear in | |
320 | # declaration order. | |
321 | ||
322 | SORT_BRIEF_DOCS = NO | |
323 | ||
324 | # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be | |
325 | # sorted by fully-qualified names, including namespaces. If set to | |
326 | # NO (the default), the class list will be sorted only by class name, | |
327 | # not including the namespace part. | |
328 | # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. | |
329 | # Note: This option applies only to the class list, not to the | |
330 | # alphabetical list. | |
331 | ||
332 | SORT_BY_SCOPE_NAME = NO | |
333 | ||
334 | # The GENERATE_TODOLIST tag can be used to enable (YES) or | |
335 | # disable (NO) the todo list. This list is created by putting \todo | |
336 | # commands in the documentation. | |
337 | ||
338 | GENERATE_TODOLIST = YES | |
339 | ||
340 | # The GENERATE_TESTLIST tag can be used to enable (YES) or | |
341 | # disable (NO) the test list. This list is created by putting \test | |
342 | # commands in the documentation. | |
343 | ||
344 | GENERATE_TESTLIST = YES | |
345 | ||
346 | # The GENERATE_BUGLIST tag can be used to enable (YES) or | |
347 | # disable (NO) the bug list. This list is created by putting \bug | |
348 | # commands in the documentation. | |
349 | ||
350 | GENERATE_BUGLIST = YES | |
351 | ||
352 | # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or | |
353 | # disable (NO) the deprecated list. This list is created by putting | |
354 | # \deprecated commands in the documentation. | |
355 | ||
356 | GENERATE_DEPRECATEDLIST= YES | |
357 | ||
358 | # The ENABLED_SECTIONS tag can be used to enable conditional | |
359 | # documentation sections, marked by \if sectionname ... \endif. | |
360 | ||
361 | ENABLED_SECTIONS = | |
362 | ||
363 | # The MAX_INITIALIZER_LINES tag determines the maximum number of lines | |
364 | # the initial value of a variable or define consists of for it to appear in | |
365 | # the documentation. If the initializer consists of more lines than specified | |
366 | # here it will be hidden. Use a value of 0 to hide initializers completely. | |
367 | # The appearance of the initializer of individual variables and defines in the | |
368 | # documentation can be controlled using \showinitializer or \hideinitializer | |
369 | # command in the documentation regardless of this setting. | |
370 | ||
371 | MAX_INITIALIZER_LINES = 30 | |
372 | ||
373 | # Set the SHOW_USED_FILES tag to NO to disable the list of files generated | |
374 | # at the bottom of the documentation of classes and structs. If set to YES the | |
375 | # list will mention the files that were used to generate the documentation. | |
376 | ||
377 | SHOW_USED_FILES = YES | |
378 | ||
379 | # If the sources in your project are distributed over multiple directories | |
380 | # then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy | |
381 | # in the documentation. The default is NO. | |
382 | ||
383 | SHOW_DIRECTORIES = YES | |
384 | ||
385 | # The FILE_VERSION_FILTER tag can be used to specify a program or script that | |
386 | # doxygen should invoke to get the current version for each file (typically from the | |
387 | # version control system). Doxygen will invoke the program by executing (via | |
388 | # popen()) the command <command> <input-file>, where <command> is the value of | |
389 | # the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file | |
390 | # provided by doxygen. Whatever the program writes to standard output | |
391 | # is used as the file version. See the manual for examples. | |
392 | ||
393 | FILE_VERSION_FILTER = | |
394 | ||
395 | #--------------------------------------------------------------------------- | |
396 | # configuration options related to warning and progress messages | |
397 | #--------------------------------------------------------------------------- | |
398 | ||
399 | # The QUIET tag can be used to turn on/off the messages that are generated | |
400 | # by doxygen. Possible values are YES and NO. If left blank NO is used. | |
401 | ||
402 | QUIET = NO | |
403 | ||
404 | # The WARNINGS tag can be used to turn on/off the warning messages that are | |
405 | # generated by doxygen. Possible values are YES and NO. If left blank | |
406 | # NO is used. | |
407 | ||
408 | WARNINGS = YES | |
409 | ||
410 | # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings | |
411 | # for undocumented members. If EXTRACT_ALL is set to YES then this flag will | |
412 | # automatically be disabled. | |
413 | ||
414 | WARN_IF_UNDOCUMENTED = YES | |
415 | ||
416 | # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for | |
417 | # potential errors in the documentation, such as not documenting some | |
418 | # parameters in a documented function, or documenting parameters that | |
419 | # don't exist or using markup commands wrongly. | |
420 | ||
421 | WARN_IF_DOC_ERROR = YES | |
422 | ||
423 | # This WARN_NO_PARAMDOC option can be abled to get warnings for | |
424 | # functions that are documented, but have no documentation for their parameters | |
425 | # or return value. If set to NO (the default) doxygen will only warn about | |
426 | # wrong or incomplete parameter documentation, but not about the absence of | |
427 | # documentation. | |
428 | ||
429 | WARN_NO_PARAMDOC = NO | |
430 | ||
431 | # The WARN_FORMAT tag determines the format of the warning messages that | |
432 | # doxygen can produce. The string should contain the $file, $line, and $text | |
433 | # tags, which will be replaced by the file and line number from which the | |
434 | # warning originated and the warning text. Optionally the format may contain | |
435 | # $version, which will be replaced by the version of the file (if it could | |
436 | # be obtained via FILE_VERSION_FILTER) | |
437 | ||
438 | WARN_FORMAT = "$file:$line: $text" | |
439 | ||
440 | # The WARN_LOGFILE tag can be used to specify a file to which warning | |
441 | # and error messages should be written. If left blank the output is written | |
442 | # to stderr. | |
443 | ||
444 | WARN_LOGFILE = | |
445 | ||
446 | #--------------------------------------------------------------------------- | |
447 | # configuration options related to the input files | |
448 | #--------------------------------------------------------------------------- | |
449 | ||
450 | # The INPUT tag can be used to specify the files and/or directories that contain | |
451 | # documented source files. You may enter file names like "myfile.cpp" or | |
452 | # directories like "/usr/src/myproject". Separate the files or directories | |
453 | # with spaces. | |
454 | ||
5561b778 RP |
455 | INPUT = @top_srcdir@/doc @top_srcdir@/asyncio @top_srcdir@/utils \ |
456 | @top_srcdir@/utils/i2ncommon | |
457 | @HAVE_LIBT2N_TRUE@INPUT += @top_srcdir@/glue_t2n | |
cbc85b6f GE |
458 | |
459 | # If the value of the INPUT tag contains directories, you can use the | |
460 | # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp | |
461 | # and *.h) to filter out the source-files in the directories. If left | |
462 | # blank the following patterns are tested: | |
463 | # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx | |
464 | # *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py | |
465 | ||
466 | FILE_PATTERNS = *.hxx *.cpp *.doc *.hpp | |
467 | ||
468 | # The RECURSIVE tag can be used to turn specify whether or not subdirectories | |
469 | # should be searched for input files as well. Possible values are YES and NO. | |
470 | # If left blank NO is used. | |
471 | ||
472 | RECURSIVE = NO | |
473 | ||
474 | # The EXCLUDE tag can be used to specify files and/or directories that should | |
475 | # excluded from the INPUT source files. This way you can easily exclude a | |
476 | # subdirectory from a directory tree whose root is specified with the INPUT tag. | |
477 | ||
478 | EXCLUDE = | |
479 | ||
480 | # The EXCLUDE_SYMLINKS tag can be used select whether or not files or | |
481 | # directories that are symbolic links (a Unix filesystem feature) are excluded | |
482 | # from the input. | |
483 | ||
484 | EXCLUDE_SYMLINKS = NO | |
485 | ||
486 | # If the value of the INPUT tag contains directories, you can use the | |
487 | # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude | |
488 | # certain files from those directories. Note that the wildcards are matched | |
489 | # against the file with absolute path, so to exclude all test directories | |
490 | # for example use the pattern */test/* | |
491 | ||
492 | EXCLUDE_PATTERNS = | |
493 | ||
494 | # The EXAMPLE_PATH tag can be used to specify one or more files or | |
495 | # directories that contain example code fragments that are included (see | |
496 | # the \include command). | |
497 | ||
498 | EXAMPLE_PATH = @top_srcdir@/examples-codegen | |
499 | ||
500 | # If the value of the EXAMPLE_PATH tag contains directories, you can use the | |
501 | # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp | |
502 | # and *.h) to filter out the source-files in the directories. If left | |
503 | # blank all files are included. | |
504 | ||
505 | EXAMPLE_PATTERNS = | |
506 | ||
507 | # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be | |
508 | # searched for input files to be used with the \include or \dontinclude | |
509 | # commands irrespective of the value of the RECURSIVE tag. | |
510 | # Possible values are YES and NO. If left blank NO is used. | |
511 | ||
512 | EXAMPLE_RECURSIVE = YES | |
513 | ||
514 | # The IMAGE_PATH tag can be used to specify one or more files or | |
515 | # directories that contain image that are included in the documentation (see | |
516 | # the \image command). | |
517 | ||
518 | IMAGE_PATH = | |
519 | ||
520 | # The INPUT_FILTER tag can be used to specify a program that doxygen should | |
521 | # invoke to filter for each input file. Doxygen will invoke the filter program | |
522 | # by executing (via popen()) the command <filter> <input-file>, where <filter> | |
523 | # is the value of the INPUT_FILTER tag, and <input-file> is the name of an | |
524 | # input file. Doxygen will then use the output that the filter program writes | |
525 | # to standard output. If FILTER_PATTERNS is specified, this tag will be | |
526 | # ignored. | |
527 | ||
528 | INPUT_FILTER = | |
529 | ||
530 | # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern | |
531 | # basis. Doxygen will compare the file name with each pattern and apply the | |
532 | # filter if there is a match. The filters are a list of the form: | |
533 | # pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further | |
534 | # info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER | |
535 | # is applied to all files. | |
536 | ||
537 | FILTER_PATTERNS = | |
538 | ||
539 | # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using | |
540 | # INPUT_FILTER) will be used to filter the input files when producing source | |
541 | # files to browse (i.e. when SOURCE_BROWSER is set to YES). | |
542 | ||
543 | FILTER_SOURCE_FILES = NO | |
544 | ||
545 | #--------------------------------------------------------------------------- | |
546 | # configuration options related to source browsing | |
547 | #--------------------------------------------------------------------------- | |
548 | ||
549 | # If the SOURCE_BROWSER tag is set to YES then a list of source files will | |
550 | # be generated. Documented entities will be cross-referenced with these sources. | |
551 | # Note: To get rid of all source code in the generated output, make sure also | |
552 | # VERBATIM_HEADERS is set to NO. | |
553 | ||
554 | SOURCE_BROWSER = NO | |
555 | ||
556 | # Setting the INLINE_SOURCES tag to YES will include the body | |
557 | # of functions and classes directly in the documentation. | |
558 | ||
559 | INLINE_SOURCES = NO | |
560 | ||
561 | # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct | |
562 | # doxygen to hide any special comment blocks from generated source code | |
563 | # fragments. Normal C and C++ comments will always remain visible. | |
564 | ||
565 | STRIP_CODE_COMMENTS = YES | |
566 | ||
567 | # If the REFERENCED_BY_RELATION tag is set to YES (the default) | |
568 | # then for each documented function all documented | |
569 | # functions referencing it will be listed. | |
570 | ||
571 | REFERENCED_BY_RELATION = YES | |
572 | ||
573 | # If the REFERENCES_RELATION tag is set to YES (the default) | |
574 | # then for each documented function all documented entities | |
575 | # called/used by that function will be listed. | |
576 | ||
577 | REFERENCES_RELATION = YES | |
578 | ||
579 | # If the REFERENCES_LINK_SOURCE tag is set to YES (the default) | |
580 | # and SOURCE_BROWSER tag is set to YES, then the hyperlinks from | |
581 | # functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will | |
582 | # link to the source code. Otherwise they will link to the documentstion. | |
583 | ||
584 | REFERENCES_LINK_SOURCE = YES | |
585 | ||
586 | # If the USE_HTAGS tag is set to YES then the references to source code | |
587 | # will point to the HTML generated by the htags(1) tool instead of doxygen | |
588 | # built-in source browser. The htags tool is part of GNU's global source | |
589 | # tagging system (see http://www.gnu.org/software/global/global.html). You | |
590 | # will need version 4.8.6 or higher. | |
591 | ||
592 | USE_HTAGS = NO | |
593 | ||
594 | # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen | |
595 | # will generate a verbatim copy of the header file for each class for | |
596 | # which an include is specified. Set to NO to disable this. | |
597 | ||
598 | VERBATIM_HEADERS = YES | |
599 | ||
600 | #--------------------------------------------------------------------------- | |
601 | # configuration options related to the alphabetical class index | |
602 | #--------------------------------------------------------------------------- | |
603 | ||
604 | # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index | |
605 | # of all compounds will be generated. Enable this if the project | |
606 | # contains a lot of classes, structs, unions or interfaces. | |
607 | ||
608 | ALPHABETICAL_INDEX = NO | |
609 | ||
610 | # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then | |
611 | # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns | |
612 | # in which this list will be split (can be a number in the range [1..20]) | |
613 | ||
614 | COLS_IN_ALPHA_INDEX = 5 | |
615 | ||
616 | # In case all classes in a project start with a common prefix, all | |
617 | # classes will be put under the same header in the alphabetical index. | |
618 | # The IGNORE_PREFIX tag can be used to specify one or more prefixes that | |
619 | # should be ignored while generating the index headers. | |
620 | ||
621 | IGNORE_PREFIX = | |
622 | ||
623 | #--------------------------------------------------------------------------- | |
624 | # configuration options related to the HTML output | |
625 | #--------------------------------------------------------------------------- | |
626 | ||
627 | # If the GENERATE_HTML tag is set to YES (the default) Doxygen will | |
628 | # generate HTML output. | |
629 | ||
630 | GENERATE_HTML = YES | |
631 | ||
632 | # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. | |
633 | # If a relative path is entered the value of OUTPUT_DIRECTORY will be | |
634 | # put in front of it. If left blank `html' will be used as the default path. | |
635 | ||
636 | HTML_OUTPUT = html | |
637 | ||
638 | # The HTML_FILE_EXTENSION tag can be used to specify the file extension for | |
639 | # each generated HTML page (for example: .htm,.php,.asp). If it is left blank | |
640 | # doxygen will generate files with .html extension. | |
641 | ||
642 | HTML_FILE_EXTENSION = .html | |
643 | ||
644 | # The HTML_HEADER tag can be used to specify a personal HTML header for | |
645 | # each generated HTML page. If it is left blank doxygen will generate a | |
646 | # standard header. | |
647 | ||
648 | #HTML_HEADER = @top_srcdir@/doc/header.html | |
649 | ||
650 | # The HTML_FOOTER tag can be used to specify a personal HTML footer for | |
651 | # each generated HTML page. If it is left blank doxygen will generate a | |
652 | # standard footer. | |
653 | ||
654 | HTML_FOOTER = | |
655 | ||
656 | # The HTML_STYLESHEET tag can be used to specify a user-defined cascading | |
657 | # style sheet that is used by each HTML page. It can be used to | |
658 | # fine-tune the look of the HTML output. If the tag is left blank doxygen | |
659 | # will generate a default style sheet. Note that doxygen will try to copy | |
660 | # the style sheet file to the HTML output directory, so don't put your own | |
661 | # stylesheet in the HTML output directory as well, or it will be erased! | |
662 | ||
663 | HTML_STYLESHEET = | |
664 | ||
665 | # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, | |
666 | # files or namespaces will be aligned in HTML using tables. If set to | |
667 | # NO a bullet list will be used. | |
668 | ||
669 | HTML_ALIGN_MEMBERS = YES | |
670 | ||
671 | # If the GENERATE_HTMLHELP tag is set to YES, additional index files | |
672 | # will be generated that can be used as input for tools like the | |
673 | # Microsoft HTML help workshop to generate a compressed HTML help file (.chm) | |
674 | # of the generated HTML documentation. | |
675 | ||
676 | GENERATE_HTMLHELP = NO | |
677 | ||
678 | # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can | |
679 | # be used to specify the file name of the resulting .chm file. You | |
680 | # can add a path in front of the file if the result should not be | |
681 | # written to the html output directory. | |
682 | ||
683 | CHM_FILE = | |
684 | ||
685 | # If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can | |
686 | # be used to specify the location (absolute path including file name) of | |
687 | # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run | |
688 | # the HTML help compiler on the generated index.hhp. | |
689 | ||
690 | HHC_LOCATION = | |
691 | ||
692 | # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag | |
693 | # controls if a separate .chi index file is generated (YES) or that | |
694 | # it should be included in the master .chm file (NO). | |
695 | ||
696 | GENERATE_CHI = NO | |
697 | ||
698 | # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag | |
699 | # controls whether a binary table of contents is generated (YES) or a | |
700 | # normal table of contents (NO) in the .chm file. | |
701 | ||
702 | BINARY_TOC = NO | |
703 | ||
704 | # The TOC_EXPAND flag can be set to YES to add extra items for group members | |
705 | # to the contents of the HTML help documentation and to the tree view. | |
706 | ||
707 | TOC_EXPAND = NO | |
708 | ||
709 | # The DISABLE_INDEX tag can be used to turn on/off the condensed index at | |
710 | # top of each HTML page. The value NO (the default) enables the index and | |
711 | # the value YES disables it. | |
712 | ||
713 | DISABLE_INDEX = NO | |
714 | ||
715 | # This tag can be used to set the number of enum values (range [1..20]) | |
716 | # that doxygen will group on one line in the generated HTML documentation. | |
717 | ||
718 | ENUM_VALUES_PER_LINE = 4 | |
719 | ||
720 | # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be | |
721 | # generated containing a tree-like index structure (just like the one that | |
722 | # is generated for HTML Help). For this to work a browser that supports | |
723 | # JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+, | |
724 | # Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are | |
725 | # probably better off using the HTML help feature. | |
726 | ||
727 | GENERATE_TREEVIEW = NO | |
728 | ||
729 | # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be | |
730 | # used to set the initial width (in pixels) of the frame in which the tree | |
731 | # is shown. | |
732 | ||
733 | TREEVIEW_WIDTH = 250 | |
734 | ||
735 | #--------------------------------------------------------------------------- | |
736 | # configuration options related to the LaTeX output | |
737 | #--------------------------------------------------------------------------- | |
738 | ||
739 | # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will | |
740 | # generate Latex output. | |
741 | ||
742 | GENERATE_LATEX = NO | |
743 | ||
744 | # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. | |
745 | # If a relative path is entered the value of OUTPUT_DIRECTORY will be | |
746 | # put in front of it. If left blank `latex' will be used as the default path. | |
747 | ||
748 | LATEX_OUTPUT = latex | |
749 | ||
750 | # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be | |
751 | # invoked. If left blank `latex' will be used as the default command name. | |
752 | ||
753 | LATEX_CMD_NAME = latex | |
754 | ||
755 | # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to | |
756 | # generate index for LaTeX. If left blank `makeindex' will be used as the | |
757 | # default command name. | |
758 | ||
759 | MAKEINDEX_CMD_NAME = makeindex | |
760 | ||
761 | # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact | |
762 | # LaTeX documents. This may be useful for small projects and may help to | |
763 | # save some trees in general. | |
764 | ||
765 | COMPACT_LATEX = NO | |
766 | ||
767 | # The PAPER_TYPE tag can be used to set the paper type that is used | |
768 | # by the printer. Possible values are: a4, a4wide, letter, legal and | |
769 | # executive. If left blank a4wide will be used. | |
770 | ||
771 | PAPER_TYPE = a4wide | |
772 | ||
773 | # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX | |
774 | # packages that should be included in the LaTeX output. | |
775 | ||
776 | EXTRA_PACKAGES = | |
777 | ||
778 | # The LATEX_HEADER tag can be used to specify a personal LaTeX header for | |
779 | # the generated latex document. The header should contain everything until | |
780 | # the first chapter. If it is left blank doxygen will generate a | |
781 | # standard header. Notice: only use this tag if you know what you are doing! | |
782 | ||
783 | LATEX_HEADER = | |
784 | ||
785 | # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated | |
786 | # is prepared for conversion to pdf (using ps2pdf). The pdf file will | |
787 | # contain links (just like the HTML output) instead of page references | |
788 | # This makes the output suitable for online browsing using a pdf viewer. | |
789 | ||
790 | PDF_HYPERLINKS = NO | |
791 | ||
792 | # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of | |
793 | # plain latex in the generated Makefile. Set this option to YES to get a | |
794 | # higher quality PDF documentation. | |
795 | ||
796 | USE_PDFLATEX = NO | |
797 | ||
798 | # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. | |
799 | # command to the generated LaTeX files. This will instruct LaTeX to keep | |
800 | # running if errors occur, instead of asking the user for help. | |
801 | # This option is also used when generating formulas in HTML. | |
802 | ||
803 | LATEX_BATCHMODE = NO | |
804 | ||
805 | # If LATEX_HIDE_INDICES is set to YES then doxygen will not | |
806 | # include the index chapters (such as File Index, Compound Index, etc.) | |
807 | # in the output. | |
808 | ||
809 | LATEX_HIDE_INDICES = NO | |
810 | ||
811 | #--------------------------------------------------------------------------- | |
812 | # configuration options related to the RTF output | |
813 | #--------------------------------------------------------------------------- | |
814 | ||
815 | # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output | |
816 | # The RTF output is optimized for Word 97 and may not look very pretty with | |
817 | # other RTF readers or editors. | |
818 | ||
819 | GENERATE_RTF = NO | |
820 | ||
821 | # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. | |
822 | # If a relative path is entered the value of OUTPUT_DIRECTORY will be | |
823 | # put in front of it. If left blank `rtf' will be used as the default path. | |
824 | ||
825 | RTF_OUTPUT = rtf | |
826 | ||
827 | # If the COMPACT_RTF tag is set to YES Doxygen generates more compact | |
828 | # RTF documents. This may be useful for small projects and may help to | |
829 | # save some trees in general. | |
830 | ||
831 | COMPACT_RTF = NO | |
832 | ||
833 | # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated | |
834 | # will contain hyperlink fields. The RTF file will | |
835 | # contain links (just like the HTML output) instead of page references. | |
836 | # This makes the output suitable for online browsing using WORD or other | |
837 | # programs which support those fields. | |
838 | # Note: wordpad (write) and others do not support links. | |
839 | ||
840 | RTF_HYPERLINKS = NO | |
841 | ||
842 | # Load stylesheet definitions from file. Syntax is similar to doxygen's | |
843 | # config file, i.e. a series of assignments. You only have to provide | |
844 | # replacements, missing definitions are set to their default value. | |
845 | ||
846 | RTF_STYLESHEET_FILE = | |
847 | ||
848 | # Set optional variables used in the generation of an rtf document. | |
849 | # Syntax is similar to doxygen's config file. | |
850 | ||
851 | RTF_EXTENSIONS_FILE = | |
852 | ||
853 | #--------------------------------------------------------------------------- | |
854 | # configuration options related to the man page output | |
855 | #--------------------------------------------------------------------------- | |
856 | ||
857 | # If the GENERATE_MAN tag is set to YES (the default) Doxygen will | |
858 | # generate man pages | |
859 | ||
860 | GENERATE_MAN = NO | |
861 | ||
862 | # The MAN_OUTPUT tag is used to specify where the man pages will be put. | |
863 | # If a relative path is entered the value of OUTPUT_DIRECTORY will be | |
864 | # put in front of it. If left blank `man' will be used as the default path. | |
865 | ||
866 | MAN_OUTPUT = man | |
867 | ||
868 | # The MAN_EXTENSION tag determines the extension that is added to | |
869 | # the generated man pages (default is the subroutine's section .3) | |
870 | ||
871 | MAN_EXTENSION = .3 | |
872 | ||
873 | # If the MAN_LINKS tag is set to YES and Doxygen generates man output, | |
874 | # then it will generate one additional man file for each entity | |
875 | # documented in the real man page(s). These additional files | |
876 | # only source the real man page, but without them the man command | |
877 | # would be unable to find the correct page. The default is NO. | |
878 | ||
879 | MAN_LINKS = NO | |
880 | ||
881 | #--------------------------------------------------------------------------- | |
882 | # configuration options related to the XML output | |
883 | #--------------------------------------------------------------------------- | |
884 | ||
885 | # If the GENERATE_XML tag is set to YES Doxygen will | |
886 | # generate an XML file that captures the structure of | |
887 | # the code including all documentation. | |
888 | ||
889 | GENERATE_XML = NO | |
890 | ||
891 | # The XML_OUTPUT tag is used to specify where the XML pages will be put. | |
892 | # If a relative path is entered the value of OUTPUT_DIRECTORY will be | |
893 | # put in front of it. If left blank `xml' will be used as the default path. | |
894 | ||
895 | XML_OUTPUT = xml | |
896 | ||
897 | # The XML_SCHEMA tag can be used to specify an XML schema, | |
898 | # which can be used by a validating XML parser to check the | |
899 | # syntax of the XML files. | |
900 | ||
901 | XML_SCHEMA = | |
902 | ||
903 | # The XML_DTD tag can be used to specify an XML DTD, | |
904 | # which can be used by a validating XML parser to check the | |
905 | # syntax of the XML files. | |
906 | ||
907 | XML_DTD = | |
908 | ||
909 | # If the XML_PROGRAMLISTING tag is set to YES Doxygen will | |
910 | # dump the program listings (including syntax highlighting | |
911 | # and cross-referencing information) to the XML output. Note that | |
912 | # enabling this will significantly increase the size of the XML output. | |
913 | ||
914 | XML_PROGRAMLISTING = YES | |
915 | ||
916 | #--------------------------------------------------------------------------- | |
917 | # configuration options for the AutoGen Definitions output | |
918 | #--------------------------------------------------------------------------- | |
919 | ||
920 | # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will | |
921 | # generate an AutoGen Definitions (see autogen.sf.net) file | |
922 | # that captures the structure of the code including all | |
923 | # documentation. Note that this feature is still experimental | |
924 | # and incomplete at the moment. | |
925 | ||
926 | GENERATE_AUTOGEN_DEF = NO | |
927 | ||
928 | #--------------------------------------------------------------------------- | |
929 | # configuration options related to the Perl module output | |
930 | #--------------------------------------------------------------------------- | |
931 | ||
932 | # If the GENERATE_PERLMOD tag is set to YES Doxygen will | |
933 | # generate a Perl module file that captures the structure of | |
934 | # the code including all documentation. Note that this | |
935 | # feature is still experimental and incomplete at the | |
936 | # moment. | |
937 | ||
938 | GENERATE_PERLMOD = NO | |
939 | ||
940 | # If the PERLMOD_LATEX tag is set to YES Doxygen will generate | |
941 | # the necessary Makefile rules, Perl scripts and LaTeX code to be able | |
942 | # to generate PDF and DVI output from the Perl module output. | |
943 | ||
944 | PERLMOD_LATEX = NO | |
945 | ||
946 | # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be | |
947 | # nicely formatted so it can be parsed by a human reader. This is useful | |
948 | # if you want to understand what is going on. On the other hand, if this | |
949 | # tag is set to NO the size of the Perl module output will be much smaller | |
950 | # and Perl will parse it just the same. | |
951 | ||
952 | PERLMOD_PRETTY = YES | |
953 | ||
954 | # The names of the make variables in the generated doxyrules.make file | |
955 | # are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. | |
956 | # This is useful so different doxyrules.make files included by the same | |
957 | # Makefile don't overwrite each other's variables. | |
958 | ||
959 | PERLMOD_MAKEVAR_PREFIX = | |
960 | ||
961 | #--------------------------------------------------------------------------- | |
962 | # Configuration options related to the preprocessor | |
963 | #--------------------------------------------------------------------------- | |
964 | ||
965 | # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will | |
966 | # evaluate all C-preprocessor directives found in the sources and include | |
967 | # files. | |
968 | ||
969 | ENABLE_PREPROCESSING = YES | |
970 | ||
971 | # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro | |
972 | # names in the source code. If set to NO (the default) only conditional | |
973 | # compilation will be performed. Macro expansion can be done in a controlled | |
974 | # way by setting EXPAND_ONLY_PREDEF to YES. | |
975 | ||
976 | MACRO_EXPANSION = NO | |
977 | ||
978 | # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES | |
979 | # then the macro expansion is limited to the macros specified with the | |
980 | # PREDEFINED and EXPAND_AS_DEFINED tags. | |
981 | ||
982 | EXPAND_ONLY_PREDEF = NO | |
983 | ||
984 | # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files | |
985 | # in the INCLUDE_PATH (see below) will be search if a #include is found. | |
986 | ||
987 | SEARCH_INCLUDES = YES | |
988 | ||
989 | # The INCLUDE_PATH tag can be used to specify one or more directories that | |
990 | # contain include files that are not input files but should be processed by | |
991 | # the preprocessor. | |
992 | ||
993 | INCLUDE_PATH = | |
994 | ||
995 | # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard | |
996 | # patterns (like *.h and *.hpp) to filter out the header-files in the | |
997 | # directories. If left blank, the patterns specified with FILE_PATTERNS will | |
998 | # be used. | |
999 | ||
1000 | INCLUDE_FILE_PATTERNS = | |
1001 | ||
1002 | # The PREDEFINED tag can be used to specify one or more macro names that | |
1003 | # are defined before the preprocessor is started (similar to the -D option of | |
1004 | # gcc). The argument of the tag is a list of macros of the form: name | |
1005 | # or name=definition (no spaces). If the definition and the = are | |
1006 | # omitted =1 is assumed. To prevent a macro definition from being | |
1007 | # undefined via #undef or recursively expanded use the := operator | |
1008 | # instead of the = operator. | |
1009 | ||
1010 | PREDEFINED = __GCCXML__ | |
1011 | ||
1012 | # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then | |
1013 | # this tag can be used to specify a list of macro names that should be expanded. | |
1014 | # The macro definition that is found in the sources will be used. | |
1015 | # Use the PREDEFINED tag if you want to use a different macro definition. | |
1016 | ||
1017 | EXPAND_AS_DEFINED = | |
1018 | ||
1019 | # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then | |
1020 | # doxygen's preprocessor will remove all function-like macros that are alone | |
1021 | # on a line, have an all uppercase name, and do not end with a semicolon. Such | |
1022 | # function macros are typically used for boiler-plate code, and will confuse | |
1023 | # the parser if not removed. | |
1024 | ||
1025 | SKIP_FUNCTION_MACROS = YES | |
1026 | ||
1027 | #--------------------------------------------------------------------------- | |
1028 | # Configuration::additions related to external references | |
1029 | #--------------------------------------------------------------------------- | |
1030 | ||
1031 | # The TAGFILES option can be used to specify one or more tagfiles. | |
1032 | # Optionally an initial location of the external documentation | |
1033 | # can be added for each tagfile. The format of a tag file without | |
1034 | # this location is as follows: | |
1035 | # TAGFILES = file1 file2 ... | |
1036 | # Adding location for the tag files is done as follows: | |
1037 | # TAGFILES = file1=loc1 "file2 = loc2" ... | |
1038 | # where "loc1" and "loc2" can be relative or absolute paths or | |
1039 | # URLs. If a location is present for each tag, the installdox tool | |
1040 | # does not have to be run to correct the links. | |
1041 | # Note that each tag file must have a unique name | |
1042 | # (where the name does NOT include the path) | |
1043 | # If a tag file is not located in the directory in which doxygen | |
1044 | # is run, you must also specify the path to the tagfile here. | |
1045 | ||
1046 | TAGFILES = | |
1047 | ||
1048 | # When a file name is specified after GENERATE_TAGFILE, doxygen will create | |
1049 | # a tag file that is based on the input files it reads. | |
1050 | ||
1051 | # GENERATE_TAGFILE = libt2n.tag | |
1052 | ||
1053 | # If the ALLEXTERNALS tag is set to YES all external classes will be listed | |
1054 | # in the class index. If set to NO only the inherited external classes | |
1055 | # will be listed. | |
1056 | ||
1057 | ALLEXTERNALS = NO | |
1058 | ||
1059 | # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed | |
1060 | # in the modules index. If set to NO, only the current project's groups will | |
1061 | # be listed. | |
1062 | ||
1063 | EXTERNAL_GROUPS = YES | |
1064 | ||
1065 | # The PERL_PATH should be the absolute path and name of the perl script | |
1066 | # interpreter (i.e. the result of `which perl'). | |
1067 | ||
1068 | PERL_PATH = /usr/bin/perl | |
1069 | ||
1070 | #--------------------------------------------------------------------------- | |
1071 | # Configuration options related to the dot tool | |
1072 | #--------------------------------------------------------------------------- | |
1073 | ||
1074 | # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will | |
1075 | # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base | |
1076 | # or super classes. Setting the tag to NO turns the diagrams off. Note that | |
1077 | # this option is superseded by the HAVE_DOT option below. This is only a | |
1078 | # fallback. It is recommended to install and use dot, since it yields more | |
1079 | # powerful graphs. | |
1080 | ||
1081 | CLASS_DIAGRAMS = YES | |
1082 | ||
1083 | # If set to YES, the inheritance and collaboration graphs will hide | |
1084 | # inheritance and usage relations if the target is undocumented | |
1085 | # or is not a class. | |
1086 | ||
1087 | HIDE_UNDOC_RELATIONS = YES | |
1088 | ||
1089 | # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is | |
1090 | # available from the path. This tool is part of Graphviz, a graph visualization | |
1091 | # toolkit from AT&T and Lucent Bell Labs. The other options in this section | |
1092 | # have no effect if this option is set to NO (the default) | |
1093 | ||
1094 | HAVE_DOT = YES | |
1095 | ||
1096 | # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen | |
1097 | # will generate a graph for each documented class showing the direct and | |
1098 | # indirect inheritance relations. Setting this tag to YES will force the | |
1099 | # the CLASS_DIAGRAMS tag to NO. | |
1100 | ||
1101 | CLASS_GRAPH = YES | |
1102 | ||
1103 | # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen | |
1104 | # will generate a graph for each documented class showing the direct and | |
1105 | # indirect implementation dependencies (inheritance, containment, and | |
1106 | # class references variables) of the class with other documented classes. | |
1107 | ||
1108 | COLLABORATION_GRAPH = NO | |
1109 | ||
1110 | # If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen | |
1111 | # will generate a graph for groups, showing the direct groups dependencies | |
1112 | ||
1113 | GROUP_GRAPHS = YES | |
1114 | ||
1115 | # If the UML_LOOK tag is set to YES doxygen will generate inheritance and | |
1116 | # collaboration diagrams in a style similar to the OMG's Unified Modeling | |
1117 | # Language. | |
1118 | ||
1119 | UML_LOOK = YES | |
1120 | ||
1121 | # If set to YES, the inheritance and collaboration graphs will show the | |
1122 | # relations between templates and their instances. | |
1123 | ||
1124 | TEMPLATE_RELATIONS = YES | |
1125 | ||
1126 | # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT | |
1127 | # tags are set to YES then doxygen will generate a graph for each documented | |
1128 | # file showing the direct and indirect include dependencies of the file with | |
1129 | # other documented files. | |
1130 | ||
1131 | INCLUDE_GRAPH = YES | |
1132 | ||
1133 | # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and | |
1134 | # HAVE_DOT tags are set to YES then doxygen will generate a graph for each | |
1135 | # documented header file showing the documented files that directly or | |
1136 | # indirectly include this file. | |
1137 | ||
1138 | INCLUDED_BY_GRAPH = YES | |
1139 | ||
1140 | # If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will | |
1141 | # generate a call dependency graph for every global function or class method. | |
1142 | # Note that enabling this option will significantly increase the time of a run. | |
1143 | # So in most cases it will be better to enable call graphs for selected | |
1144 | # functions only using the \callgraph command. | |
1145 | ||
1146 | CALL_GRAPH = NO | |
1147 | ||
1148 | # If the CALLER_GRAPH and HAVE_DOT tags are set to YES then doxygen will | |
1149 | # generate a caller dependency graph for every global function or class method. | |
1150 | # Note that enabling this option will significantly increase the time of a run. | |
1151 | # So in most cases it will be better to enable caller graphs for selected | |
1152 | # functions only using the \callergraph command. | |
1153 | ||
1154 | CALLER_GRAPH = NO | |
1155 | ||
1156 | # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen | |
1157 | # will graphical hierarchy of all classes instead of a textual one. | |
1158 | ||
1159 | GRAPHICAL_HIERARCHY = YES | |
1160 | ||
1161 | # If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES | |
1162 | # then doxygen will show the dependencies a directory has on other directories | |
1163 | # in a graphical way. The dependency relations are determined by the #include | |
1164 | # relations between the files in the directories. | |
1165 | ||
1166 | DIRECTORY_GRAPH = YES | |
1167 | ||
1168 | # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images | |
1169 | # generated by dot. Possible values are png, jpg, or gif | |
1170 | # If left blank png will be used. | |
1171 | ||
1172 | DOT_IMAGE_FORMAT = png | |
1173 | ||
1174 | # The tag DOT_PATH can be used to specify the path where the dot tool can be | |
1175 | # found. If left blank, it is assumed the dot tool can be found in the path. | |
1176 | ||
1177 | DOT_PATH = | |
1178 | ||
1179 | # The DOTFILE_DIRS tag can be used to specify one or more directories that | |
1180 | # contain dot files that are included in the documentation (see the | |
1181 | # \dotfile command). | |
1182 | ||
1183 | DOTFILE_DIRS = | |
1184 | ||
1185 | # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the | |
1186 | # graphs generated by dot. A depth value of 3 means that only nodes reachable | |
1187 | # from the root by following a path via at most 3 edges will be shown. Nodes | |
1188 | # that lay further from the root node will be omitted. Note that setting this | |
1189 | # option to 1 or 2 may greatly reduce the computation time needed for large | |
1190 | # code bases. Also note that a graph may be further truncated if the graph's | |
1191 | # image dimensions are not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH | |
1192 | # and MAX_DOT_GRAPH_HEIGHT). If 0 is used for the depth value (the default), | |
1193 | # the graph is not depth-constrained. | |
1194 | ||
1195 | MAX_DOT_GRAPH_DEPTH = 0 | |
1196 | ||
1197 | # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent | |
1198 | # background. This is disabled by default, which results in a white background. | |
1199 | # Warning: Depending on the platform used, enabling this option may lead to | |
1200 | # badly anti-aliased labels on the edges of a graph (i.e. they become hard to | |
1201 | # read). | |
1202 | ||
1203 | DOT_TRANSPARENT = NO | |
1204 | ||
1205 | # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output | |
1206 | # files in one run (i.e. multiple -o and -T options on the command line). This | |
1207 | # makes dot run faster, but since only newer versions of dot (>1.8.10) | |
1208 | # support this, this feature is disabled by default. | |
1209 | ||
1210 | DOT_MULTI_TARGETS = NO | |
1211 | ||
1212 | # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will | |
1213 | # generate a legend page explaining the meaning of the various boxes and | |
1214 | # arrows in the dot generated graphs. | |
1215 | ||
1216 | GENERATE_LEGEND = YES | |
1217 | ||
1218 | # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will | |
1219 | # remove the intermediate dot files that are used to generate | |
1220 | # the various graphs. | |
1221 | ||
1222 | DOT_CLEANUP = YES | |
1223 | ||
1224 | #--------------------------------------------------------------------------- | |
1225 | # Configuration::additions related to the search engine | |
1226 | #--------------------------------------------------------------------------- | |
1227 | ||
1228 | # The SEARCHENGINE tag specifies whether or not a search engine should be | |
1229 | # used. If set to NO the values of all tags below this one will be ignored. | |
1230 | ||
1231 | SEARCHENGINE = NO |