source: rtems/cpukit/Doxyfile.in @ bdd4eb8

Last change on this file since bdd4eb8 was addeb53a, checked in by Chris Johns <chrisj@…>, on Oct 11, 2017 at 11:36:42 PM

doxygen: Set the Latex generation default to NO.

Closes #3130.

  • Property mode set to 100644
File size: 64.5 KB
Line 
1# Doxyfile 1.6.2-20100208
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# This tag specifies the encoding used for all characters in the config file
18# that follow. The default is UTF-8 which is also the encoding used for all
19# text before the first occurrence of this tag. Doxygen uses libiconv (or the
20# iconv built into libc) for the transcoding. See
21# http://www.gnu.org/software/libiconv for the list of possible encodings.
22
23DOXYFILE_ENCODING      = UTF-8
24
25# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
26# by quotes) that should identify the project.
27
28PROJECT_NAME           = "RTEMS CPU Kit with SuperCore"
29
30# The PROJECT_NUMBER tag can be used to enter a project or revision number.
31# This could be handy for archiving the generated documentation or
32# if some version control system is used.
33
34PROJECT_NUMBER         = @PACKAGE_VERSION@
35
36# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
37# base path where the generated documentation will be put.
38# If a relative path is entered, it will be relative to the location
39# where doxygen was started. If left blank the current directory will be used.
40
41OUTPUT_DIRECTORY       = cpukit_doxy
42
43# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
44# 4096 sub-directories (in 2 levels) under the output directory of each output
45# format and will distribute the generated files over these directories.
46# Enabling this option can be useful when feeding doxygen a huge amount of
47# source files, where putting all generated files in the same directory would
48# otherwise cause performance problems for the file system.
49
50CREATE_SUBDIRS         = NO
51
52# The OUTPUT_LANGUAGE tag is used to specify the language in which all
53# documentation generated by doxygen is written. Doxygen will use this
54# information to generate all constant output in the proper language.
55# The default language is English, other supported languages are:
56# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,
57# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German,
58# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English
59# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian,
60# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrilic, Slovak,
61# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.
62
63OUTPUT_LANGUAGE        = English
64
65# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
66# include brief member descriptions after the members that are listed in
67# the file and class documentation (similar to JavaDoc).
68# Set to NO to disable this.
69
70BRIEF_MEMBER_DESC      = YES
71
72# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
73# the brief description of a member or function before the detailed description.
74# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
75# brief descriptions will be completely suppressed.
76
77REPEAT_BRIEF           = YES
78
79# This tag implements a quasi-intelligent brief description abbreviator
80# that is used to form the text in various listings. Each string
81# in this list, if found as the leading text of the brief description, will be
82# stripped from the text and the result after processing the whole list, is
83# used as the annotated text. Otherwise, the brief description is used as-is.
84# If left blank, the following values are used ("$name" is automatically
85# replaced with the name of the entity): "The $name class" "The $name widget"
86# "The $name file" "is" "provides" "specifies" "contains"
87# "represents" "a" "an" "the"
88
89ABBREVIATE_BRIEF       =
90
91# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
92# Doxygen will generate a detailed section even if there is only a brief
93# description.
94
95ALWAYS_DETAILED_SEC    = NO
96
97# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
98# inherited members of a class in the documentation of that class as if those
99# members were ordinary class members. Constructors, destructors and assignment
100# operators of the base classes will not be shown.
101
102INLINE_INHERITED_MEMB  = NO
103
104# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
105# path before files name in the file list and in the header files. If set
106# to NO the shortest path that makes the file name unique will be used.
107
108FULL_PATH_NAMES        = YES
109
110# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
111# can be used to strip a user-defined part of the path. Stripping is
112# only done if one of the specified strings matches the left-hand part of
113# the path. The tag can be used to show relative paths in the file list.
114# If left blank the directory from which doxygen is run is used as the
115# path to strip.
116
117STRIP_FROM_PATH        = ../lib/include
118
119# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
120# the path mentioned in the documentation of a class, which tells
121# the reader which header file to include in order to use a class.
122# If left blank only the name of the header file containing the class
123# definition is used. Otherwise one should specify the include paths that
124# are normally passed to the compiler using the -I flag.
125
126STRIP_FROM_INC_PATH    =
127
128# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
129# (but less readable) file names. This can be useful is your file systems
130# doesn't support long names like on DOS, Mac, or CD-ROM.
131
132SHORT_NAMES            = NO
133
134# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
135# will interpret the first line (until the first dot) of a JavaDoc-style
136# comment as the brief description. If set to NO, the JavaDoc
137# comments will behave just like regular Qt-style comments
138# (thus requiring an explicit @brief command for a brief description.)
139
140JAVADOC_AUTOBRIEF      = YES
141
142# If the QT_AUTOBRIEF tag is set to YES then Doxygen will
143# interpret the first line (until the first dot) of a Qt-style
144# comment as the brief description. If set to NO, the comments
145# will behave just like regular Qt-style comments (thus requiring
146# an explicit \brief command for a brief description.)
147
148QT_AUTOBRIEF           = YES
149
150# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
151# treat a multi-line C++ special comment block (i.e. a block of //! or ///
152# comments) as a brief description. This used to be the default behaviour.
153# The new default is to treat a multi-line C++ comment block as a detailed
154# description. Set this tag to YES if you prefer the old behaviour instead.
155
156MULTILINE_CPP_IS_BRIEF = NO
157
158# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
159# member inherits the documentation from any documented member that it
160# re-implements.
161
162INHERIT_DOCS           = YES
163
164# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
165# a new page for each member. If set to NO, the documentation of a member will
166# be part of the file/class/namespace that contains it.
167
168SEPARATE_MEMBER_PAGES  = NO
169
170# The TAB_SIZE tag can be used to set the number of spaces in a tab.
171# Doxygen uses this value to replace tabs by spaces in code fragments.
172
173TAB_SIZE               = 8
174
175# This tag can be used to specify a number of aliases that acts
176# as commands in the documentation. An alias has the form "name=value".
177# For example adding "sideeffect=\par Side Effects:\n" will allow you to
178# put the command \sideeffect (or @sideeffect) in the documentation, which
179# will result in a user-defined paragraph with heading "Side Effects:".
180# You can put \n's in the value part of an alias to insert newlines.
181
182ALIASES                =
183
184# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
185# sources only. Doxygen will then generate output that is more tailored for C.
186# For instance, some of the names that are used will be different. The list
187# of all members will be omitted, etc.
188
189OPTIMIZE_OUTPUT_FOR_C  = YES
190
191# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java
192# sources only. Doxygen will then generate output that is more tailored for
193# Java. For instance, namespaces will be presented as packages, qualified
194# scopes will look different, etc.
195
196OPTIMIZE_OUTPUT_JAVA   = NO
197
198# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
199# sources only. Doxygen will then generate output that is more tailored for
200# Fortran.
201
202OPTIMIZE_FOR_FORTRAN   = NO
203
204# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
205# sources. Doxygen will then generate output that is tailored for
206# VHDL.
207
208OPTIMIZE_OUTPUT_VHDL   = NO
209
210# Doxygen selects the parser to use depending on the extension of the files it parses.
211# With this tag you can assign which parser to use for a given extension.
212# Doxygen has a built-in mapping, but you can override or extend it using this tag.
213# The format is ext=language, where ext is a file extension, and language is one of
214# the parsers supported by doxygen: IDL, Java, Javascript, C#, C, C++, D, PHP,
215# Objective-C, Python, Fortran, VHDL, C, C++. For instance to make doxygen treat
216# .inc files as Fortran files (default is PHP), and .f files as C (default is Fortran),
217# use: inc=Fortran f=C. Note that for custom extensions you also need to set FILE_PATTERNS otherwise the files are not read by doxygen.
218
219EXTENSION_MAPPING      =
220
221# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
222# to include (a tag file for) the STL sources as input, then you should
223# set this tag to YES in order to let doxygen match functions declarations and
224# definitions whose arguments contain STL classes (e.g. func(std::string); v.s.
225# func(std::string) {}). This also make the inheritance and collaboration
226# diagrams that involve STL classes more complete and accurate.
227
228BUILTIN_STL_SUPPORT    = NO
229
230# If you use Microsoft's C++/CLI language, you should set this option to YES to
231# enable parsing support.
232
233CPP_CLI_SUPPORT        = NO
234
235# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only.
236# Doxygen will parse them like normal C++ but will assume all classes use public
237# instead of private inheritance when no explicit protection keyword is present.
238
239SIP_SUPPORT            = NO
240
241# For Microsoft's IDL there are propget and propput attributes to indicate getter
242# and setter methods for a property. Setting this option to YES (the default)
243# will make doxygen to replace the get and set methods by a property in the
244# documentation. This will only work if the methods are indeed getting or
245# setting a simple type. If this is not the case, or you want to show the
246# methods anyway, you should set this option to NO.
247
248IDL_PROPERTY_SUPPORT   = YES
249
250# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
251# tag is set to YES, then doxygen will reuse the documentation of the first
252# member in the group (if any) for the other members of the group. By default
253# all members of a group must be documented explicitly.
254
255DISTRIBUTE_GROUP_DOC   = NO
256
257# Set the SUBGROUPING tag to YES (the default) to allow class member groups of
258# the same type (for instance a group of public functions) to be put as a
259# subgroup of that type (e.g. under the Public Functions section). Set it to
260# NO to prevent subgrouping. Alternatively, this can be done per class using
261# the \nosubgrouping command.
262
263SUBGROUPING            = YES
264
265# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum
266# is documented as struct, union, or enum with the name of the typedef. So
267# typedef struct TypeS {} TypeT, will appear in the documentation as a struct
268# with name TypeT. When disabled the typedef will appear as a member of a file,
269# namespace, or class. And the struct will be named TypeS. This can typically
270# be useful for C code in case the coding convention dictates that all compound
271# types are typedef'ed and only the typedef is referenced, never the tag name.
272
273TYPEDEF_HIDES_STRUCT   = NO
274
275# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to
276# determine which symbols to keep in memory and which to flush to disk.
277# When the cache is full, less often used symbols will be written to disk.
278# For small to medium size projects (<1000 input files) the default value is
279# probably good enough. For larger projects a too small cache size can cause
280# doxygen to be busy swapping symbols to and from disk most of the time
281# causing a significant performance penality.
282# If the system has enough physical memory increasing the cache will improve the
283# performance by keeping more symbols in memory. Note that the value works on
284# a logarithmic scale so increasing the size by one will rougly double the
285# memory usage. The cache size is given by this formula:
286# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,
287# corresponding to a cache size of 2^16 = 65536 symbols
288
289SYMBOL_CACHE_SIZE      = 0
290
291#---------------------------------------------------------------------------
292# Build related configuration options
293#---------------------------------------------------------------------------
294
295# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
296# documentation are documented, even if no documentation was available.
297# Private class members and static file members will be hidden unless
298# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
299
300EXTRACT_ALL            = NO
301
302# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
303# will be included in the documentation.
304
305EXTRACT_PRIVATE        = NO
306
307# If the EXTRACT_STATIC tag is set to YES all static members of a file
308# will be included in the documentation.
309
310EXTRACT_STATIC         = NO
311
312# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
313# defined locally in source files will be included in the documentation.
314# If set to NO only classes defined in header files are included.
315
316EXTRACT_LOCAL_CLASSES  = YES
317
318# This flag is only useful for Objective-C code. When set to YES local
319# methods, which are defined in the implementation section but not in
320# the interface are included in the documentation.
321# If set to NO (the default) only methods in the interface are included.
322
323EXTRACT_LOCAL_METHODS  = NO
324
325# If this flag is set to YES, the members of anonymous namespaces will be
326# extracted and appear in the documentation as a namespace called
327# 'anonymous_namespace{file}', where file will be replaced with the base
328# name of the file that contains the anonymous namespace. By default
329# anonymous namespace are hidden.
330
331EXTRACT_ANON_NSPACES   = NO
332
333# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
334# undocumented members of documented classes, files or namespaces.
335# If set to NO (the default) these members will be included in the
336# various overviews, but no documentation section is generated.
337# This option has no effect if EXTRACT_ALL is enabled.
338
339HIDE_UNDOC_MEMBERS     = NO
340
341# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
342# undocumented classes that are normally visible in the class hierarchy.
343# If set to NO (the default) these classes will be included in the various
344# overviews. This option has no effect if EXTRACT_ALL is enabled.
345
346HIDE_UNDOC_CLASSES     = NO
347
348# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
349# friend (class|struct|union) declarations.
350# If set to NO (the default) these declarations will be included in the
351# documentation.
352
353HIDE_FRIEND_COMPOUNDS  = NO
354
355# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
356# documentation blocks found inside the body of a function.
357# If set to NO (the default) these blocks will be appended to the
358# function's detailed documentation block.
359
360HIDE_IN_BODY_DOCS      = NO
361
362# The INTERNAL_DOCS tag determines if documentation
363# that is typed after a \internal command is included. If the tag is set
364# to NO (the default) then the documentation will be excluded.
365# Set it to YES to include the internal documentation.
366
367INTERNAL_DOCS          = NO
368
369# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
370# file names in lower-case letters. If set to YES upper-case letters are also
371# allowed. This is useful if you have classes or files whose names only differ
372# in case and if your file system supports case sensitive file names. Windows
373# and Mac users are advised to set this option to NO.
374
375CASE_SENSE_NAMES       = YES
376
377# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
378# will show members with their full class and namespace scopes in the
379# documentation. If set to YES the scope will be hidden.
380
381HIDE_SCOPE_NAMES       = NO
382
383# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
384# will put a list of the files that are included by a file in the documentation
385# of that file.
386
387SHOW_INCLUDE_FILES     = YES
388
389# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen
390# will list include files with double quotes in the documentation
391# rather than with sharp brackets.
392
393FORCE_LOCAL_INCLUDES   = NO
394
395# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
396# is inserted in the documentation for inline members.
397
398INLINE_INFO            = YES
399
400# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
401# will sort the (detailed) documentation of file and class members
402# alphabetically by member name. If set to NO the members will appear in
403# declaration order.
404
405SORT_MEMBER_DOCS       = YES
406
407# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
408# brief documentation of file, namespace and class members alphabetically
409# by member name. If set to NO (the default) the members will appear in
410# declaration order.
411
412SORT_BRIEF_DOCS        = NO
413
414# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the (brief and detailed) documentation of class members so that constructors and destructors are listed first. If set to NO (the default) the constructors will appear in the respective orders defined by SORT_MEMBER_DOCS and SORT_BRIEF_DOCS. This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.
415
416SORT_MEMBERS_CTORS_1ST = NO
417
418# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the
419# hierarchy of group names into alphabetical order. If set to NO (the default)
420# the group names will appear in their defined order.
421
422SORT_GROUP_NAMES       = NO
423
424# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
425# sorted by fully-qualified names, including namespaces. If set to
426# NO (the default), the class list will be sorted only by class name,
427# not including the namespace part.
428# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
429# Note: This option applies only to the class list, not to the
430# alphabetical list.
431
432SORT_BY_SCOPE_NAME     = NO
433
434# The GENERATE_TODOLIST tag can be used to enable (YES) or
435# disable (NO) the todo list. This list is created by putting \todo
436# commands in the documentation.
437
438GENERATE_TODOLIST      = YES
439
440# The GENERATE_TESTLIST tag can be used to enable (YES) or
441# disable (NO) the test list. This list is created by putting \test
442# commands in the documentation.
443
444GENERATE_TESTLIST      = YES
445
446# The GENERATE_BUGLIST tag can be used to enable (YES) or
447# disable (NO) the bug list. This list is created by putting \bug
448# commands in the documentation.
449
450GENERATE_BUGLIST       = YES
451
452# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
453# disable (NO) the deprecated list. This list is created by putting
454# \deprecated commands in the documentation.
455
456GENERATE_DEPRECATEDLIST= YES
457
458# The ENABLED_SECTIONS tag can be used to enable conditional
459# documentation sections, marked by \if sectionname ... \endif.
460
461ENABLED_SECTIONS       =
462
463# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
464# the initial value of a variable or define consists of for it to appear in
465# the documentation. If the initializer consists of more lines than specified
466# here it will be hidden. Use a value of 0 to hide initializers completely.
467# The appearance of the initializer of individual variables and defines in the
468# documentation can be controlled using \showinitializer or \hideinitializer
469# command in the documentation regardless of this setting.
470
471MAX_INITIALIZER_LINES  = 30
472
473# Set the SHOW_USED_FILES tag to NO to disable the list of files generated
474# at the bottom of the documentation of classes and structs. If set to YES the
475# list will mention the files that were used to generate the documentation.
476
477SHOW_USED_FILES        = YES
478
479# If the sources in your project are distributed over multiple directories
480# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
481# in the documentation. The default is NO.
482
483SHOW_DIRECTORIES       = NO
484
485# Set the SHOW_FILES tag to NO to disable the generation of the Files page.
486# This will remove the Files entry from the Quick Index and from the
487# Folder Tree View (if specified). The default is YES.
488
489SHOW_FILES             = YES
490
491# Set the SHOW_NAMESPACES tag to NO to disable the generation of the
492# Namespaces page.
493# This will remove the Namespaces entry from the Quick Index
494# and from the Folder Tree View (if specified). The default is YES.
495
496SHOW_NAMESPACES        = YES
497
498# The FILE_VERSION_FILTER tag can be used to specify a program or script that
499# doxygen should invoke to get the current version for each file (typically from
500# the version control system). Doxygen will invoke the program by executing (via
501# popen()) the command <command> <input-file>, where <command> is the value of
502# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
503# provided by doxygen. Whatever the program writes to standard output
504# is used as the file version. See the manual for examples.
505
506FILE_VERSION_FILTER    =
507
508# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed by
509# doxygen. The layout file controls the global structure of the generated output files
510# in an output format independent way. The create the layout file that represents
511# doxygen's defaults, run doxygen with the -l option. You can optionally specify a
512# file name after the option, if omitted DoxygenLayout.xml will be used as the name
513# of the layout file.
514
515LAYOUT_FILE            =
516
517#---------------------------------------------------------------------------
518# configuration options related to warning and progress messages
519#---------------------------------------------------------------------------
520
521# The QUIET tag can be used to turn on/off the messages that are generated
522# by doxygen. Possible values are YES and NO. If left blank NO is used.
523
524QUIET                  = NO
525
526# The WARNINGS tag can be used to turn on/off the warning messages that are
527# generated by doxygen. Possible values are YES and NO. If left blank
528# NO is used.
529
530WARNINGS               = YES
531
532# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
533# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
534# automatically be disabled.
535
536WARN_IF_UNDOCUMENTED   = YES
537
538# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
539# potential errors in the documentation, such as not documenting some
540# parameters in a documented function, or documenting parameters that
541# don't exist or using markup commands wrongly.
542
543WARN_IF_DOC_ERROR      = YES
544
545# This WARN_NO_PARAMDOC option can be abled to get warnings for
546# functions that are documented, but have no documentation for their parameters
547# or return value. If set to NO (the default) doxygen will only warn about
548# wrong or incomplete parameter documentation, but not about the absence of
549# documentation.
550
551WARN_NO_PARAMDOC       = NO
552
553# The WARN_FORMAT tag determines the format of the warning messages that
554# doxygen can produce. The string should contain the $file, $line, and $text
555# tags, which will be replaced by the file and line number from which the
556# warning originated and the warning text. Optionally the format may contain
557# $version, which will be replaced by the version of the file (if it could
558# be obtained via FILE_VERSION_FILTER)
559
560WARN_FORMAT            = "$file:$line: $text"
561
562# The WARN_LOGFILE tag can be used to specify a file to which warning
563# and error messages should be written. If left blank the output is written
564# to stderr.
565
566WARN_LOGFILE           = warnings.log
567
568#---------------------------------------------------------------------------
569# configuration options related to the input files
570#---------------------------------------------------------------------------
571
572# The INPUT tag can be used to specify the files and/or directories that contain
573# documented source files. You may enter file names like "myfile.cpp" or
574# directories like "/usr/src/myproject". Separate the files or directories
575# with spaces.
576
577INPUT                  = ../lib/include
578
579# This tag can be used to specify the character encoding of the source files
580# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is
581# also the default input encoding. Doxygen uses libiconv (or the iconv built
582# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for
583# the list of possible encodings.
584
585INPUT_ENCODING         = UTF-8
586
587# If the value of the INPUT tag contains directories, you can use the
588# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
589# and *.h) to filter out the source-files in the directories. If left
590# blank the following patterns are tested:
591# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx
592# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90
593
594FILE_PATTERNS          = *.h \
595                         *.inl \
596                         *.c
597
598# The RECURSIVE tag can be used to turn specify whether or not subdirectories
599# should be searched for input files as well. Possible values are YES and NO.
600# If left blank NO is used.
601
602RECURSIVE              = YES
603
604# The EXCLUDE tag can be used to specify files and/or directories that should
605# excluded from the INPUT source files. This way you can easily exclude a
606# subdirectory from a directory tree whose root is specified with the INPUT tag.
607
608EXCLUDE                = score/mainpage.h
609
610# The EXCLUDE_SYMLINKS tag can be used select whether or not files or
611# directories that are symbolic links (a Unix filesystem feature) are excluded
612# from the input.
613
614EXCLUDE_SYMLINKS       = NO
615
616# If the value of the INPUT tag contains directories, you can use the
617# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
618# certain files from those directories. Note that the wildcards are matched
619# against the file with absolute path, so to exclude all test directories
620# for example use the pattern */test/*
621
622EXCLUDE_PATTERNS       =
623
624# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
625# (namespaces, classes, functions, etc.) that should be excluded from the
626# output. The symbol name can be a fully qualified name, a word, or if the
627# wildcard * is used, a substring. Examples: ANamespace, AClass,
628# AClass::ANamespace, ANamespace::*Test
629
630EXCLUDE_SYMBOLS        =
631
632# The EXAMPLE_PATH tag can be used to specify one or more files or
633# directories that contain example code fragments that are included (see
634# the \include command).
635
636EXAMPLE_PATH           =
637
638# If the value of the EXAMPLE_PATH tag contains directories, you can use the
639# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
640# and *.h) to filter out the source-files in the directories. If left
641# blank all files are included.
642
643EXAMPLE_PATTERNS       =
644
645# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
646# searched for input files to be used with the \include or \dontinclude
647# commands irrespective of the value of the RECURSIVE tag.
648# Possible values are YES and NO. If left blank NO is used.
649
650EXAMPLE_RECURSIVE      = NO
651
652# The IMAGE_PATH tag can be used to specify one or more files or
653# directories that contain image that are included in the documentation (see
654# the \image command).
655
656IMAGE_PATH             =
657
658# The INPUT_FILTER tag can be used to specify a program that doxygen should
659# invoke to filter for each input file. Doxygen will invoke the filter program
660# by executing (via popen()) the command <filter> <input-file>, where <filter>
661# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
662# input file. Doxygen will then use the output that the filter program writes
663# to standard output.
664# If FILTER_PATTERNS is specified, this tag will be
665# ignored.
666
667INPUT_FILTER           = @top_srcdir@/doxy-filter
668
669# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
670# basis.
671# Doxygen will compare the file name with each pattern and apply the
672# filter if there is a match.
673# The filters are a list of the form:
674# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
675# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER
676# is applied to all files.
677
678FILTER_PATTERNS        =
679
680# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
681# INPUT_FILTER) will be used to filter the input files when producing source
682# files to browse (i.e. when SOURCE_BROWSER is set to YES).
683
684FILTER_SOURCE_FILES    = NO
685
686#---------------------------------------------------------------------------
687# configuration options related to source browsing
688#---------------------------------------------------------------------------
689
690# If the SOURCE_BROWSER tag is set to YES then a list of source files will
691# be generated. Documented entities will be cross-referenced with these sources.
692# Note: To get rid of all source code in the generated output, make sure also
693# VERBATIM_HEADERS is set to NO.
694
695SOURCE_BROWSER         = NO
696
697# Setting the INLINE_SOURCES tag to YES will include the body
698# of functions and classes directly in the documentation.
699
700INLINE_SOURCES         = NO
701
702# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
703# doxygen to hide any special comment blocks from generated source code
704# fragments. Normal C and C++ comments will always remain visible.
705
706STRIP_CODE_COMMENTS    = YES
707
708# If the REFERENCED_BY_RELATION tag is set to YES
709# then for each documented function all documented
710# functions referencing it will be listed.
711
712REFERENCED_BY_RELATION = YES
713
714# If the REFERENCES_RELATION tag is set to YES
715# then for each documented function all documented entities
716# called/used by that function will be listed.
717
718REFERENCES_RELATION    = YES
719
720# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
721# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
722# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
723# link to the source code.
724# Otherwise they will link to the documentation.
725
726REFERENCES_LINK_SOURCE = YES
727
728# If the USE_HTAGS tag is set to YES then the references to source code
729# will point to the HTML generated by the htags(1) tool instead of doxygen
730# built-in source browser. The htags tool is part of GNU's global source
731# tagging system (see http://www.gnu.org/software/global/global.html). You
732# will need version 4.8.6 or higher.
733
734USE_HTAGS              = NO
735
736# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
737# will generate a verbatim copy of the header file for each class for
738# which an include is specified. Set to NO to disable this.
739
740VERBATIM_HEADERS       = YES
741
742#---------------------------------------------------------------------------
743# configuration options related to the alphabetical class index
744#---------------------------------------------------------------------------
745
746# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
747# of all compounds will be generated. Enable this if the project
748# contains a lot of classes, structs, unions or interfaces.
749
750ALPHABETICAL_INDEX     = NO
751
752# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
753# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
754# in which this list will be split (can be a number in the range [1..20])
755
756COLS_IN_ALPHA_INDEX    = 5
757
758# In case all classes in a project start with a common prefix, all
759# classes will be put under the same header in the alphabetical index.
760# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
761# should be ignored while generating the index headers.
762
763IGNORE_PREFIX          =
764
765#---------------------------------------------------------------------------
766# configuration options related to the HTML output
767#---------------------------------------------------------------------------
768
769# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
770# generate HTML output.
771
772GENERATE_HTML          = YES
773
774# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
775# If a relative path is entered the value of OUTPUT_DIRECTORY will be
776# put in front of it. If left blank `html' will be used as the default path.
777
778HTML_OUTPUT            = html
779
780# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
781# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
782# doxygen will generate files with .html extension.
783
784HTML_FILE_EXTENSION    = .html
785
786# The HTML_HEADER tag can be used to specify a personal HTML header for
787# each generated HTML page. If it is left blank doxygen will generate a
788# standard header.
789
790HTML_HEADER            =
791
792# The HTML_FOOTER tag can be used to specify a personal HTML footer for
793# each generated HTML page. If it is left blank doxygen will generate a
794# standard footer.
795
796HTML_FOOTER            =
797
798# If the HTML_TIMESTAMP tag is set to YES then the generated HTML
799# documentation will contain the timesstamp.
800
801HTML_TIMESTAMP         = NO
802
803# The HTML_STYLESHEET tag can be used to specify a user-defined cascading
804# style sheet that is used by each HTML page. It can be used to
805# fine-tune the look of the HTML output. If the tag is left blank doxygen
806# will generate a default style sheet. Note that doxygen will try to copy
807# the style sheet file to the HTML output directory, so don't put your own
808# stylesheet in the HTML output directory as well, or it will be erased!
809
810HTML_STYLESHEET        =
811
812# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
813# page will contain the date and time when the page was generated. Setting
814# this to NO can help when comparing the output of multiple runs.
815
816HTML_TIMESTAMP         = NO
817
818# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
819# files or namespaces will be aligned in HTML using tables. If set to
820# NO a bullet list will be used.
821
822HTML_ALIGN_MEMBERS     = YES
823
824# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
825# documentation will contain sections that can be hidden and shown after the
826# page has loaded. For this to work a browser that supports
827# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox
828# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).
829
830HTML_DYNAMIC_SECTIONS  = NO
831
832# If the GENERATE_DOCSET tag is set to YES, additional index files
833# will be generated that can be used as input for Apple's Xcode 3
834# integrated development environment, introduced with OSX 10.5 (Leopard).
835# To create a documentation set, doxygen will generate a Makefile in the
836# HTML output directory. Running make will produce the docset in that
837# directory and running "make install" will install the docset in
838# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
839# it at startup.
840# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html for more information.
841
842GENERATE_DOCSET        = NO
843
844# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the
845# feed. A documentation feed provides an umbrella under which multiple
846# documentation sets from a single provider (such as a company or product suite)
847# can be grouped.
848
849DOCSET_FEEDNAME        = "Doxygen generated docs"
850
851# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that
852# should uniquely identify the documentation set bundle. This should be a
853# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen
854# will append .docset to the name.
855
856DOCSET_BUNDLE_ID       = org.doxygen.Project
857
858# If the GENERATE_HTMLHELP tag is set to YES, additional index files
859# will be generated that can be used as input for tools like the
860# Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
861# of the generated HTML documentation.
862
863GENERATE_HTMLHELP      = NO
864
865# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
866# be used to specify the file name of the resulting .chm file. You
867# can add a path in front of the file if the result should not be
868# written to the html output directory.
869
870CHM_FILE               =
871
872# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
873# be used to specify the location (absolute path including file name) of
874# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
875# the HTML help compiler on the generated index.hhp.
876
877HHC_LOCATION           =
878
879# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
880# controls if a separate .chi index file is generated (YES) or that
881# it should be included in the master .chm file (NO).
882
883GENERATE_CHI           = NO
884
885# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING
886# is used to encode HtmlHelp index (hhk), content (hhc) and project file
887# content.
888
889CHM_INDEX_ENCODING     =
890
891# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
892# controls whether a binary table of contents is generated (YES) or a
893# normal table of contents (NO) in the .chm file.
894
895BINARY_TOC             = NO
896
897# The TOC_EXPAND flag can be set to YES to add extra items for group members
898# to the contents of the HTML help documentation and to the tree view.
899
900TOC_EXPAND             = NO
901
902# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and QHP_VIRTUAL_FOLDER
903# are set, an additional index file will be generated that can be used as input for
904# Qt's qhelpgenerator to generate a Qt Compressed Help (.qch) of the generated
905# HTML documentation.
906
907GENERATE_QHP           = NO
908
909# If the QHG_LOCATION tag is specified, the QCH_FILE tag can
910# be used to specify the file name of the resulting .qch file.
911# The path specified is relative to the HTML output folder.
912
913QCH_FILE               =
914
915# The QHP_NAMESPACE tag specifies the namespace to use when generating
916# Qt Help Project output. For more information please see
917# http://doc.trolltech.com/qthelpproject.html#namespace
918
919QHP_NAMESPACE          = org.doxygen.Project
920
921# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating
922# Qt Help Project output. For more information please see
923# http://doc.trolltech.com/qthelpproject.html#virtual-folders
924
925QHP_VIRTUAL_FOLDER     = doc
926
927# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to add.
928# For more information please see
929# http://doc.trolltech.com/qthelpproject.html#custom-filters
930
931QHP_CUST_FILTER_NAME   =
932
933# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the custom filter to add.For more information please see
934# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">Qt Help Project / Custom Filters</a>.
935
936QHP_CUST_FILTER_ATTRS  =
937
938# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this project's
939# filter section matches.
940# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">Qt Help Project / Filter Attributes</a>.
941
942QHP_SECT_FILTER_ATTRS  =
943
944# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can
945# be used to specify the location of Qt's qhelpgenerator.
946# If non-empty doxygen will try to run qhelpgenerator on the generated
947# .qhp file.
948
949QHG_LOCATION           =
950
951# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files
952#  will be generated, which together with the HTML files, form an Eclipse help
953#  plugin. To install this plugin and make it available under the help contents
954# menu in Eclipse, the contents of the directory containing the HTML and XML
955# files needs to be copied into the plugins directory of eclipse. The name of
956# the directory within the plugins directory should be the same as
957# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before the help appears.
958
959GENERATE_ECLIPSEHELP   = NO
960
961# A unique identifier for the eclipse help plugin. When installing the plugin
962# the directory name containing the HTML and XML files should also have
963# this name.
964
965ECLIPSE_DOC_ID         = org.doxygen.Project
966
967# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
968# top of each HTML page. The value NO (the default) enables the index and
969# the value YES disables it.
970
971DISABLE_INDEX          = NO
972
973# This tag can be used to set the number of enum values (range [1..20])
974# that doxygen will group on one line in the generated HTML documentation.
975
976ENUM_VALUES_PER_LINE   = 4
977
978# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
979# structure should be generated to display hierarchical information.
980# If the tag value is set to YES, a side panel will be generated
981# containing a tree-like index structure (just like the one that
982# is generated for HTML Help). For this to work a browser that supports
983# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).
984# Windows users are probably better off using the HTML help feature.
985
986GENERATE_TREEVIEW      = NO
987
988# By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories,
989# and Class Hierarchy pages using a tree view instead of an ordered list.
990
991USE_INLINE_TREES       = NO
992
993# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
994# used to set the initial width (in pixels) of the frame in which the tree
995# is shown.
996
997TREEVIEW_WIDTH         = 250
998
999# Use this tag to change the font size of Latex formulas included
1000# as images in the HTML documentation. The default is 10. Note that
1001# when you change the font size after a successful doxygen run you need
1002# to manually remove any form_*.png images from the HTML output directory
1003# to force them to be regenerated.
1004
1005FORMULA_FONTSIZE       = 10
1006
1007# When the SEARCHENGINE tag is enabled doxygen will generate a search box for the HTML output. The underlying search engine uses javascript
1008# and DHTML and should work on any modern browser. Note that when using HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET) there is already a search function so this one should
1009# typically be disabled. For large projects the javascript based search engine
1010# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.
1011
1012SEARCHENGINE           = NO
1013
1014# When the SERVER_BASED_SEARCH tag is enabled the search engine will be implemented using a PHP enabled web server instead of at the web client using Javascript. Doxygen will generate the search PHP script and index
1015# file to put on the web server. The advantage of the server based approach is that it scales better to large projects and allows full text search. The disadvances is that it is more difficult to setup
1016# and does not have live searching capabilities.
1017
1018SERVER_BASED_SEARCH    = NO
1019
1020#---------------------------------------------------------------------------
1021# configuration options related to the LaTeX output
1022#---------------------------------------------------------------------------
1023
1024# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
1025# generate Latex output.
1026
1027GENERATE_LATEX         = NO
1028
1029# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
1030# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1031# put in front of it. If left blank `latex' will be used as the default path.
1032
1033LATEX_OUTPUT           = latex
1034
1035# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
1036# invoked. If left blank `latex' will be used as the default command name.
1037# Note that when enabling USE_PDFLATEX this option is only used for
1038# generating bitmaps for formulas in the HTML output, but not in the
1039# Makefile that is written to the output directory.
1040
1041LATEX_CMD_NAME         = latex
1042
1043# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
1044# generate index for LaTeX. If left blank `makeindex' will be used as the
1045# default command name.
1046
1047MAKEINDEX_CMD_NAME     = makeindex
1048
1049# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
1050# LaTeX documents. This may be useful for small projects and may help to
1051# save some trees in general.
1052
1053COMPACT_LATEX          = NO
1054
1055# The PAPER_TYPE tag can be used to set the paper type that is used
1056# by the printer. Possible values are: a4, a4wide, letter, legal and
1057# executive. If left blank a4wide will be used.
1058
1059PAPER_TYPE             = a4wide
1060
1061# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
1062# packages that should be included in the LaTeX output.
1063
1064EXTRA_PACKAGES         =
1065
1066# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
1067# the generated latex document. The header should contain everything until
1068# the first chapter. If it is left blank doxygen will generate a
1069# standard header. Notice: only use this tag if you know what you are doing!
1070
1071LATEX_HEADER           =
1072
1073# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
1074# is prepared for conversion to pdf (using ps2pdf). The pdf file will
1075# contain links (just like the HTML output) instead of page references
1076# This makes the output suitable for online browsing using a pdf viewer.
1077
1078PDF_HYPERLINKS         = NO
1079
1080# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
1081# plain latex in the generated Makefile. Set this option to YES to get a
1082# higher quality PDF documentation.
1083
1084USE_PDFLATEX           = NO
1085
1086# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
1087# command to the generated LaTeX files. This will instruct LaTeX to keep
1088# running if errors occur, instead of asking the user for help.
1089# This option is also used when generating formulas in HTML.
1090
1091LATEX_BATCHMODE        = NO
1092
1093# If LATEX_HIDE_INDICES is set to YES then doxygen will not
1094# include the index chapters (such as File Index, Compound Index, etc.)
1095# in the output.
1096
1097LATEX_HIDE_INDICES     = NO
1098
1099# If LATEX_SOURCE_CODE is set to YES then doxygen will include source code with syntax highlighting in the LaTeX output. Note that which sources are shown also depends on other settings such as SOURCE_BROWSER.
1100
1101LATEX_SOURCE_CODE      = NO
1102
1103#---------------------------------------------------------------------------
1104# configuration options related to the RTF output
1105#---------------------------------------------------------------------------
1106
1107# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
1108# The RTF output is optimized for Word 97 and may not look very pretty with
1109# other RTF readers or editors.
1110
1111GENERATE_RTF           = NO
1112
1113# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
1114# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1115# put in front of it. If left blank `rtf' will be used as the default path.
1116
1117RTF_OUTPUT             = rtf
1118
1119# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
1120# RTF documents. This may be useful for small projects and may help to
1121# save some trees in general.
1122
1123COMPACT_RTF            = NO
1124
1125# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
1126# will contain hyperlink fields. The RTF file will
1127# contain links (just like the HTML output) instead of page references.
1128# This makes the output suitable for online browsing using WORD or other
1129# programs which support those fields.
1130# Note: wordpad (write) and others do not support links.
1131
1132RTF_HYPERLINKS         = NO
1133
1134# Load stylesheet definitions from file. Syntax is similar to doxygen's
1135# config file, i.e. a series of assignments. You only have to provide
1136# replacements, missing definitions are set to their default value.
1137
1138RTF_STYLESHEET_FILE    =
1139
1140# Set optional variables used in the generation of an rtf document.
1141# Syntax is similar to doxygen's config file.
1142
1143RTF_EXTENSIONS_FILE    =
1144
1145#---------------------------------------------------------------------------
1146# configuration options related to the man page output
1147#---------------------------------------------------------------------------
1148
1149# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
1150# generate man pages
1151
1152GENERATE_MAN           = NO
1153
1154# The MAN_OUTPUT tag is used to specify where the man pages will be put.
1155# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1156# put in front of it. If left blank `man' will be used as the default path.
1157
1158MAN_OUTPUT             = man
1159
1160# The MAN_EXTENSION tag determines the extension that is added to
1161# the generated man pages (default is the subroutine's section .3)
1162
1163MAN_EXTENSION          = .3
1164
1165# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
1166# then it will generate one additional man file for each entity
1167# documented in the real man page(s). These additional files
1168# only source the real man page, but without them the man command
1169# would be unable to find the correct page. The default is NO.
1170
1171MAN_LINKS              = NO
1172
1173#---------------------------------------------------------------------------
1174# configuration options related to the XML output
1175#---------------------------------------------------------------------------
1176
1177# If the GENERATE_XML tag is set to YES Doxygen will
1178# generate an XML file that captures the structure of
1179# the code including all documentation.
1180
1181GENERATE_XML           = NO
1182
1183# The XML_OUTPUT tag is used to specify where the XML pages will be put.
1184# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1185# put in front of it. If left blank `xml' will be used as the default path.
1186
1187XML_OUTPUT             = xml
1188
1189# The XML_SCHEMA tag can be used to specify an XML schema,
1190# which can be used by a validating XML parser to check the
1191# syntax of the XML files.
1192
1193XML_SCHEMA             =
1194
1195# The XML_DTD tag can be used to specify an XML DTD,
1196# which can be used by a validating XML parser to check the
1197# syntax of the XML files.
1198
1199XML_DTD                =
1200
1201# If the XML_PROGRAMLISTING tag is set to YES Doxygen will
1202# dump the program listings (including syntax highlighting
1203# and cross-referencing information) to the XML output. Note that
1204# enabling this will significantly increase the size of the XML output.
1205
1206XML_PROGRAMLISTING     = YES
1207
1208#---------------------------------------------------------------------------
1209# configuration options for the AutoGen Definitions output
1210#---------------------------------------------------------------------------
1211
1212# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
1213# generate an AutoGen Definitions (see autogen.sf.net) file
1214# that captures the structure of the code including all
1215# documentation. Note that this feature is still experimental
1216# and incomplete at the moment.
1217
1218GENERATE_AUTOGEN_DEF   = NO
1219
1220#---------------------------------------------------------------------------
1221# configuration options related to the Perl module output
1222#---------------------------------------------------------------------------
1223
1224# If the GENERATE_PERLMOD tag is set to YES Doxygen will
1225# generate a Perl module file that captures the structure of
1226# the code including all documentation. Note that this
1227# feature is still experimental and incomplete at the
1228# moment.
1229
1230GENERATE_PERLMOD       = NO
1231
1232# If the PERLMOD_LATEX tag is set to YES Doxygen will generate
1233# the necessary Makefile rules, Perl scripts and LaTeX code to be able
1234# to generate PDF and DVI output from the Perl module output.
1235
1236PERLMOD_LATEX          = NO
1237
1238# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
1239# nicely formatted so it can be parsed by a human reader.
1240# This is useful
1241# if you want to understand what is going on.
1242# On the other hand, if this
1243# tag is set to NO the size of the Perl module output will be much smaller
1244# and Perl will parse it just the same.
1245
1246PERLMOD_PRETTY         = YES
1247
1248# The names of the make variables in the generated doxyrules.make file
1249# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
1250# This is useful so different doxyrules.make files included by the same
1251# Makefile don't overwrite each other's variables.
1252
1253PERLMOD_MAKEVAR_PREFIX =
1254
1255#---------------------------------------------------------------------------
1256# Configuration options related to the preprocessor
1257#---------------------------------------------------------------------------
1258
1259# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
1260# evaluate all C-preprocessor directives found in the sources and include
1261# files.
1262
1263ENABLE_PREPROCESSING   = YES
1264
1265# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
1266# names in the source code. If set to NO (the default) only conditional
1267# compilation will be performed. Macro expansion can be done in a controlled
1268# way by setting EXPAND_ONLY_PREDEF to YES.
1269
1270MACRO_EXPANSION        = YES
1271
1272# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
1273# then the macro expansion is limited to the macros specified with the
1274# PREDEFINED and EXPAND_AS_DEFINED tags.
1275
1276EXPAND_ONLY_PREDEF     = YES
1277
1278# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
1279# in the INCLUDE_PATH (see below) will be search if a #include is found.
1280
1281SEARCH_INCLUDES        = YES
1282
1283# The INCLUDE_PATH tag can be used to specify one or more directories that
1284# contain include files that are not input files but should be processed by
1285# the preprocessor.
1286
1287INCLUDE_PATH           =
1288
1289# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
1290# patterns (like *.h and *.hpp) to filter out the header-files in the
1291# directories. If left blank, the patterns specified with FILE_PATTERNS will
1292# be used.
1293
1294INCLUDE_FILE_PATTERNS  =
1295
1296# The PREDEFINED tag can be used to specify one or more macro names that
1297# are defined before the preprocessor is started (similar to the -D option of
1298# gcc). The argument of the tag is a list of macros of the form: name
1299# or name=definition (no spaces). If the definition and the = are
1300# omitted =1 is assumed. To prevent a macro definition from being
1301# undefined via #undef or recursively expanded use the := operator
1302# instead of the = operator.
1303
1304PREDEFINED             = FALSE=0 \
1305                         CPU_USE_GENERIC_BITFIELD_DATA=0 \
1306                         __attribute__(x)= \
1307                         RTEMS_COMPILER_NO_RETURN_ATTRIBUTE= \
1308                         RTEMS_COMPILER_DEPRECATED_ATTRIBUTE= \
1309                         RTEMS_COMPILER_PACKED_ATTRIBUTE=
1310
1311# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
1312# this tag can be used to specify a list of macro names that should be expanded.
1313# The macro definition that is found in the sources will be used.
1314# Use the PREDEFINED tag if you want to use a different macro definition.
1315
1316EXPAND_AS_DEFINED      =
1317
1318# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
1319# doxygen's preprocessor will remove all function-like macros that are alone
1320# on a line, have an all uppercase name, and do not end with a semicolon. Such
1321# function macros are typically used for boiler-plate code, and will confuse
1322# the parser if not removed.
1323
1324SKIP_FUNCTION_MACROS   = YES
1325
1326#---------------------------------------------------------------------------
1327# Configuration::additions related to external references
1328#---------------------------------------------------------------------------
1329
1330# The TAGFILES option can be used to specify one or more tagfiles.
1331# Optionally an initial location of the external documentation
1332# can be added for each tagfile. The format of a tag file without
1333# this location is as follows:
1334#
1335# TAGFILES = file1 file2 ...
1336# Adding location for the tag files is done as follows:
1337#
1338# TAGFILES = file1=loc1 "file2 = loc2" ...
1339# where "loc1" and "loc2" can be relative or absolute paths or
1340# URLs. If a location is present for each tag, the installdox tool
1341# does not have to be run to correct the links.
1342# Note that each tag file must have a unique name
1343# (where the name does NOT include the path)
1344# If a tag file is not located in the directory in which doxygen
1345# is run, you must also specify the path to the tagfile here.
1346
1347TAGFILES               =
1348
1349# When a file name is specified after GENERATE_TAGFILE, doxygen will create
1350# a tag file that is based on the input files it reads.
1351
1352GENERATE_TAGFILE       =
1353
1354# If the ALLEXTERNALS tag is set to YES all external classes will be listed
1355# in the class index. If set to NO only the inherited external classes
1356# will be listed.
1357
1358ALLEXTERNALS           = NO
1359
1360# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1361# in the modules index. If set to NO, only the current project's groups will
1362# be listed.
1363
1364EXTERNAL_GROUPS        = YES
1365
1366# The PERL_PATH should be the absolute path and name of the perl script
1367# interpreter (i.e. the result of `which perl').
1368
1369PERL_PATH              = @PERL@
1370
1371#---------------------------------------------------------------------------
1372# Configuration options related to the dot tool
1373#---------------------------------------------------------------------------
1374
1375# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1376# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
1377# or super classes. Setting the tag to NO turns the diagrams off. Note that
1378# this option is superseded by the HAVE_DOT option below. This is only a
1379# fallback. It is recommended to install and use dot, since it yields more
1380# powerful graphs.
1381
1382CLASS_DIAGRAMS         = YES
1383
1384# You can define message sequence charts within doxygen comments using the \msc
1385# command. Doxygen will then run the mscgen tool (see
1386# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the
1387# documentation. The MSCGEN_PATH tag allows you to specify the directory where
1388# the mscgen tool resides. If left empty the tool is assumed to be found in the
1389# default search path.
1390
1391MSCGEN_PATH            =
1392
1393# If set to YES, the inheritance and collaboration graphs will hide
1394# inheritance and usage relations if the target is undocumented
1395# or is not a class.
1396
1397HIDE_UNDOC_RELATIONS   = YES
1398
1399# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1400# available from the path. This tool is part of Graphviz, a graph visualization
1401# toolkit from AT&T and Lucent Bell Labs. The other options in this section
1402# have no effect if this option is set to NO (the default)
1403
1404HAVE_DOT               = YES
1405
1406# By default doxygen will write a font called FreeSans.ttf to the output
1407# directory and reference it in all dot files that doxygen generates. This
1408# font does not include all possible unicode characters however, so when you need
1409# these (or just want a differently looking font) you can specify the font name
1410# using DOT_FONTNAME. You need need to make sure dot is able to find the font,
1411# which can be done by putting it in a standard location or by setting the
1412# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory
1413# containing the font.
1414
1415DOT_FONTNAME           = FreeSans
1416
1417# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs.
1418# The default size is 10pt.
1419
1420DOT_FONTSIZE           = 10
1421
1422# By default doxygen will tell dot to use the output directory to look for the
1423# FreeSans.ttf font (which doxygen will put there itself). If you specify a
1424# different font using DOT_FONTNAME you can set the path where dot
1425# can find it using this tag.
1426
1427DOT_FONTPATH           =
1428
1429# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
1430# will generate a graph for each documented class showing the direct and
1431# indirect inheritance relations. Setting this tag to YES will force the
1432# the CLASS_DIAGRAMS tag to NO.
1433
1434CLASS_GRAPH            = YES
1435
1436# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
1437# will generate a graph for each documented class showing the direct and
1438# indirect implementation dependencies (inheritance, containment, and
1439# class references variables) of the class with other documented classes.
1440
1441COLLABORATION_GRAPH    = YES
1442
1443# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
1444# will generate a graph for groups, showing the direct groups dependencies
1445
1446GROUP_GRAPHS           = YES
1447
1448# If the UML_LOOK tag is set to YES doxygen will generate inheritance and
1449# collaboration diagrams in a style similar to the OMG's Unified Modeling
1450# Language.
1451
1452UML_LOOK               = NO
1453
1454# If set to YES, the inheritance and collaboration graphs will show the
1455# relations between templates and their instances.
1456
1457TEMPLATE_RELATIONS     = NO
1458
1459# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
1460# tags are set to YES then doxygen will generate a graph for each documented
1461# file showing the direct and indirect include dependencies of the file with
1462# other documented files.
1463
1464INCLUDE_GRAPH          = YES
1465
1466# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
1467# HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1468# documented header file showing the documented files that directly or
1469# indirectly include this file.
1470
1471INCLUDED_BY_GRAPH      = YES
1472
1473# If the CALL_GRAPH and HAVE_DOT options are set to YES then
1474# doxygen will generate a call dependency graph for every global function
1475# or class method. Note that enabling this option will significantly increase
1476# the time of a run. So in most cases it will be better to enable call graphs
1477# for selected functions only using the \callgraph command.
1478
1479CALL_GRAPH             = NO
1480
1481# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then
1482# doxygen will generate a caller dependency graph for every global function
1483# or class method. Note that enabling this option will significantly increase
1484# the time of a run. So in most cases it will be better to enable caller
1485# graphs for selected functions only using the \callergraph command.
1486
1487CALLER_GRAPH           = NO
1488
1489# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
1490# will graphical hierarchy of all classes instead of a textual one.
1491
1492GRAPHICAL_HIERARCHY    = YES
1493
1494# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
1495# then doxygen will show the dependencies a directory has on other directories
1496# in a graphical way. The dependency relations are determined by the #include
1497# relations between the files in the directories.
1498
1499DIRECTORY_GRAPH        = YES
1500
1501# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1502# generated by dot. Possible values are png, jpg, or gif
1503# If left blank png will be used.
1504
1505DOT_IMAGE_FORMAT       = png
1506
1507# The tag DOT_PATH can be used to specify the path where the dot tool can be
1508# found. If left blank, it is assumed the dot tool can be found in the path.
1509
1510DOT_PATH               =
1511
1512# The DOTFILE_DIRS tag can be used to specify one or more directories that
1513# contain dot files that are included in the documentation (see the
1514# \dotfile command).
1515
1516DOTFILE_DIRS           =
1517
1518# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of
1519# nodes that will be shown in the graph. If the number of nodes in a graph
1520# becomes larger than this value, doxygen will truncate the graph, which is
1521# visualized by representing a node as a red box. Note that doxygen if the
1522# number of direct children of the root node in a graph is already larger than
1523# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note
1524# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
1525
1526DOT_GRAPH_MAX_NODES    = 50
1527
1528# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
1529# graphs generated by dot. A depth value of 3 means that only nodes reachable
1530# from the root by following a path via at most 3 edges will be shown. Nodes
1531# that lay further from the root node will be omitted. Note that setting this
1532# option to 1 or 2 may greatly reduce the computation time needed for large
1533# code bases. Also note that the size of a graph can be further restricted by
1534# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
1535
1536MAX_DOT_GRAPH_DEPTH    = 0
1537
1538# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
1539# background. This is disabled by default, because dot on Windows does not
1540# seem to support this out of the box. Warning: Depending on the platform used,
1541# enabling this option may lead to badly anti-aliased labels on the edges of
1542# a graph (i.e. they become hard to read).
1543
1544DOT_TRANSPARENT        = NO
1545
1546# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
1547# files in one run (i.e. multiple -o and -T options on the command line). This
1548# makes dot run faster, but since only newer versions of dot (>1.8.10)
1549# support this, this feature is disabled by default.
1550
1551DOT_MULTI_TARGETS      = NO
1552
1553# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1554# generate a legend page explaining the meaning of the various boxes and
1555# arrows in the dot generated graphs.
1556
1557GENERATE_LEGEND        = YES
1558
1559# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1560# remove the intermediate dot files that are used to generate
1561# the various graphs.
1562
1563DOT_CLEANUP            = YES
Note: See TracBrowser for help on using the repository browser.