projects/build/bsp.dxyfile

4 # doxygen (www.doxygen.org) for a project
6 # All text after a hash (#) is considered a comment and will be ignored
25 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded
30 # The PROJECT_NUMBER tag can be used to enter a project or revision number.
38 # If a relative path is entered, it will be relative to the location
46 # Enabling this option can be useful when feeding doxygen a huge amount of
73 # the brief description of a member or function before the detailed description.
79 # This tag implements a quasi-intelligent brief description abbreviator
87 # "represents" "a" "an" "the"
97                          a \
102 # Doxygen will generate a detailed section even if there is only a brief
108 # inherited members of a class in the documentation of that class as if those
121 # can be used to strip a user-defined part of the path. Stripping is
129 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
130 # the path mentioned in the documentation of a class, which tells
131 # the reader which header file to include in order to use a class.
145 # will interpret the first line (until the first dot) of a JavaDoc-style
148 # (thus requiring an explicit @brief command for a brief description.)
153 # interpret the first line (until the first dot) of a Qt-style
156 # an explicit \brief command for a brief description.)
161 # treat a multi-line C++ special comment block (i.e. a block of //! or ///
162 # comments) as a brief description. This used to be the default behaviour.
163 # The new default is to treat a multi-line C++ comment block as a detailed
175 # a new page for each member. If set to NO, the documentation of a member will
180 # The TAB_SIZE tag can be used to set the number of spaces in a tab.
185 # This tag can be used to specify a number of aliases that acts
189 # will result in a user-defined paragraph with heading "Side Effects:".
221 # to include (a tag file for) the STL sources as input, then you should
241 # and setter methods for a property. Setting this option to YES (the default)
242 # will make doxygen to replace the get and set methods by a property in the
244 # setting a simple type. If this is not the case, or you want to show the
252 # all members of a group must be documented explicitly.
257 # the same type (for instance a group of public functions) to be put as a
264 # When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum
266 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
267 # with name TypeT. When disabled the typedef will appear as a member of a file,
278 # probably good enough. For larger projects a too small cache size can cause
280 # causing a significant performance penality.
283 # a logarithmic scale so increasing the size by one will rougly double the
286 # corresponding to a cache size of 2^16 = 65536 symbols
301 # If the EXTRACT_PRIVATE tag is set to YES all private members of a class
306 # If the EXTRACT_STATIC tag is set to YES all static members of a file
325 # extracted and appear in the documentation as a namespace called
355 # documentation blocks found inside the body of a function.
362 # that is typed after a \internal command is included. If the tag is set
383 # will put a list of the files that are included by a file in the documentation
388 # If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
453 # the initial value of a variable or define consists of for it to appear in
455 # here it will be hidden. Use a value of 0 to hide initializers completely.
486 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
496 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed by
499 # doxygen's defaults, run doxygen with the -l option. You can optionally specify a
528 # parameters in a documented function, or documenting parameters that
550 # The WARN_LOGFILE tag can be used to specify a file to which warning
624 # excluded from the INPUT source files. This way you can easily exclude a
625 # subdirectory from a directory tree whose root is specified with the INPUT tag.
630 # directories that are symbolic links (a Unix filesystem feature) are excluded
645 # output. The symbol name can be a fully qualified name, a word, or if the
646 # wildcard * is used, a substring. Examples: ANamespace, AClass,
677 # The INPUT_FILTER tag can be used to specify a program that doxygen should
687 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
689 # filter if there is a match.  The filters are a list of the form:
706 # If the SOURCE_BROWSER tag is set to YES then a list of source files will
752 # will generate a verbatim copy of the header file for each class for
763 # contains a lot of classes, structs, unions or interfaces.
769 # in which this list will be split (can be a number in the range [1..20])
773 # In case all classes in a project start with a common prefix, all
790 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
801 # The HTML_HEADER tag can be used to specify a personal HTML header for
802 # each generated HTML page. If it is left blank doxygen will generate a
807 # The HTML_FOOTER tag can be used to specify a personal HTML footer for
808 # each generated HTML page. If it is left blank doxygen will generate a
813 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading
816 # will generate a default style sheet. Note that doxygen will try to copy
824 # NO a bullet list will be used.
830 # page has loaded. For this to work a browser that supports
839 # To create a documentation set, doxygen will generate a Makefile in the
850 # documentation sets from a single provider (such as a company or product suite)
855 # When GENERATE_DOCSET tag is set to YES, this tag specifies a string that
856 # should uniquely identify the documentation set bundle. This should be a
864 # Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
871 # can add a path in front of the file if the result should not be
884 # controls if a separate .chi index file is generated (YES) or that
896 # controls whether a binary table of contents is generated (YES) or a
908 # Qt's qhelpgenerator to generate a Qt Compressed Help (.qch) of the generated
921 # <a href="http://doc.trolltech.com/qthelpproject.html#namespace">Qt Help Project / Namespace</a>.
927 # <a href="http://doc.trolltech.com/qthelpproject.html#virtual-folders">Qt Help Project / Virtual F…
949 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
951 # If the tag value is set to FRAME, a side panel will be generated
952 # containing a tree-like index structure (just like the one that
953 # is generated for HTML Help). For this to work a browser that supports
958 # and Class Hierarchy pages using a tree view instead of an ordered list;
974 # when you change the font size after a successful doxygen run you need
990 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
1023 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for
1025 # the first chapter. If it is left blank doxygen will generate a
1033 # This makes the output suitable for online browsing using a pdf viewer.
1038 # plain latex in the generated Makefile. Set this option to YES to get a
1067 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
1088 # config file, i.e. a series of assignments. You only have to provide
1108 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
1137 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
1143 # which can be used by a validating XML parser to check the
1149 # which can be used by a validating XML parser to check the
1178 # generate a Perl module file that captures the structure of
1192 # nicely formatted so it can be parsed by a human reader.  This is useful
1218 # compilation will be performed. Macro expansion can be done in a controlled
1230 # in the INCLUDE_PATH (see below) will be search if a #include is found.
1249 # gcc). The argument of the tag is a list of macros of the form: name
1251 # omitted =1 is assumed. To prevent a macro definition from being
1260 # this tag can be used to specify a list of macro names that should be expanded.
1262 # Use the PREDEFINED tag if you want to use a different macro definition.
1268 # on a line, have an all uppercase name, and do not end with a semicolon. Such
1280 # can be added for each tagfile. The format of a tag file without
1286 # URLs. If a location is present for each tag, the installdox tool
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.
1322 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
1324 # this option is superseded by the HAVE_DOT option below. This is only a
1341 # or is not a class.
1346 # available from the path. This tool is part of Graphviz, a graph visualization
1352 # By default doxygen will write a font called FreeSans.ttf to the output
1355 # these (or just want a differently looking font) you can specify the font name
1357 # which can be done by putting it in a standard location or by setting the
1369 # FreeSans.ttf font (which doxygen will put there itself). If you specify a
1376 # will generate a graph for each documented class showing the direct and
1383 # will generate a graph for each documented class showing the direct and
1390 # will generate a graph for groups, showing the direct groups dependencies
1395 # collaboration diagrams in a style similar to the OMG's Unified Modeling
1406 # tags are set to YES then doxygen will generate a graph for each documented
1413 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1420 # doxygen will generate a call dependency graph for every global function
1422 # the time of a run. So in most cases it will be better to enable call graphs
1428 # doxygen will generate a caller dependency graph for every global function
1430 # the time of a run. So in most cases it will be better to enable caller
1436 # will graphical hierarchy of all classes instead of a textual one.
1441 # then doxygen will show the dependencies a directory has on other directories
1442 # in a graphical way. The dependency relations are determined by the #include
1465 # nodes that will be shown in the graph. If the number of nodes in a graph
1467 # visualized by representing a node as a red box. Note that doxygen if the
1468 # number of direct children of the root node in a graph is already larger than
1470 # that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
1476 # from the root by following a path via at most 3 edges will be shown. Nodes
1479 # code bases. Also note that the size of a graph can be further restricted by
1480 # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
1484 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
1488 # a graph (i.e. they become hard to read).
1500 # generate a legend page explaining the meaning of the various boxes and
1515 # The SEARCHENGINE tag specifies whether or not a search engine should be