188 lines
124 KiB
Plaintext
188 lines
124 KiB
Plaintext
|
b0VIM 7.3 ã{T]„tO dgarcia Liquidity.local ~dgarcia/Documents/Arduino/libraries/FastLED/docs/Doxyfile utf-8
|
|||
|
|
3210 #"! U
|
|||
|
|
W _ X ¶ G
|
|||
|
|
M U W ¢ Q ù M J F — Y Ý T 6 _ Š X é \ A R � U ï [ D S Ÿ * ò ad = © T ï î ¤ y w * ´ £ ˆ Y = ÷
|
|||
|
|
ö
|
|||
|
|
©
|
|||
|
|
�
|
|||
|
|
4
|
|||
|
|
3
|
|||
|
|
æ • F õ Ï ° ¯ � � A ö
|
|||
|
|
©
|
|||
|
|
n
|
|||
|
|
J
|
|||
|
|
I
|
|||
|
|
&
|
|||
|
|
%
|
|||
|
|
Ô † l k N M þ ° e d K J ú ª Y > = $ # Õ … 8 í ì ž M ° e 9 ÿ ² b ì ë Ï Î ‡ @ ú © ¨ # Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Catalan, Chinese, # information to generate all constant output in the proper language. # documentation generated by doxygen is written. Doxygen will use this # The OUTPUT_LANGUAGE tag is used to specify the language in which all ALLOW_UNICODE_NAMES = NO # The default value is: NO. # U+3044. # characters will be escaped, for example _xE3_x81_x84 will be used for Unicode # characters to appear in the names of generated files. If set to NO, non-ASCII # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII CREATE_SUBDIRS = NO # The default value is: NO. # performance problems for the file system. # putting all generated files in the same directory would otherwise causes # option can be useful when feeding doxygen a huge amount of source files, where # will distribute the generated files over these directories. Enabling this # directories (in 2 levels) under the output directory of each output format and # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 4096 sub- OUTPUT_DIRECTORY = # left blank the current directory will be used. # entered, it will be relative to the location where doxygen was started. If # into which the generated documentation will be written. If a relative path is # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path PROJECT_LOGO = # to the output directory. # and the maximum width should not exceed 200 pixels. Doxygen will copy the logo # the documentation. The maximum height of the logo should not exceed 55 pixels # With the PROJECT_LOGO tag one can specify an logo or icon that is included in PROJECT_BRIEF = # quick idea about the purpose of the project. Keep the description short. # for a project that appears at the top of each page and should give viewer a # Using the PROJECT_BRIEF tag one can provide an optional one line description PROJECT_NUMBER = 3.1 # control system is used. # could be handy for archiving the generated documentation or if some version # The PROJECT_NUMBER tag can be used to enter a project or revision number. This PROJECT_NAME = "FastLED" # The default value is: My Project. # title of most generated pages and in a few other places. # project for which the documentation is generated. This name is used in the # double-quotes, unless you are using Doxywizard) that should identify the # The PROJECT_NAME tag is a single word (or a sequence of words surrounded by DOXYFILE_ENCODING = UTF-8 # The default value is: UTF-8. # for the list of possible encodings. # built into libc) for the transcoding. See http://www.gnu.org/software/libiconv # before the first occurrence of this tag. Doxygen uses libiconv (or the iconv # that follow. The default is UTF-8 which is also the encoding used for all text # This tag specifies the encoding used for all characters in the config file #--------------------------------------------------------------------------- # Project related configuration options #--------------------------------------------------------------------------- # Values that contain spaces should be placed between quotes (\" \"). # TAG += value [value, ...] # For lists, items can also be appended using: # TAG = value [value, ...] # The format is: # All text after a single hash (#) is considered a comment and will be ignored. # # front of the TAG it is preceding. # All text after a double hash (##) is considered a comment and is placed in # # doxygen (www.doxygen.org) for a project. # This file describes the settings to be used by the documentation system # Doxyfile 1.8.8 ad ² v * Ã } B í ì ¡ Q / - á
|
|||
|
|
“
|
|||
|
|
Š
|
|||
|
|
n
|
|||
|
|
5
|
|||
|
|
4
|
|||
|
|
|
|||
|
|
|
|||
|
|
Ê { , ÿ ã ª © � Œ = ï
|
|||
|
|
å
|
|||
|
|
È
|
|||
|
|
�
|
|||
|
|
Ž
|
|||
|
|
q
|
|||
|
|
p
|
|||
|
|
|
|||
|
|
ê Í ” “ v u DOT_CLEANUP = YES # This tag requires that the tag HAVE_DOT is set to YES. # The default value is: YES. # files that are used to generate the various graphs. # If the DOT_CLEANUP tag is set to YES doxygen will remove the intermediate dot GENERATE_LEGEND = YES # This tag requires that the tag HAVE_DOT is set to YES. # The default value is: YES. # graphs. # explaining the meaning of the various boxes and arrows in the dot generated # If the GENERATE_LEGEND tag is set to YES doxygen will generate a legend page DOT_MULTI_TARGETS = NO # This tag requires that the tag HAVE_DOT is set to YES. # The default value is: NO. # this, this feature is disabled by default. # makes dot run faster, but since only newer versions of dot (>1.8.10) support # files in one run (i.e. multiple -o and -T options on the command line). This # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output DOT_TRANSPARENT = NO # This tag requires that the tag HAVE_DOT is set to YES. # The default value is: NO. # read). # badly anti-aliased labels on the edges of a graph (i.e. they become hard to # Warning: Depending on the platform used, enabling this option may lead to # # to support this out of the box. # background. This is disabled by default, because dot on Windows does not seem # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent MAX_DOT_GRAPH_DEPTH = 0 # This tag requires that the tag HAVE_DOT is set to YES. # Minimum value: 0, maximum value: 1000, default value: 0. # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction. # note that the size of a graph can be further restricted by ad \ M ± e ß Ã Â ¥ ¤ U ¾
|
|||
|
|
{
|
|||
|
|
a
|
|||
|
|
D
|
|||
|
|
C
|
|||
|
|
&
|
|||
|
|
%
|
|||
|
|
Ô † 7 + ) î Õ ¹ ¸ œ › J ú
|
|||
|
|
³
|
|||
|
|
c
|
|||
|
|
|
|||
|
|
å É È ¬ « ^ À p Ò ƒ g f J I ú © Z º i Ñ œ d c H G ú Ô ‡ † ; ë © f å É È ¬ « \ [ # If the EXTRACT_PRIVATE tag is set to YES all private members of a class will EXTRACT_ALL = NO # The default value is: NO. # normally produced when WARNINGS is set to YES. # Note: This will also disable the warnings about undocumented members that are # EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES. # class members and static file members will be hidden unless the # documentation are documented, even if no documentation was available. Private # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in #--------------------------------------------------------------------------- # Build related configuration options #--------------------------------------------------------------------------- LOOKUP_CACHE_SIZE = 0 # Minimum value: 0, maximum value: 9, default value: 0. # the optimal cache size from a speed point of view. # symbols. At the end of a run doxygen will report the cache usage and suggest # is 0..9, the default is 0, corresponding to a cache size of 2^16=65536 # cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range # doxygen will become slower. If the cache is too large, memory is wasted. The # code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small # an expensive process and often the same symbol appears multiple times in the # cache is used to resolve symbols given their name and scope. Since this can be # The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This TYPEDEF_HIDES_STRUCT = NO # The default value is: NO. # types are typedef'ed and only the typedef is referenced, never the tag name. # useful for C code in case the coding convention dictates that all compound # namespace, or class. And the struct will be named TypeS. This can typically be # with name TypeT. When disabled the typedef will appear as a member of a file, # typedef struct TypeS {} TypeT, will appear in the documentation as a struct # enum is documented as struct, union, or enum with the name of the typedef. So # When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or INLINE_SIMPLE_STRUCTS = NO # The default value is: NO. # Man pages) or section (for LaTeX and RTF). # to NO, structs, classes, and unions are shown on a separate page (for HTML and # namespace, or group documentation), provided this scope is documented. If set # the documentation of the scope in which they are defined (i.e. file, # with only public data fields or simple typedef fields will be shown inline in # When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and unions INLINE_GROUPED_CLASSES = NO # The default value is: NO. # SEPARATE_MEMBER_PAGES. # Note that this feature does not work in combination with # # and RTF). # instead of on a separate page (for HTML and Man pages) or section (for LaTeX # are shown inside the group in which they are included (e.g. using \ingroup) # When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and unions SUBGROUPING = YES # The default value is: YES. # \nosubgrouping command. # subgrouping. Alternatively, this can be done per class using the # type (e.g. under the Public Functions section). Set it to NO to prevent # (for instance a group of public functions) to be put as a subgroup of that # Set the SUBGROUPING tag to YES to allow class member groups of the same type DISTRIBUTE_GROUP_DOC = YES # The default value is: NO. # all members of a group must be documented explicitly. # member in the group (if any) for the other members of the group. By default # tag is set to YES, then doxygen will reuse the documentation of the first # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC ad F Þ _ Ü À ¿ £ ¢ R # ê é š y ] \ @ ? ð
|
|||
|
|
¢
|
|||
|
|
T
|
|||
|
|
@
|
|||
|
|
#
|
|||
|
|
"
|
|||
|
|
|
|||
|
|
|
|||
|
|
´ e í ì Ð Ï
|
|||
|
|
¡
|
|||
|
|
“
|
|||
|
|
w
|
|||
|
|
v
|
|||
|
|
Z
|
|||
|
|
Y
|
|||
|
|
|
|||
|
|
Æ | / ö õ ° ` è Ì Ë ¯ ® _ ñ Õ Ô ¸ · s $ Ú ¾ ½ ¡ V ½ ¡ „ ƒ 3 ê › M í ì Ð Ï € 0 ü û ß Þ Ý HIDE_SCOPE_NAMES = NO # The default value is: NO. # scope will be hidden. # their full class and namespace scopes in the documentation. If set to YES the # If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with CASE_SENSE_NAMES = NO # The default value is: system dependent. # and Mac users are advised to set this option to NO. # in case and if your file system supports case sensitive file names. Windows # allowed. This is useful if you have classes or files whose names only differ # names in lower-case letters. If set to YES upper-case letters are also # If the CASE_SENSE_NAMES tag is set to NO then doxygen will only generate file INTERNAL_DOCS = NO # The default value is: NO. # will be excluded. Set it to YES to include the internal documentation. # \internal command is included. If the tag is set to NO then the documentation # The INTERNAL_DOCS tag determines if documentation that is typed after a HIDE_IN_BODY_DOCS = NO # The default value is: NO. # blocks will be appended to the function's detailed documentation block. # documentation blocks found inside the body of a function. If set to NO these # If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any HIDE_FRIEND_COMPOUNDS = NO # The default value is: NO. # included in the documentation. # (class|struct|union) declarations. If set to NO these declarations will be # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend HIDE_UNDOC_CLASSES = NO # The default value is: NO. # no effect if EXTRACT_ALL is enabled. # to NO these classes will be included in the various overviews. This option has # undocumented classes that are normally visible in the class hierarchy. If set # If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all HIDE_UNDOC_MEMBERS = NO # The default value is: NO. # section is generated. This option has no effect if EXTRACT_ALL is enabled. # members will be included in the various overviews, but no documentation # undocumented members inside documented classes or files. If set to NO these # If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all EXTRACT_ANON_NSPACES = NO # The default value is: NO. # are hidden. # the file that contains the anonymous namespace. By default anonymous namespace # 'anonymous_namespace{file}', where file will be replaced with the base name of # extracted and appear in the documentation as a namespace called # If this flag is set to YES, the members of anonymous namespaces will be EXTRACT_LOCAL_METHODS = NO # The default value is: NO. # included. # included in the documentation. If set to NO only methods in the interface are # which are defined in the implementation section but not in the interface are # This flag is only useful for Objective-C code. When set to YES local methods, EXTRACT_LOCAL_CLASSES = YES # The default value is: YES. # for Java sources. # only classes defined in header files are included. Does not have any effect # locally in source files will be included in the documentation. If set to NO # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) defined EXTRACT_STATIC = NO # The default value is: NO. # included in the documentation. # If the EXTRACT_STATIC tag is set to YES all static members of a file will be EXTRACT_PACKAGE = NO # The default value is: NO. # scope will be included in the documentation. # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal EXTRACT_PRIVATE = NO # The default value is: NO. # be included in the documentation. ad Ý á : ² g J I , + Û Œ X < ; Ï
|
|||
|
|
~
|
|||
|
|
b
|
|||
|
|
a
|
|||
|
|
E
|
|||
|
|
D
|
|||
|
|
ö Ò µ ´ — – O ¾ ¡ ƒ ‚ 6 é
|
|||
|
|
œ
|
|||
|
|
U
|
|||
|
|
9
|
|||
|
|
8
|
|||
|
|
|
|||
|
|
|
|||
|
|
Î . é ˜ € 4 ÷ ö Ú Ù ˆ < ÿ þ á Ç “ B ¶ j b F E ) ( Ø ‡ : ï ¢ ] A @ $ # Õ ’ � d c F E ÷ ´ £ † # # The default value is: YES. # documentation. # test list. This list is created by putting \test commands in the # The GENERATE_TESTLIST tag can be used to enable ( YES) or disable ( NO) the GENERATE_TODOLIST = YES # The default value is: YES. # documentation. # todo list. This list is created by putting \todo commands in the # The GENERATE_TODOLIST tag can be used to enable ( YES) or disable ( NO) the STRICT_PROTO_MATCHING = NO # The default value is: NO. # accept a match between prototype and implementation in such cases. # simple string match. By disabling STRICT_PROTO_MATCHING doxygen will still # only one candidate or it is obvious which candidate to choose by doing a # the prototype and the implementation of a member function even if there is # type resolution of all parameters of a function it will reject a match between # If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper SORT_BY_SCOPE_NAME = NO # The default value is: NO. # list. # Note: This option applies only to the class list, not to the alphabetical # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. # be sorted only by class name, not including the namespace part. # fully-qualified names, including namespaces. If set to NO, the class list will # If the SORT_BY_SCOPE_NAME tag is set to YES, the cSORT_GROUP_NAMES = YSORT_GROUP_NAMES = YES # The default value is: NO. # appear in their defined order. # of group names into alphabetical order. If set to NO the group names will # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the hierarchy SORT_MEMBERS_CTORS_1ST = NO # The default value is: NO. # detailed member documentation. # Note: If SORT_MEMBER_DOCS is set to NO this option is ignored for sorting # member documentation. # Note: If SORT_BRIEF_DOCS is set to NO this option is ignored for sorting brief # respective orders defined by SORT_BRIEF_DOCS and SORT_MEMBER_DOCS. # destructors are listed first. If set to NO the constructors will appear in the # (brief and detailed) documentation of class members so that constructors and # If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the SORT_BRIEF_DOCS = NO # The default value is: NO. # this will also influence the order of the classes in the class list. # name. If set to NO the members will appear in declaration order. Note that # descriptions of file, namespace and class members alphabetically by member # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief SORT_MEMBER_DOCS = YES # The default value is: YES. # name. If set to NO the members will appear in declaration order. # (detailed) documentation of file and class members alphabetically by member # If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the INLINE_INFO = YES # The default value is: YES. # documentation for inline members. # If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the FORCE_LOCAL_INCLUDES = NO # The default value is: NO. # files with double quotes in the documentation rather than with sharp brackets. # If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include SHOW_GROUPED_MEMB_INC = NO # The default value is: NO. # which file to include in order to use the member. # grouped member an include statement to the documentation, telling the reader # If the SHOW_GROUPED_MEMB_INC tag is set to YES then Doxygen will add for each SHOW_INCLUDE_FILES = YES # The default value is: YES. # the files that are included by a file in the documentation of that file. # If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of ad j S ÿ â á � D ' & ¸ i T 7 6 Í
|
|||
|
|
~
|
|||
|
|
g
|
|||
|
|
f
|
|||
|
|
M
|
|||
|
|
L
|
|||
|
|
ü « \ Ã | P ö
|
|||
|
|
õ
|
|||
|
|
§
|
|||
|
|
V
|
|||
|
|
|
|||
|
|
ò ñ Ô Ó ‚ 1 ä ã “ C å ä – E ô § W Õ Ô » º j Ï � 1 · f Q P 7 6 å œ L ý » j # LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the # For LaTeX the style of the bibliography can be controlled using # to be installed. See also http://en.wikipedia.org/wiki/BibTeX for more info. # extension is automatically appended if omitted. This requires the bibtex tool # the reference definitions. This must be a list of .bib files. The .bib # The CITE_BIB_FILES tag can be used to specify one or more bib files containing LAYOUT_FILE = # tag is left empty. # DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE # Note that if you run doxygen from a directory containing a file called # # will be used as the name of the layout file. # optionally specify a file name after the option, if omitted DoxygenLayout.xml # that represents doxygen's defaults, run doxygen with the -l option. You can # output files in an output format independent way. To create the layout file # by doxygen. The layout file controls the global structure of the generated # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed FILE_VERSION_FILTER = # version. For an example see the documentation. # by doxygen. Whatever the program writes to standard output is used as the file # FILE_VERSION_FILTER tag, and input-file is the name of an input file provided # popen()) the command command input-file, where command is the value of the # the version control system). Doxygen will invoke the program by executing (via # doxygen should invoke to get the current version for each file (typically from # The FILE_VERSION_FILTER tag can be used to specify a program or script that SHOW_NAMESPACES = YES # The default value is: YES. # Folder Tree View (if specified). # page. This will remove the Namespaces entry from the Quick Index and from the # Set the SHOW_NAMESPACES tag to NO to disable the generation of the Namespaces SHOW_FILES = YES # The default value is: YES. # (if specified). # will remove the Files entry from the Quick Index and from the Folder Tree View # Set the SHOW_FILES tag to NO to disable the generation of the Files page. This SHOW_USED_FILES = YES # The default value is: YES. # will mention the files that were used to generate the documentation. # the bottom of the documentation of classes and structs. If set to YES the list # Set the SHOW_USED_FILES tag to NO to disable the list of files generated at MAX_INITIALIZER_LINES = 30 # Minimum value: 0, maximum value: 10000, default value: 30. # documentation regardless of this setting. # controlled using \showinitializer or \hideinitializer command in the # appearance of the value of individual variables and macros / defines can be # it will be hidden. Use a value of 0 to hide initializers completely. The # documentation. If the initializer consists of more lines than specified here # initial value of a variable or macro / define can have for it to appear in the # The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the ENABLED_SECTIONS = # ... \endcond blocks. # sections, marked by \if <section_label> ... \endif and \cond <section_label> # The ENABLED_SECTIONS tag can be used to enable conditional documentation GENERATE_DEPRECATEDLIST= YES # The default value is: YES. # the documentation. # the deprecated list. This list is created by putting \deprecated commands in # The GENERATE_DEPRECATEDLIST tag can be used to enable ( YES) or disable ( NO) GENERATE_BUGLIST = YES # The default value is: YES. # list. This list is created by putting \bug commands in the documentation. # The GENERATE_BUGLIST tag can be used to enable ( YES) or disable ( NO) the bug GENERATE_TESTLIST = YES ad > ¶ W ¿ ¾ ¥ ¤ W É È z / ÿ
|
|||
|
|
þ
|
|||
|
|
â
|
|||
|
|
á
|
|||
|
|
•
|
|||
|
|
G
|
|||
|
|
|
|||
|
|
|
|||
|
|
ã Æ Å ¨ § [
|
|||
|
|
è Ë Ê ¬ [
|
|||
|
|
º
|
|||
|
|
Ÿ
|
|||
|
|
‚
|
|||
|
|
�
|
|||
|
|
d
|
|||
|
|
c
|
|||
|
|
|
|||
|
|
Ç v 9 ÿ ® ] ½ w ` 4 3 ´ f T S : 9 ì ¹ l k × ‰ ? > % $ × ‡ 7 ë Õ ¶ µ – • O ¶ µ # *.h) to filter out the source-files in the directories. If left blank the # FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and # If the value of the INPUT tag contains directories, you can use the INPUT_ENCODING = UTF-8 # The default value is: UTF-8. # possible encodings. # documentation (see: http://www.gnu.org/software/libiconv) for the list of # libiconv (or the iconv built into libc) for the transcoding. See the libiconv # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses # This tag can be used to specify the character encoding of the source files INPUT = # Note: If this tag is empty the current directory is searched. # spaces. # directories like /usr/src/myproject. Separate the files or directories with # documented source files. You may enter file names like myfile.cpp or # The INPUT tag is used to specify the files and/or directories that contain #--------------------------------------------------------------------------- # Configuration options related to the input files #--------------------------------------------------------------------------- WARN_LOGFILE = # error (stderr). # messages should be written. If left blank the output is written to standard # The WARN_LOGFILE tag can be used to specify a file to which warning and error WARN_FORMAT = "$file:$line: $text" # The default value is: $file:$line: $text. # FILE_VERSION_FILTER) # be replaced by the version of the file (if it could be obtained via # and the warning text. Optionally the format may contain $version, which will # will be replaced by the file and line number from which the warning originated # can produce. The string should contain the $file, $line, and $text tags, which # The WARN_FORMAT tag determines the format of the warning messages that doxygen WARN_NO_PARAMDOC = NO # The default value is: NO. # documentation, but not about the absence of documentation. # value. If set to NO doxygen will only warn about wrong or incomplete parameter # are documented, but have no documentation for their parameters or return # This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that WARN_IF_DOC_ERROR = YES # The default value is: YES. # markup commands wrongly. # in a documented function, or documenting parameters that don't exist or using # potential errors in the documentation, such as not documenting some parameters # If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for WARN_IF_UNDOCUMENTED = YES # The default value is: YES. # will automatically be disabled. # warnings for undocumented members. If EXTRACT_ALL is set to YES then this flag # If the WARN_IF_UNDOCUMENTED tag is set to YES, then doxygen will generate WARNINGS = YES # The default value is: YES. # Tip: Turn warnings on while writing the documentation. # # this implies that the warnings are on. # generated to standard error ( stderr) by doxygen. If WARNINGS is set to YES # The WARNINGS tag can be used to turn on/off the warning messages that are QUIET = NO # The default value is: NO. # messages are off. # standard output by doxygen. If QUIET is set to YES this implies that the # The QUIET tag can be used to turn on/off the messages that are generated to #--------------------------------------------------------------------------- # Configuration options related to warning and progress messages #--------------------------------------------------------------------------- CITE_BIB_FILES = # search path. See also \cite for info how to create references. ad H Ø ] ² f Ï · ¶ � œ L % ì
|
|||
|
|
ë
|
|||
|
|
š
|
|||
|
|
P
|
|||
|
|
ÿ ý ® § ¦ � Œ C ó á Å Ä ¨ § a î
|
|||
|
|
ì
|
|||
|
|
›
|
|||
|
|
W
|
|||
|
|
V
|
|||
|
|
=
|
|||
|
|
<
|
|||
|
|
ò ¨ ] ô ò ¡ i h O N ÿ µ © ¨ � Ž A ò ¦ � � v u , Û © � Œ p o " Ö Ã Â © ¨ \
|
|||
|
|
ã á É Ç x . ß Ì Ê | + ó ò Ù Ø × INPUT_FILTER = # or removed, the anchors will not be placed correctly. # code is scanned, but not when the output code is generated. If lines are added # Note that the filter must not add or remove lines; it is applied before the # # will be ignored. # program writes to standard output. If FILTER_PATTERNS is specified, this tag # name of an input file. Doxygen will then use the output that the filter # where <filter> is the value of the INPUT_FILTER tag, and <input-file> is the # # <filter> <input-file> # # by executing (via popen()) the command: # invoke to filter for each input file. Doxygen will invoke the filter program # The INPUT_FILTER tag can be used to specify a program that doxygen should IMAGE_PATH = # \image command). # that contain images that are to be included in the documentation (see the # The IMAGE_PATH tag can be used to specify one or more files or directories EXAMPLE_RECURSIVE = NO # The default value is: NO. # irrespective of the value of the RECURSIVE tag. # searched for input files to be used with the \include or \dontinclude commands # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be EXAMPLE_PATTERNS = # files are included. # *.h) to filter out the source-files in the directories. If left blank all # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and # If the value of the EXAMPLE_PATH tag contains directories, you can use the EXAMPLE_PATH = # command). # that contain example code fragments that are included (see the \include # The EXAMPLE_PATH tag can be used to specify one or more files or directories EXCLUDE_SYMBOLS = # exclude all test directories use the pattern */test/* # Note that the wildcards are matched against the file with absolute path, so to # # AClass::ANamespace, ANamespace::*Test # wildcard * is used, a substring. Examples: ANamespace, AClass, # output. The symbol name can be a fully qualified name, a word, or if the # (namespaces, classes, functions, etc.) that should be excluded from the # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names EXCLUDE_PATTERNS = # exclude all test directories for example use the pattern */test/* # Note that the wildcards are matched against the file with absolute path, so to # # certain files from those directories. # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude # If the value of the INPUT tag contains directories, you can use the EXCLUDE_SYMLINKS = NO # The default value is: NO. # from the input. # directories that are symbolic links (a Unix file system feature) are excluded # The EXCLUDE_SYMLINKS tag can be used to select whether or not files or EXCLUDE = # run. # Note that relative paths are relative to the directory from which doxygen is # # subdirectory from a directory tree whose root is specified with the INPUT tag. # excluded from the INPUT source files. This way you can easily exclude a # The EXCLUDE tag can be used to specify files and/or directories that should be RECURSIVE = NO # The default value is: NO. # be searched for input files as well. # The RECURSIVE tag can be used to specify whether or not subdirectories should FILE_PATTERNS = # *.qsf, *.as and *.js. # *.md, *.mm, *.dox, *.py, *.f90, *.f, *.for, *.tcl, *.vhd, *.vhdl, *.ucf, # *.h++, *.cs, *.d, *.php, *.php4, *.php5, *.phtml, *.inc, *.m, *.markdown, # *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h, *.hh, *.hxx, *.hpp, # following patterns are tested:*.c, *.cc, *.cxx, *.cpp, *.c++, *.java, *.ii, ad 7 ¯ W ± e Æ | C B ) ( Ù
|
|||
|
|
Š
|
|||
|
|
9
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
ÿ ¯ ` ê ¦ ¥ Œ ‹ < ÷
|
|||
|
|
§
|
|||
|
|
`
|
|||
|
|
_
|
|||
|
|
F
|
|||
|
|
E
|
|||
|
|
ø Å x w ) Û Ù ‹ e I H , + ß ª Ž � q p ! Ð ¡ „ ƒ f e × » º ž � L é è Ì Ë { 3 â Å ¨ § Š ‰ : é › M *
|
|||
|
|
Î Í ° ¯ ® SOURCE_TOOLTIPS = YES # This tag requires that the tag SOURCE_BROWSER is set to YES. # The default value is: YES. # can opt to disable this feature. # will make the HTML file larger and loading of large files a bit slower, you # brief description and links to the definition and documentation. Since this # source code will show a tooltip with additional information such as prototype, # If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the REFERENCES_LINK_SOURCE = YES # The default value is: YES. # link to the documentation. # REFERENCED_BY_RELATION lists will link to the source code. Otherwise they will # to YES, then the hyperlinks from functions in REFERENCES_RELATION and # If the REFERENCES_LINK_SOURCE tag is set to YES and SOURCE_BROWSER tag is set REFERENCES_RELATION = NO # The default value is: NO. # all documented entities called/used by that function will be listed. # If the REFERENCES_RELATION tag is set to YES then for each documented function REFERENCED_BY_RELATION = NO # The default value is: NO. # function all documented functions referencing it will be listed. # If the REFERENCED_BY_RELATION tag is set to YES then for each documented STRIP_CODE_COMMENTS = YES # The default value is: YES. # Fortran comments will always remain visible. # special comment blocks from generated source code fragments. Normal C, C++ and # Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any INLINE_SOURCES = NO # The default value is: NO. # classes and enums directly into the documentation. # Setting the INLINE_SOURCES tag to YES will include the body of functions, SOURCE_BROWSER = NO # The default value is: NO. # also VERBATIM_HEADERS is set to NO. # Note: To get rid of all source code in the generated output, make sure that # # generated. Documented entities will be cross-referenced with these sources. # If the SOURCE_BROWSER tag is set to YES then a list of source files will be #--------------------------------------------------------------------------- # Configuration options related to source browsing #--------------------------------------------------------------------------- USE_MDFILE_AS_MAINPAGE = # and want to reuse the introduction page also for the doxygen output. # (index.html). This can be useful if you have a project on for instance GitHub # is part of the input, its contents will be placed on the main page # If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that FILTER_SOURCE_PATTERNS = # This tag requires that the tag FILTER_SOURCE_FILES is set to YES. # *.ext= (so without naming a filter). # it is also possible to disable source filtering for a specific pattern using # pattern. A pattern will override the setting for FILTER_PATTERN (if any) and # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file FILTER_SOURCE_FILES = NO # The default value is: NO. # producing the source files to browse (i.e. when SOURCE_BROWSER is set to YES). # INPUT_FILTER ) will also be used to filter the input files that are used for # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using FILTER_PATTERNS = # patterns match the file name, INPUT_FILTER is applied. # filters are used. If the FILTER_PATTERNS tag is empty or if none of the # (like *.cpp=my_cpp_filter). See INPUT_FILTER for further information on how # filter if there is a match. The filters are a list of the form: pattern=filter # basis. Doxygen will compare the file name with each pattern and apply the # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern ad
|
|||
|
|
† X ³ d Ç ´ ² ” k 0 ò
|
|||
|
|
Ø
|
|||
|
|
Ö
|
|||
|
|
‹
|
|||
|
|
@
|
|||
|
|
>
|
|||
|
|
ï º ž _ ^ B A ÷ … i L K . - à
|
|||
|
|
|
|||
|
|
S
|
|||
|
|
R
|
|||
|
|
|
|||
|
|
º � s r U T Ó š W V ; : ê š I # à ß Æ Å x E ø ÷ ¬ � Ž q p ! Ð Ê ¨ j i B A ð ¹ š \ [ < ; ê � Š ˆ 9 è � † … # default header using # the setting GENERATE_TREEVIEW). It is highly recommended to start with a # that doxygen needs, which is dependent on the configuration options used (e.g. # To get valid HTML the header file that includes any scripts and style sheets # # standard header. # each generated HTML page. If the tag is left blank doxygen will generate a # The HTML_HEADER tag can be used to specify a user-defined HTML header file for HTML_FILE_EXTENSION = .html # This tag requires that the tag GENERATE_HTML is set to YES. # The default value is: .html. # generated HTML page (for example: .htm, .php, .asp). # The HTML_FILE_EXTENSION tag can be used to specify the file extension for each HTML_OUTPUT = html/docs/3.1 # This tag requires that the tag GENERATE_HTML is set to YES. # The default directory is: html. # it. # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a GENERATE_HTML = YES # The default value is: YES. # If the GENERATE_HTML tag is set to YES doxygen will generate HTML output #--------------------------------------------------------------------------- # Configuration options related to the HTML output #--------------------------------------------------------------------------- IGNORE_PREFIX = # This tag requires that the tag ALPHABETICAL_INDEX is set to YES. # while generating the index headers. # can be used to specify a prefix (or a list of prefixes) that should be ignored # be put under the same header in the alphabetical index. The IGNORE_PREFIX tag # In case all classes in a project start with a common prefix, all classes will COLS_IN_ALPHA_INDEX = 5 # This tag requires that the tag ALPHABETICAL_INDEX is set to YES. # Minimum value: 1, maximum value: 20, default value: 5. # which the alphabetical index list will be split. # The COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns in ALPHABETICAL_INDEX = YES # The default value is: YES. # classes, structs, unions or interfaces. # compounds will be generated. Enable this if the project contains a lot of # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index of all #--------------------------------------------------------------------------- # Configuration options related to the alphabetical class index #--------------------------------------------------------------------------- VERBATIM_HEADERS = YES # The default value is: YES. # See also: Section \class. # specified. Set to NO to disable this. # verbatim copy of the header file for each class for which an include is # If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a USE_HTAGS = NO # This tag requires that the tag SOURCE_BROWSER is set to YES. # The default value is: NO. # source code will now point to the output of htags. # The result: instead of the source browser generated by doxygen, the links to # # tools must be available from the command line (i.e. in the search path). # Doxygen will invoke htags (and that will in turn invoke gtags), so these # # - Run doxygen as normal # - Make sure the INPUT points to the root of the source tree # - Enable SOURCE_BROWSER and USE_HTAGS in the config file # - Install the latest version of global # To use it do the following: # # 4.8.6 or higher. # (see http://www.gnu.org/software/global/global.html). You will need version # source browser. The htags tool is part of GNU's global source tagging system # point to the HTML generated by the htags(1) tool instead of doxygen built-in # If the USE_HTAGS tag is set to YES then the references to source code will ad S G » ª ] · f % ç
|
|||
|
|
æ
|
|||
|
|
Í
|
|||
|
|
Ì
|
|||
|
|
{
|
|||
|
|
*
|
|||
|
|
Þ “ C % ç æ Í Ì | , Þ
|
|||
|
|
Ž
|
|||
|
|
j
|
|||
|
|
|
|||
|
|
Î Â „ ƒ j i Ï 2 ç ¤ T Ú œ › ‚ � 3 ä — J ù ¯ q p W V » { + Ý ½ � C B % $ Ô † S R # value of 255 will produce the most vivid colors. # in the HTML output. For a value of 0 the output will use grayscales only. A # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors HTML_COLORSTYLE_HUE = 220 # This tag requires that the tag GENERATE_HTML is set to YES. # Minimum value: 0, maximum value: 359, default value: 220. # purple, and 360 is red again. # 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300 # http://en.wikipedia.org/wiki/Hue for more information. For instance the value # this color. Hue is specified as an angle on a colorwheel, see # will adjust the colors in the stylesheet and background images according to # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen HTML_EXTRA_FILES = # This tag requires that the tag GENERATE_HTML is set to YES. # files will be copied as-is; there are no commands or markers available. # files. In the HTML_STYLESHEET file, use the file name only. Also note that the # $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these # that these files will be copied to the base HTML output directory. Use the # other source files which should be copied to the HTML output directory. Note # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or HTML_EXTRA_STYLESHEET = # This tag requires that the tag GENERATE_HTML is set to YES. # list). For an example see the documentation. # stylesheet in the list overrules the setting of the previous ones in the # Note: The order of the extra stylesheet files is of importance (e.g. the last # Doxygen will copy the style sheet files to the output directory. # standard style sheet and is therefor more robust against future updates. # This is preferred over using HTML_STYLESHEET since it does not replace the # created by doxygen. Using this option one can overrule certain style aspects. # cascading style sheets that are included after the standard style sheets # The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined HTML_STYLESHEET = # This tag requires that the tag GENERATE_HTML is set to YES. # obsolete. # it is more robust and this tag (HTML_STYLESHEET) will in the future become # Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as # sheet that doxygen normally uses. # See also section "Doxygen usage" for information on how to generate the style # the HTML output. If left blank doxygen will generate a default style sheet. # sheet that is used by each HTML page. It can be used to fine-tune the look of # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style HTML_FOOTER = # This tag requires that the tag GENERATE_HTML is set to YES. # that doxygen normally uses. # section "Doxygen usage" for information on how to generate the default footer # footer and what special commands can be used inside the footer. See also # footer. See HTML_HEADER for more information on how to generate a default # generated HTML page. If the tag is left blank doxygen will generate a standard # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each HTML_HEADER = # This tag requires that the tag GENERATE_HTML is set to YES. # of the possible markers and block names see the documentation. # default header when upgrading to a newer version of doxygen. For a description # Note: The header is subject to change so you typically have to regenerate the # uses. # for information on how to generate the default header that doxygen normally # and then modify the file new_header.html. See also section "Doxygen usage" # YourConfigFile # doxygen -w html new_header.html new_footer.html new_stylesheet.css ad h M Ä † … h g Ñ ƒ 2 æ
|
|||
|
|
Ò
|
|||
|
|
–
|
|||
|
|
X
|
|||
|
|
W
|
|||
|
|
;
|
|||
|
|
:
|
|||
|
|
é ™ \ ? ã â ™ L 9
|
|||
|
|
Þ
|
|||
|
|
Â
|
|||
|
|
Á
|
|||
|
|
s
|
|||
|
|
%
|
|||
|
|
Ø ˆ 8 è ˜ … H
|
|||
|
|
ì ë O ´ c Í } e I
|
|||
|
|
î í œ O è ¨ § u t & à � p 0 / ² h g # the documentation publisher. This should be a reverse domain-name style # The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify DOCSET_BUNDLE_ID = org.doxygen.Project # This tag requires that the tag GENERATE_DOCSET is set to YES. # The default value is: org.doxygen.Project. # com.mycompany.MyDocSet. Doxygen will append .docset to the name. # set bundle. This should be a reverse domain-name style string, e.g. # This tag specifies a string that should uniquely identify the documentation DOCSET_FEEDNAME = "Doxygen generated docs" # This tag requires that the tag GENERATE_DOCSET is set to YES. # The default value is: Doxygen generated docs. # (such as a company or product suite) can be grouped. # an umbrella under which multiple documentation sets from a single provider # This tag determines the name of the docset feed. A documentation feed provides GENERATE_DOCSET = NO # This tag requires that the tag GENERATE_HTML is set to YES. # The default value is: NO. # for more information. # startup. See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at # that directory and running make install will install the docset in # Makefile in the HTML output directory. Running make will produce the docset in # OSX 10.5 (Leopard). To create a documentation set, doxygen will generate a # environment (see: http://developer.apple.com/tools/xcode/), introduced with # generated that can be used as input for Apple's Xcode 3 integrated development # If the GENERATE_DOCSET tag is set to YES, additional index files will be HTML_INDEX_NUM_ENTRIES = 100 # This tag requires that the tag GENERATE_HTML is set to YES. # Minimum value: 0, maximum value: 9999, default value: 100. # tree by default. # representing an infinite number of entries and will result in a full expanded # entries 1 will produce a full collapsed tree by default. 0 is a special value # a fully collapsed tree already exceeds this amount). So setting the number of # such a level that at most the specified number of entries are visible (unless # and collapse entries dynamically later on. Doxygen will expand the tree to # shown in the various tree structured indices initially; the user can expand # With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries HTML_DYNAMIC_SECTIONS = NO # This tag requires that the tag GENERATE_HTML is set to YES. # The default value is: NO. # page has loaded. # documentation will contain sections that can be hidden and shown after the # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML HTML_TIMESTAMP = YES # This tag requires that the tag GENERATE_HTML is set to YES. # The default value is: YES. # to NO can help when comparing the output of multiple runs. # page will contain the date and time when the page was generated. Setting this # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML HTML_COLORSTYLE_GAMMA = 80 # This tag requires that the tag GENERATE_HTML is set to YES. # Minimum value: 40, maximum value: 240, default value: 80. # change the gamma. # a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not # darker. The value divided by 100 is the actual gamma applied, so 80 represents # gradually make the output lighter, whereas values above 100 make the output # luminance component of the colors in the HTML output. Values below 100 # The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the HTML_COLORSTYLE_SAT = 100 # This tag requires that the tag GENERATE_HTML is set to YES. # Minimum value: 0, maximum value: 255, default value: 100. ad € W Ë œ \ [ , + ã À € \ [ É
|
|||
|
|
x
|
|||
|
|
.
|
|||
|
|
#
|
|||
|
|
!
|
|||
|
|
Ó … 8 è ˜ M 4 Ú
|
|||
|
|
Ù
|
|||
|
|
½
|
|||
|
|
¼
|
|||
|
|
n
|
|||
|
|
"
|
|||
|
|
ú ¸ · ž � S ¼ � K J 1 0 â ž ‚ @ ? # " Ñ µ s r Y X » ’ v 4 3 Æ y ] þ ý º l î Ò ” “ w v & Ø ¾ � € # This tag requires that the tag GENERATE_QHP is set to YES. # the HTML output folder. # the file name of the resulting .qch file. The path specified is relative to # If the QHG_LOCATION tag is specified, the QCH_FILE tag can be used to specify GENERATE_QHP = NO # This tag requires that the tag GENERATE_HTML is set to YES. # The default value is: NO. # (.qch) of the generated HTML documentation. # can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and TOC_EXPAND = NO # This tag requires that the tag GENERATE_HTMLHELP is set to YES. # The default value is: NO. # the table of contents of the HTML help documentation and to the tree view. # The TOC_EXPAND flag can be set to YES to add extra items for group members to BINARY_TOC = NO # This tag requires that the tag GENERATE_HTMLHELP is set to YES. # The default value is: NO. # enables the Previous and Next buttons. # YES) or a normal table of contents ( NO) in the .chm file. Furthermore it # The BINARY_TOC flag controls whether a binary table of contents is generated ( CHM_INDEX_ENCODING = # This tag requires that the tag GENERATE_HTMLHELP is set to YES. # and project file content. # The CHM_INDEX_ENCODING is used to encode HtmlHelp index ( hhk), content ( hhc) GENERATE_CHI = NO # This tag requires that the tag GENERATE_HTMLHELP is set to YES. # The default value is: NO. # YES) or that it should be included in the master .chm file ( NO). # The GENERATE_CHI flag controls if a separate .chi index file is generated ( HHC_LOCATION = # This tag requires that the tag GENERATE_HTMLHELP is set to YES. # The file has to be specified with full path. # doxygen will try to run the HTML help compiler on the generated index.hhp. # including file name) of the HTML help compiler ( hhc.exe). If non-empty # The HHC_LOCATION tag can be used to specify the location (absolute path CHM_FILE = # This tag requires that the tag GENERATE_HTMLHELP is set to YES. # written to the html output directory. # file. You can add a path in front of the file if the result should not be # The CHM_FILE tag can be used to specify the file name of the resulting .chm GENERATE_HTMLHELP = NO # This tag requires that the tag GENERATE_HTML is set to YES. # The default value is: NO. # compressed HTML files. # words in the documentation. The HTML workshop also contains a viewer for # HTML files also contain an index, a table of contents, and you can search for # Windows help format (.hlp) on all Windows platforms in the future. Compressed # files are now used as the Windows 98 help format, and will replace the old # generated by doxygen into a single compiled HTML file (.chm). Compiled HTML # The HTML Help Workshop contains a compiler that can convert all HTML output # # Windows. # (see: http://www.microsoft.com/en-us/download/details.aspx?id=21138) on # index.hhp is a project file that can be read by Microsoft's HTML Help Workshop # additional HTML index files: index.hhp, index.hhc, and index.hhk. The # If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three DOCSET_PUBLISHER_NAME = Publisher # This tag requires that the tag GENERATE_DOCSET is set to YES. # The default value is: Publisher. # The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher. DOCSET_PUBLISHER_ID = org.doxygen.Publisher # This tag requires that the tag GENERATE_DOCSET is set to YES. # The default value is: org.doxygen.Publisher. # string, e.g. com.mycompany.MyDocSet.documentation. ad z Q ç æ — I Ô — – i h È
|
|||
|
|
{
|
|||
|
|
o
|
|||
|
|
R
|
|||
|
|
|
|||
|
|
|
|||
|
|
÷ ö ª ` Ë Ê ± ° d Ç
|
|||
|
|
»
|
|||
|
|
~
|
|||
|
|
}
|
|||
|
|
d
|
|||
|
|
c
|
|||
|
|
|
|||
|
|
Ë � D C * ) æ ™ ‚ E D + * Ú Š > í � N ë ¬ � � A ô µ ˆ C B Ä ~ - Ý Œ ; á à Ä Ã z y # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index DISABLE_INDEX = NO # This tag requires that the tag GENERATE_HTML is set to YES. # The default value is: NO. # tree, you can set this option to YES if you also set GENERATE_TREEVIEW to YES. # it. Since the tabs in the index contain the same information as the navigation # of each HTML page. A value of NO enables the index and the value YES disables # DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) at top # be necessary to disable the index and replace it with your own. The # If you want full control over the layout of the generated HTML pages it might ECLIPSE_DOC_ID = org.doxygen.Project # This tag requires that the tag GENERATE_ECLIPSEHELP is set to YES. # The default value is: org.doxygen.Project. # name. Each documentation set should have its own identifier. # the directory name containing the HTML and XML files should also have this # A unique identifier for the Eclipse help plugin. When installing the plugin GENERATE_ECLIPSEHELP = NO # This tag requires that the tag GENERATE_HTML is set to YES. # The default value is: NO. # After copying Eclipse needs to be restarted before the help appears. # within the plugins directory should be the same as the ECLIPSE_DOC_ID value. # to be copied into the plugins directory of eclipse. The name of the directory # Eclipse, the contents of the directory containing the HTML and XML files needs # install this plugin and make it available under the help contents menu in # generated, together with the HTML files, they form an Eclipse help plugin. To # If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be QHG_LOCATION = # This tag requires that the tag GENERATE_QHP is set to YES. # generated .qhp file. # qhelpgenerator. If non-empty doxygen will try to run qhelpgenerator on the # The QHG_LOCATION tag can be used to specify the location of Qt's QHP_SECT_FILTER_ATTRS = # This tag requires that the tag GENERATE_QHP is set to YES. # http://qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes). # project's filter section matches. Qt Help Project / Filter Attributes (see: # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this QHP_CUST_FILTER_ATTRS = # This tag requires that the tag GENERATE_QHP is set to YES. # filters). # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom- # custom filter to add. For more information please see Qt Help Project / Custom # The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the QHP_CUST_FILTER_NAME = # This tag requires that the tag GENERATE_QHP is set to YES. # filters). # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom- # filter to add. For more information please see Qt Help Project / Custom # If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom QHP_VIRTUAL_FOLDER = doc # This tag requires that the tag GENERATE_QHP is set to YES. # The default value is: doc. # folders). # Folders (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#virtual- # Help Project output. For more information please see Qt Help Project / Virtual # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt QHP_NAMESPACE = org.doxygen.Project # This tag requires that the tag GENERATE_QHP is set to YES. # The default value is: org.doxygen.Project. # (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#namespace). # Project output. For more information please see Qt Help Project / Namespace # The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help QCH_FILE = ad ^ M ° c à v & Ú
|
|||
|
|
Œ
|