projects/build/bsp.dxyfile

3 # This file describes the settings to be used by the documentation system
17 # This tag specifies the encoding used for all characters in the config file
48 # otherwise cause performance problems for the file system.
67 # the file and class documentation (similar to JavaDoc).
86 # "The $name file" "is" "provides" "specifies" "contains"
91                          "The $name file        " \
115 # path before files name in the file list and in the header files. If set
116 # to NO the shortest path that makes the file name unique will be used.
123 # the path. The tag can be used to show relative paths in the file list.
131 # the reader which header file to include in order to use a class.
132 # If left blank only the name of the header file containing the class
139 # (but less readable) file names. This can be useful is your file systems
176 # be part of the file/class/namespace that contains it.
221 # to include (a tag file for) the STL sources as input, then you should
267 # with name TypeT. When disabled the typedef will appear as a member of a file,
296 # Private class members and static file members will be hidden unless
306 # If the EXTRACT_STATIC tag is set to YES all static members of a file
326 # 'anonymous_namespace{file}', where file will be replaced with the base
327 # name of the file that contains the anonymous namespace. By default
369 # file names in lower-case letters. If set to YES upper-case letters are also
371 # in case and if your file system supports case sensitive file names. Windows
383 # will put a list of the files that are included by a file in the documentation
384 # of that file.
394 # will sort the (detailed) documentation of file and class members
401 # brief documentation of file, namespace and class members alphabetically
487 # doxygen should invoke to get the current version for each file (typically from
489 # popen()) the command <command> <input-file>, where <command> is the value of
490 # the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
492 # is used as the file version. See the manual for examples.
496 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed by
497 # doxygen. The layout file controls the global structure of the generated output files
498 # in an output format independent way. The create the layout file that represents
500 # file name after the option, if omitted DoxygenLayout.xml will be used as the name
501 # of the layout file.
542 # doxygen can produce. The string should contain the $file, $line, and $text
543 # tags, which will be replaced by the file and line number from which the
545 # $version, which will be replaced by the version of the file (if it could
548 WARN_FORMAT            = "$file:$line: $text  "
550 # The WARN_LOGFILE tag can be used to specify a file to which warning
561 # documented source files. You may enter file names like "myfile.cpp" or
638 # against the file with absolute path, so to exclude all test directories
678 # invoke to filter for each input file. Doxygen will invoke the filter program
679 # by executing (via popen()) the command <filter> <input-file>, where <filter>
680 # is the value of the INPUT_FILTER tag, and <input-file> is the name of an
681 # input file. Doxygen will then use the output that the filter program writes
687 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
688 # basis.  Doxygen will compare the file name with each pattern and apply the
752 # will generate a verbatim copy of the header file for each class for
795 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for
817 # the style sheet file to the HTML output directory, so don't put your own
864 # Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
870 # be used to specify the file name of the resulting .chm file. You
871 # can add a path in front of the file if the result should not be
877 # be used to specify the location (absolute path including file name) of
884 # controls if a separate .chi index file is generated (YES) or that
885 # it should be included in the master .chm file (NO).
890 # is used to encode HtmlHelp index (hhk), content (hhc) and project file
897 # normal table of contents (NO) in the .chm file.
907 # are set, an additional index file will be generated that can be used as input for
914 # be used to specify the file name of the resulting .qch file.
934 # .qhp file .
1031 # is prepared for conversion to pdf (using ps2pdf). The pdf file will
1079 # will contain hyperlink fields. The RTF file will
1087 # Load stylesheet definitions from file. Syntax is similar to doxygen's
1088 # config file, i.e. a series of assignments. You only have to provide
1094 # Syntax is similar to doxygen's config file.
1119 # then it will generate one additional man file for each entity
1131 # generate an XML file that captures the structure of
1166 # generate an AutoGen Definitions (see autogen.sf.net) file
1178 # generate a Perl module file that captures the structure of
1199 # The names of the make variables in the generated doxyrules.make file
1280 # can be added for each tagfile. The format of a tag file without
1288 # Note that each tag file must have a unique name
1290 # If a tag file is not located in the directory in which doxygen
1295 # When a file name is specified after GENERATE_TAGFILE, doxygen will create
1296 # a tag file that is based on the input files it reads.
1407 # file showing the direct and indirect include dependencies of the file with
1414 # documented header file showing the documented files that directly or
1415 # indirectly include this file.