llvm.org GIT mirror llvm / 80626a7
Upgrade in preparation for doxygen 1.4.4. The config file format changed, there are new/different css styles to support, and the footer was woefully out of date. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@28308 91177308-0d34-0410-b5e6-96231b3b80d8 Reid Spencer 13 years ago
3 changed file(s) with 881 addition(s) and 227 deletion(s). Raw diff Collapse all Expand all
None # Doxyfile 1.2.13.1
0 # Doxyfile 1.4.4
11
22 # This file describes the settings to be used by the documentation system
33 # doxygen (www.doxygen.org) for a project
1010 # Values that contain spaces should be placed between quotes (" ")
1111
1212 #---------------------------------------------------------------------------
13 # General configuration options
13 # Project related configuration options
1414 #---------------------------------------------------------------------------
1515
1616 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded
3131
3232 OUTPUT_DIRECTORY = @abs_top_builddir@/docs/doxygen
3333
34 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
35 # 4096 sub-directories (in 2 levels) under the output directory of each output
36 # format and will distribute the generated files over these directories.
37 # Enabling this option can be useful when feeding doxygen a huge amount of
38 # source files, where putting all generated files in the same directory would
39 # otherwise cause performance problems for the file system.
40
41 CREATE_SUBDIRS = NO
42
3443 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
3544 # documentation generated by doxygen is written. Doxygen will use this
3645 # information to generate all constant output in the proper language.
3746 # The default language is English, other supported languages are:
38 # Brazilian, Chinese, Croatian, Czech, Danish, Dutch, Finnish, French,
39 # German, Greek, Hungarian, Italian, Japanese, Korean, Norwegian, Polish,
40 # Portuguese, Romanian, Russian, Slovak, Slovene, Spanish and Swedish.
47 # Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish,
48 # Dutch, Finnish, French, German, Greek, Hungarian, Italian, Japanese,
49 # Japanese-en (Japanese with English messages), Korean, Korean-en, Norwegian,
50 # Polish, Portuguese, Romanian, Russian, Serbian, Slovak, Slovene, Spanish,
51 # Swedish, and Ukrainian.
4152
4253 OUTPUT_LANGUAGE = English
54
55 # This tag can be used to specify the encoding used in the generated output.
56 # The encoding is not always determined by the language that is chosen,
57 # but also whether or not the output is meant for Windows or non-Windows users.
58 # In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES
59 # forces the Windows encoding (this is the default for the Windows binary),
60 # whereas setting the tag to NO uses a Unix-style encoding (the default for
61 # all platforms other than Windows).
62
63 USE_WINDOWS_ENCODING = NO
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
70 BRIEF_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
77 REPEAT_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
89 ABBREVIATE_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
95 ALWAYS_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
102 INLINE_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
108 FULL_PATH_NAMES = NO
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
117 STRIP_FROM_PATH = ../..
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
126 STRIP_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
132 SHORT_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 the Qt-style comments (thus requiring an
138 # explicit @brief command for a brief description.
139
140 JAVADOC_AUTOBRIEF = NO
141
142 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
143 # treat a multi-line C++ special comment block (i.e. a block of //! or ///
144 # comments) as a brief description. This used to be the default behaviour.
145 # The new default is to treat a multi-line C++ comment block as a detailed
146 # description. Set this tag to YES if you prefer the old behaviour instead.
147
148 MULTILINE_CPP_IS_BRIEF = NO
149
150 # If the DETAILS_AT_TOP tag is set to YES then Doxygen
151 # will output the detailed description near the top, like JavaDoc.
152 # If set to NO, the detailed description appears after the member
153 # documentation.
154
155 DETAILS_AT_TOP = NO
156
157 # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
158 # member inherits the documentation from any documented member that it
159 # re-implements.
160
161 INHERIT_DOCS = YES
162
163 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
164 # tag is set to YES, then doxygen will reuse the documentation of the first
165 # member in the group (if any) for the other members of the group. By default
166 # all members of a group must be documented explicitly.
167
168 DISTRIBUTE_GROUP_DOC = NO
169
170 # If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
171 # a new page for each member. If set to NO, the documentation of a member will
172 # be part of the file/class/namespace that contains it.
173
174 SEPARATE_MEMBER_PAGES = NO
175
176 # The TAB_SIZE tag can be used to set the number of spaces in a tab.
177 # Doxygen uses this value to replace tabs by spaces in code fragments.
178
179 TAB_SIZE = 2
180
181 # This tag can be used to specify a number of aliases that acts
182 # as commands in the documentation. An alias has the form "name=value".
183 # For example adding "sideeffect=\par Side Effects:\n" will allow you to
184 # put the command \sideeffect (or @sideeffect) in the documentation, which
185 # will result in a user-defined paragraph with heading "Side Effects:".
186 # You can put \n's in the value part of an alias to insert newlines.
187
188 ALIASES =
189
190 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
191 # sources only. Doxygen will then generate output that is more tailored for C.
192 # For instance, some of the names that are used will be different. The list
193 # of all members will be omitted, etc.
194
195 OPTIMIZE_OUTPUT_FOR_C = NO
196
197 # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources
198 # only. Doxygen will then generate output that is more tailored for Java.
199 # For instance, namespaces will be presented as packages, qualified scopes
200 # will look different, etc.
201
202 OPTIMIZE_OUTPUT_JAVA = NO
203
204 # Set the SUBGROUPING tag to YES (the default) to allow class member groups of
205 # the same type (for instance a group of public functions) to be put as a
206 # subgroup of that type (e.g. under the Public Functions section). Set it to
207 # NO to prevent subgrouping. Alternatively, this can be done per class using
208 # the \nosubgrouping command.
209
210 SUBGROUPING = YES
211
212 #---------------------------------------------------------------------------
213 # Build related configuration options
214 #---------------------------------------------------------------------------
43215
44216 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
45217 # documentation are documented, even if no documentation was available.
63235 # If set to NO only classes defined in header files are included.
64236
65237 EXTRACT_LOCAL_CLASSES = YES
238
239 # This flag is only useful for Objective-C code. When set to YES local
240 # methods, which are defined in the implementation section but not in
241 # the interface are included in the documentation.
242 # If set to NO (the default) only methods in the interface are included.
243
244 EXTRACT_LOCAL_METHODS = NO
66245
67246 # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
68247 # undocumented members of documented classes, files or namespaces.
74253
75254 # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
76255 # undocumented classes that are normally visible in the class hierarchy.
77 # If set to NO (the default) these class will be included in the various
256 # If set to NO (the default) these classes will be included in the various
78257 # overviews. This option has no effect if EXTRACT_ALL is enabled.
79258
80259 HIDE_UNDOC_CLASSES = NO
81260
82 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
83 # include brief member descriptions after the members that are listed in
84 # the file and class documentation (similar to JavaDoc).
85 # Set to NO to disable this.
86
87 BRIEF_MEMBER_DESC = YES
88
89 # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
90 # the brief description of a member or function before the detailed description.
91 # Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
92 # brief descriptions will be completely suppressed.
93
94 REPEAT_BRIEF = YES
95
96 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
97 # Doxygen will generate a detailed section even if there is only a brief
98 # description.
99
100 ALWAYS_DETAILED_SEC = NO
101
102 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
103 # inherited members of a class in the documentation of that class as if those
104 # members were ordinary class members. Constructors, destructors and assignment
105 # operators of the base classes will not be shown.
106
107 INLINE_INHERITED_MEMB = NO
108
109 # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
110 # path before files name in the file list and in the header files. If set
111 # to NO the shortest path that makes the file name unique will be used.
112
113 FULL_PATH_NAMES = NO
114
115 # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
116 # can be used to strip a user defined part of the path. Stripping is
117 # only done if one of the specified strings matches the left-hand part of
118 # the path. It is allowed to use relative paths in the argument list.
119
120 STRIP_FROM_PATH = ../..
261 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
262 # friend (class|struct|union) declarations.
263 # If set to NO (the default) these declarations will be included in the
264 # documentation.
265
266 HIDE_FRIEND_COMPOUNDS = NO
267
268 # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
269 # documentation blocks found inside the body of a function.
270 # If set to NO (the default) these blocks will be appended to the
271 # function's detailed documentation block.
272
273 HIDE_IN_BODY_DOCS = NO
121274
122275 # The INTERNAL_DOCS tag determines if documentation
123276 # that is typed after a \internal command is included. If the tag is set
126279
127280 INTERNAL_DOCS = NO
128281
129 # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
130 # doxygen to hide any special comment blocks from generated source code
131 # fragments. Normal C and C++ comments will always remain visible.
132
133 STRIP_CODE_COMMENTS = NO
134
135282 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
136 # file names in lower case letters. If set to YES upper case letters are also
283 # file names in lower-case letters. If set to YES upper-case letters are also
137284 # allowed. This is useful if you have classes or files whose names only differ
138285 # in case and if your file system supports case sensitive file names. Windows
139 # users are adviced to set this option to NO.
286 # and Mac users are advised to set this option to NO.
140287
141288 CASE_SENSE_NAMES = YES
142
143 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
144 # (but less readable) file names. This can be useful is your file systems
145 # doesn't support long names like on DOS, Mac, or CD-ROM.
146
147 SHORT_NAMES = NO
148289
149290 # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
150291 # will show members with their full class and namespace scopes in the
152293
153294 HIDE_SCOPE_NAMES = NO
154295
155 # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
156 # will generate a verbatim copy of the header file for each class for
157 # which an include is specified. Set to NO to disable this.
158
159 VERBATIM_HEADERS = YES
160
161296 # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
162 # will put list of the files that are included by a file in the documentation
297 # will put a list of the files that are included by a file in the documentation
163298 # of that file.
164299
165300 SHOW_INCLUDE_FILES = YES
166
167 # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
168 # will interpret the first line (until the first dot) of a JavaDoc-style
169 # comment as the brief description. If set to NO, the JavaDoc
170 # comments will behave just like the Qt-style comments (thus requiring an
171 # explict @brief command for a brief description.
172
173 JAVADOC_AUTOBRIEF = NO
174
175 # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
176 # member inherits the documentation from any documented member that it
177 # reimplements.
178
179 INHERIT_DOCS = YES
180301
181302 # If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
182303 # is inserted in the documentation for inline members.
190311
191312 SORT_MEMBER_DOCS = YES
192313
193 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
194 # tag is set to YES, then doxygen will reuse the documentation of the first
195 # member in the group (if any) for the other members of the group. By default
196 # all members of a group must be documented explicitly.
197
198 DISTRIBUTE_GROUP_DOC = NO
199
200 # The TAB_SIZE tag can be used to set the number of spaces in a tab.
201 # Doxygen uses this value to replace tabs by spaces in code fragments.
202
203 TAB_SIZE = 2
314 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
315 # brief documentation of file, namespace and class members alphabetically
316 # by member name. If set to NO (the default) the members will appear in
317 # declaration order.
318
319 SORT_BRIEF_DOCS = NO
320
321 # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
322 # sorted by fully-qualified names, including namespaces. If set to
323 # NO (the default), the class list will be sorted only by class name,
324 # not including the namespace part.
325 # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
326 # Note: This option applies only to the class list, not to the
327 # alphabetical list.
328
329 SORT_BY_SCOPE_NAME = NO
204330
205331 # The GENERATE_TODOLIST tag can be used to enable (YES) or
206332 # disable (NO) the todo list. This list is created by putting \todo
220346
221347 GENERATE_BUGLIST = YES
222348
223 # This tag can be used to specify a number of aliases that acts
224 # as commands in the documentation. An alias has the form "name=value".
225 # For example adding "sideeffect=\par Side Effects:\n" will allow you to
226 # put the command \sideeffect (or @sideeffect) in the documentation, which
227 # will result in a user defined paragraph with heading "Side Effects:".
228 # You can put \n's in the value part of an alias to insert newlines.
229
230 ALIASES =
349 # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
350 # disable (NO) the deprecated list. This list is created by putting
351 # \deprecated commands in the documentation.
352
353 GENERATE_DEPRECATEDLIST= YES
231354
232355 # The ENABLED_SECTIONS tag can be used to enable conditional
233356 # documentation sections, marked by \if sectionname ... \endif.
235358 ENABLED_SECTIONS =
236359
237360 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines
238 # the initial value of a variable or define consist of for it to appear in
361 # the initial value of a variable or define consists of for it to appear in
239362 # the documentation. If the initializer consists of more lines than specified
240363 # here it will be hidden. Use a value of 0 to hide initializers completely.
241364 # The appearance of the initializer of individual variables and defines in the
244367
245368 MAX_INITIALIZER_LINES = 30
246369
247 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
248 # only. Doxygen will then generate output that is more tailored for C.
249 # For instance some of the names that are used will be different. The list
250 # of all members will be omitted, etc.
251
252 OPTIMIZE_OUTPUT_FOR_C = NO
253
254370 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated
255371 # at the bottom of the documentation of classes and structs. If set to YES the
256372 # list will mention the files that were used to generate the documentation.
257373
258374 SHOW_USED_FILES = YES
259375
376 # If the sources in your project are distributed over multiple directories
377 # then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
378 # in the documentation. The default is YES.
379
380 SHOW_DIRECTORIES = YES
381
382 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
383 # doxygen should invoke to get the current version for each file (typically from the
384 # version control system). Doxygen will invoke the program by executing (via
385 # popen()) the command , where is the value of
386 # the FILE_VERSION_FILTER tag, and is the name of an input file
387 # provided by doxygen. Whatever the progam writes to standard output
388 # is used as the file version. See the manual for examples.
389
390 FILE_VERSION_FILTER =
391
260392 #---------------------------------------------------------------------------
261393 # configuration options related to warning and progress messages
262394 #---------------------------------------------------------------------------
278410
279411 WARN_IF_UNDOCUMENTED = NO
280412
413 # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
414 # potential errors in the documentation, such as not documenting some
415 # parameters in a documented function, or documenting parameters that
416 # don't exist or using markup commands wrongly.
417
418 WARN_IF_DOC_ERROR = YES
419
420 # This WARN_NO_PARAMDOC option can be abled to get warnings for
421 # functions that are documented, but have no documentation for their parameters
422 # or return value. If set to NO (the default) doxygen will only warn about
423 # wrong or incomplete parameter documentation, but not about the absence of
424 # documentation.
425
426 WARN_NO_PARAMDOC = NO
427
281428 # The WARN_FORMAT tag determines the format of the warning messages that
282429 # doxygen can produce. The string should contain the $file, $line, and $text
283430 # tags, which will be replaced by the file and line number from which the
284 # warning originated and the warning text.
431 # warning originated and the warning text. Optionally the format may contain
432 # $version, which will be replaced by the version of the file (if it could
433 # be obtained via FILE_VERSION_FILTER)
285434
286435 WARN_FORMAT =
287436
295444 # configuration options related to the input files
296445 #---------------------------------------------------------------------------
297446
298 # The INPUT tag can be used to specify the files and/or directories that contain
299 # documented source files. You may enter file names like "myfile.cpp" or
300 # directories like "/usr/src/myproject". Separate the files or directories with
301 # spaces.
302
303 INPUT = @abs_top_srcdir@/include @abs_top_srcdir@/lib @abs_top_srcdir@/docs/doxygen.intro
447 # The INPUT tag can be used to specify the files and/or directories that contain
448 # documented source files. You may enter file names like "myfile.cpp" or
449 # directories like "/usr/src/myproject". Separate the files or directories
450 # with spaces.
451
452 INPUT = @abs_top_srcdir@/include \
453 @abs_top_srcdir@/lib \
454 @abs_top_srcdir@/docs/doxygen.intro
304455
305456 # If the value of the INPUT tag contains directories, you can use the
306457 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
307458 # and *.h) to filter out the source-files in the directories. If left
308459 # blank the following patterns are tested:
309 # *.c *.cc *.cxx *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp
310 # *.h++ *.idl
460 # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx
461 # *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm
311462
312463 FILE_PATTERNS =
313464
317468
318469 RECURSIVE = YES
319470
320 # The EXCLUDE tag can be u sed to specify files and/or directories that should
471 # The EXCLUDE tag can be used to specify files and/or directories that should
321472 # excluded from the INPUT source files. This way you can easily exclude a
322473 # subdirectory from a directory tree whose root is specified with the INPUT tag.
323474
324475 EXCLUDE =
325476
477 # The EXCLUDE_SYMLINKS tag can be used select whether or not files or
478 # directories that are symbolic links (a Unix filesystem feature) are excluded
479 # from the input.
480
481 EXCLUDE_SYMLINKS = NO
482
326483 # If the value of the INPUT tag contains directories, you can use the
327484 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
328 # certain files from those directories.
485 # certain files from those directories. Note that the wildcards are matched
486 # against the file with absolute path, so to exclude all test directories
487 # for example use the pattern */test/*
329488
330489 EXCLUDE_PATTERNS =
331490
360519 # by executing (via popen()) the command , where
361520 # is the value of the INPUT_FILTER tag, and is the name of an
362521 # input file. Doxygen will then use the output that the filter program writes
363 # to standard output.
522 # to standard output. If FILTER_PATTERNS is specified, this tag will be
523 # ignored.
364524
365525 INPUT_FILTER =
526
527 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
528 # basis. Doxygen will compare the file name with each pattern and apply the
529 # filter if there is a match. The filters are a list of the form:
530 # pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
531 # info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER
532 # is applied to all files.
533
534 FILTER_PATTERNS =
366535
367536 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
368537 # INPUT_FILTER) will be used to filter the input files when producing source
369 # files to browse.
538 # files to browse (i.e. when SOURCE_BROWSER is set to YES).
370539
371540 FILTER_SOURCE_FILES = NO
372541
375544 #---------------------------------------------------------------------------
376545
377546 # If the SOURCE_BROWSER tag is set to YES then a list of source files will
378 # be generated. Documented entities will be cross-referenced with these sources.
547 # be generated. Documented entities will be cross-referenced with these sources.
548 # Note: To get rid of all source code in the generated output, make sure also
549 # VERBATIM_HEADERS is set to NO.
379550
380551 SOURCE_BROWSER = YES
381552
383554 # of functions and classes directly in the documentation.
384555
385556 INLINE_SOURCES = NO
557
558 # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
559 # doxygen to hide any special comment blocks from generated source code
560 # fragments. Normal C and C++ comments will always remain visible.
561
562 STRIP_CODE_COMMENTS = NO
386563
387564 # If the REFERENCED_BY_RELATION tag is set to YES (the default)
388565 # then for each documented function all documented
395572 # called/used by that function will be listed.
396573
397574 REFERENCES_RELATION = YES
575
576 # If the USE_HTAGS tag is set to YES then the references to source code
577 # will point to the HTML generated by the htags(1) tool instead of doxygen
578 # built-in source browser. The htags tool is part of GNU's global source
579 # tagging system (see http://www.gnu.org/software/global/global.html). You
580 # will need version 4.8.6 or higher.
581
582 USE_HTAGS = NO
583
584 # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
585 # will generate a verbatim copy of the header file for each class for
586 # which an include is specified. Set to NO to disable this.
587
588 VERBATIM_HEADERS = YES
398589
399590 #---------------------------------------------------------------------------
400591 # configuration options related to the alphabetical class index
434625
435626 HTML_OUTPUT = html
436627
628 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for
629 # each generated HTML page (for example: .htm,.php,.asp). If it is left blank
630 # doxygen will generate files with .html extension.
631
632 HTML_FILE_EXTENSION = .html
633
437634 # The HTML_HEADER tag can be used to specify a personal HTML header for
438635 # each generated HTML page. If it is left blank doxygen will generate a
439636 # standard header.
446643
447644 HTML_FOOTER = @abs_top_srcdir@/docs/doxygen.footer
448645
449 # The HTML_STYLESHEET tag can be used to specify a user defined cascading
646 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading
450647 # style sheet that is used by each HTML page. It can be used to
451648 # fine-tune the look of the HTML output. If the tag is left blank doxygen
452 # will generate a default style sheet
649 # will generate a default style sheet. Note that doxygen will try to copy
650 # the style sheet file to the HTML output directory, so don't put your own
651 # stylesheet in the HTML output directory as well, or it will be erased!
453652
454653 HTML_STYLESHEET = @abs_top_srcdir@/docs/doxygen.css
455654
466665
467666 GENERATE_HTMLHELP = NO
468667
668 # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
669 # be used to specify the file name of the resulting .chm file. You
670 # can add a path in front of the file if the result should not be
671 # written to the html output directory.
672
673 CHM_FILE =
674
675 # If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
676 # be used to specify the location (absolute path including file name) of
677 # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
678 # the HTML help compiler on the generated index.hhp.
679
680 HHC_LOCATION =
681
469682 # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
470683 # controls if a separate .chi index file is generated (YES) or that
471684 # it should be included in the master .chm file (NO).
479692 BINARY_TOC = NO
480693
481694 # The TOC_EXPAND flag can be set to YES to add extra items for group members
482 # to the contents of the Html help documentation and to the tree view.
695 # to the contents of the HTML help documentation and to the tree view.
483696
484697 TOC_EXPAND = NO
485698
497710 # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
498711 # generated containing a tree-like index structure (just like the one that
499712 # is generated for HTML Help). For this to work a browser that supports
500 # JavaScript and frames is required (for instance Mozilla, Netscape 4.0+,
501 # or Internet explorer 4.0+). Note that for large projects the tree generation
502 # can take a very long time. In such cases it is better to disable this feature.
503 # Windows users are probably better off using the HTML help feature.
713 # JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+,
714 # Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are
715 # probably better off using the HTML help feature.
504716
505717 GENERATE_TREEVIEW = NO
506718
524736 # put in front of it. If left blank `latex' will be used as the default path.
525737
526738 LATEX_OUTPUT =
739
740 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
741 # invoked. If left blank `latex' will be used as the default command name.
742
743 LATEX_CMD_NAME = latex
744
745 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
746 # generate index for LaTeX. If left blank `makeindex' will be used as the
747 # default command name.
748
749 MAKEINDEX_CMD_NAME = makeindex
527750
528751 # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
529752 # LaTeX documents. This may be useful for small projects and may help to
569792
570793 LATEX_BATCHMODE = NO
571794
795 # If LATEX_HIDE_INDICES is set to YES then doxygen will not
796 # include the index chapters (such as File Index, Compound Index, etc.)
797 # in the output.
798
799 LATEX_HIDE_INDICES = NO
800
572801 #---------------------------------------------------------------------------
573802 # configuration options related to the RTF output
574803 #---------------------------------------------------------------------------
575804
576805 # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
577 # The RTF output is optimised for Word 97 and may not look very pretty with
806 # The RTF output is optimized for Word 97 and may not look very pretty with
578807 # other RTF readers or editors.
579808
580809 GENERATE_RTF = NO
601830 RTF_HYPERLINKS = NO
602831
603832 # Load stylesheet definitions from file. Syntax is similar to doxygen's
604 # config file, i.e. a series of assigments. You only have to provide
833 # config file, i.e. a series of assignments. You only have to provide
605834 # replacements, missing definitions are set to their default value.
606835
607836 RTF_STYLESHEET_FILE =
645874
646875 # If the GENERATE_XML tag is set to YES Doxygen will
647876 # generate an XML file that captures the structure of
648 # the code including all documentation. Note that this
649 # feature is still experimental and incomplete at the
650 # moment.
877 # the code including all documentation.
651878
652879 GENERATE_XML = NO
880
881 # The XML_OUTPUT tag is used to specify where the XML pages will be put.
882 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
883 # put in front of it. If left blank `xml' will be used as the default path.
884
885 XML_OUTPUT = xml
886
887 # The XML_SCHEMA tag can be used to specify an XML schema,
888 # which can be used by a validating XML parser to check the
889 # syntax of the XML files.
890
891 XML_SCHEMA =
892
893 # The XML_DTD tag can be used to specify an XML DTD,
894 # which can be used by a validating XML parser to check the
895 # syntax of the XML files.
896
897 XML_DTD =
898
899 # If the XML_PROGRAMLISTING tag is set to YES Doxygen will
900 # dump the program listings (including syntax highlighting
901 # and cross-referencing information) to the XML output. Note that
902 # enabling this will significantly increase the size of the XML output.
903
904 XML_PROGRAMLISTING = YES
653905
654906 #---------------------------------------------------------------------------
655907 # configuration options for the AutoGen Definitions output
664916 GENERATE_AUTOGEN_DEF = NO
665917
666918 #---------------------------------------------------------------------------
919 # configuration options related to the Perl module output
920 #---------------------------------------------------------------------------
921
922 # If the GENERATE_PERLMOD tag is set to YES Doxygen will
923 # generate a Perl module file that captures the structure of
924 # the code including all documentation. Note that this
925 # feature is still experimental and incomplete at the
926 # moment.
927
928 GENERATE_PERLMOD = NO
929
930 # If the PERLMOD_LATEX tag is set to YES Doxygen will generate
931 # the necessary Makefile rules, Perl scripts and LaTeX code to be able
932 # to generate PDF and DVI output from the Perl module output.
933
934 PERLMOD_LATEX = NO
935
936 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
937 # nicely formatted so it can be parsed by a human reader. This is useful
938 # if you want to understand what is going on. On the other hand, if this
939 # tag is set to NO the size of the Perl module output will be much smaller
940 # and Perl will parse it just the same.
941
942 PERLMOD_PRETTY = YES
943
944 # The names of the make variables in the generated doxyrules.make file
945 # are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
946 # This is useful so different doxyrules.make files included by the same
947 # Makefile don't overwrite each other's variables.
948
949 PERLMOD_MAKEVAR_PREFIX =
950
951 #---------------------------------------------------------------------------
667952 # Configuration options related to the preprocessor
668953 #---------------------------------------------------------------------------
669954
708993 # are defined before the preprocessor is started (similar to the -D option of
709994 # gcc). The argument of the tag is a list of macros of the form: name
710995 # or name=definition (no spaces). If the definition and the = are
711 # omitted =1 is assumed.
996 # omitted =1 is assumed. To prevent a macro definition from being
997 # undefined via #undef or recursively expanded use the := operator
998 # instead of the = operator.
712999
7131000 PREDEFINED =
7141001
715 # If the MACRO_EXPANSION and EXPAND_PREDEF_ONLY tags are set to YES then
1002 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
7161003 # this tag can be used to specify a list of macro names that should be expanded.
7171004 # The macro definition that is found in the sources will be used.
7181005 # Use the PREDEFINED tag if you want to use a different macro definition.
7211008
7221009 # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
7231010 # doxygen's preprocessor will remove all function-like macros that are alone
724 # on a line and do not end with a semicolon. Such function macros are typically
725 # used for boiler-plate code, and will confuse the parser if not removed.
1011 # on a line, have an all uppercase name, and do not end with a semicolon. Such
1012 # function macros are typically used for boiler-plate code, and will confuse
1013 # the parser if not removed.
7261014
7271015 SKIP_FUNCTION_MACROS = YES
7281016
7291017 #---------------------------------------------------------------------------
730 # Configuration::addtions related to external references
731 #---------------------------------------------------------------------------
732
733 # The TAGFILES tag can be used to specify one or more tagfiles.
1018 # Configuration::additions related to external references
1019 #---------------------------------------------------------------------------
1020
1021 # The TAGFILES option can be used to specify one or more tagfiles.
1022 # Optionally an initial location of the external documentation
1023 # can be added for each tagfile. The format of a tag file without
1024 # this location is as follows:
1025 # TAGFILES = file1 file2 ...
1026 # Adding location for the tag files is done as follows:
1027 # TAGFILES = file1=loc1 "file2 = loc2" ...
1028 # where "loc1" and "loc2" can be relative or absolute paths or
1029 # URLs. If a location is present for each tag, the installdox tool
1030 # does not have to be run to correct the links.
1031 # Note that each tag file must have a unique name
1032 # (where the name does NOT include the path)
1033 # If a tag file is not located in the directory in which doxygen
1034 # is run, you must also specify the path to the tagfile here.
7341035
7351036 TAGFILES =
7361037
7451046
7461047 ALLEXTERNALS = YES
7471048
1049 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1050 # in the modules index. If set to NO, only the current project's groups will
1051 # be listed.
1052
1053 EXTERNAL_GROUPS = YES
1054
7481055 # The PERL_PATH should be the absolute path and name of the perl script
7491056 # interpreter (i.e. the result of `which perl').
7501057
7541061 # Configuration options related to the dot tool
7551062 #---------------------------------------------------------------------------
7561063
757 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will generate a
758 # inheritance diagram (in Html, RTF and LaTeX) for classes with base or super
759 # classes. Setting the tag to NO turns the diagrams off. Note that this option
760 # is superceded by the HAVE_DOT option below. This is only a fallback. It is
761 # recommended to install and use dot, since it yield more powerful graphs.
1064 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1065 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
1066 # or super classes. Setting the tag to NO turns the diagrams off. Note that
1067 # this option is superseded by the HAVE_DOT option below. This is only a
1068 # fallback. It is recommended to install and use dot, since it yields more
1069 # powerful graphs.
7621070
7631071 CLASS_DIAGRAMS = YES
1072
1073 # If set to YES, the inheritance and collaboration graphs will hide
1074 # inheritance and usage relations if the target is undocumented
1075 # or is not a class.
1076
1077 HIDE_UNDOC_RELATIONS = NO
7641078
7651079 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
7661080 # available from the path. This tool is part of Graphviz, a graph visualization
7831097
7841098 COLLABORATION_GRAPH = YES
7851099
1100 # If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
1101 # will generate a graph for groups, showing the direct groups dependencies
1102
1103 GROUP_GRAPHS = YES
1104
1105 # If the UML_LOOK tag is set to YES doxygen will generate inheritance and
1106 # collaboration diagrams in a style similar to the OMG's Unified Modeling
1107 # Language.
1108
1109 UML_LOOK = NO
1110
7861111 # If set to YES, the inheritance and collaboration graphs will show the
7871112 # relations between templates and their instances.
7881113
7891114 TEMPLATE_RELATIONS = YES
790
791 # If set to YES, the inheritance and collaboration graphs will hide
792 # inheritance and usage relations if the target is undocumented
793 # or is not a class.
794
795 HIDE_UNDOC_RELATIONS = NO
7961115
7971116 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
7981117 # tags are set to YES then doxygen will generate a graph for each documented
8081127
8091128 INCLUDED_BY_GRAPH = YES
8101129
1130 # If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will
1131 # generate a call dependency graph for every global function or class method.
1132 # Note that enabling this option will significantly increase the time of a run.
1133 # So in most cases it will be better to enable call graphs for selected
1134 # functions only using the \callgraph command.
1135
1136 CALL_GRAPH = NO
1137
8111138 # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
8121139 # will graphical hierarchy of all classes instead of a textual one.
8131140
8141141 GRAPHICAL_HIERARCHY = YES
8151142
1143 # If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
1144 # then doxygen will show the dependencies a directory has on other directories
1145 # in a graphical way. The dependency relations are determined by the #include
1146 # relations between the files in the directories.
1147
1148 DIRECTORY_GRAPH = YES
1149
1150 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1151 # generated by dot. Possible values are png, jpg, or gif
1152 # If left blank png will be used.
1153
1154 DOT_IMAGE_FORMAT = png
1155
8161156 # The tag DOT_PATH can be used to specify the path where the dot tool can be
817 # found. If left blank, it is assumed the dot tool can be found on the path.
1157 # found. If left blank, it is assumed the dot tool can be found in the path.
8181158
8191159 DOT_PATH = @DOT@
8201160
8401180
8411181 MAX_DOT_GRAPH_HEIGHT = 1024
8421182
1183 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
1184 # graphs generated by dot. A depth value of 3 means that only nodes reachable
1185 # from the root by following a path via at most 3 edges will be shown. Nodes
1186 # that lay further from the root node will be omitted. Note that setting this
1187 # option to 1 or 2 may greatly reduce the computation time needed for large
1188 # code bases. Also note that a graph may be further truncated if the graph's
1189 # image dimensions are not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH
1190 # and MAX_DOT_GRAPH_HEIGHT). If 0 is used for the depth value (the default),
1191 # the graph is not depth-constrained.
1192
1193 MAX_DOT_GRAPH_DEPTH = 0
1194
1195 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
1196 # background. This is disabled by default, which results in a white background.
1197 # Warning: Depending on the platform used, enabling this option may lead to
1198 # badly anti-aliased labels on the edges of a graph (i.e. they become hard to
1199 # read).
1200
1201 DOT_TRANSPARENT = NO
1202
1203 # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
1204 # files in one run (i.e. multiple -o and -T options on the command line). This
1205 # makes dot run faster, but since only newer versions of dot (>1.8.10)
1206 # support this, this feature is disabled by default.
1207
1208 DOT_MULTI_TARGETS = NO
1209
8431210 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
8441211 # generate a legend page explaining the meaning of the various boxes and
8451212 # arrows in the dot generated graphs.
8471214 GENERATE_LEGEND = YES
8481215
8491216 # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
850 # remove the intermedate dot files that are used to generate
1217 # remove the intermediate dot files that are used to generate
8511218 # the various graphs.
8521219
8531220 DOT_CLEANUP = YES
8541221
8551222 #---------------------------------------------------------------------------
856 # Configuration::addtions related to the search engine
1223 # Configuration::additions related to the search engine
8571224 #---------------------------------------------------------------------------
8581225
8591226 # The SEARCHENGINE tag specifies whether or not a search engine should be
None BODY { background: white; color: black; font-family: Verdana,Arial,sans-serif; }
1 H1 { text-align: center; }
2 H2 { text-align: center; }
3 H3 { text-align: center; }
0 BODY,H1,H2,H3,H4,H5,H6,P,CENTER,TD,TH,UL,DL,DIV {
1 font-family: Verdana,Geneva,Arial,Helvetica,sans-serif;
2 }
3 BODY,TD {
4 font-size: 90%;
5 }
6 H1 {
7 text-align: center;
8 font-size: 140%;
9 font-weight: bold;
10 }
11 H2 {
12 font-size: 120%;
13 font-style: italic;
14 }
15 H3 {
16 font-size: 100%;
17 }
418 CAPTION { font-weight: bold }
5 A.qindex {}
6 A.qindexRef {}
19 DIV.qindex {
20 width: 100%;
21 background-color: #eeeeff;
22 border: 1px solid #b0b0b0;
23 text-align: center;
24 margin: 2px;
25 padding: 2px;
26 line-height: 140%;
27 }
28 DIV.nav {
29 width: 100%;
30 background-color: #eeeeff;
31 border: 1px solid #b0b0b0;
32 text-align: center;
33 margin: 2px;
34 padding: 2px;
35 line-height: 140%;
36 }
37 DIV.navtab {
38 background-color: #eeeeff;
39 border: 1px solid #b0b0b0;
40 text-align: center;
41 margin: 2px;
42 margin-right: 15px;
43 padding: 2px;
44 }
45 TD.navtab {
46 font-size: 70%;
47 }
48 A.qindex {
49 text-decoration: none;
50 font-weight: bold;
51 color: #1A419D;
52 }
53 A.qindex:visited {
54 text-decoration: none;
55 font-weight: bold;
56 color: #1A419D
57 }
58 A.qindex:hover {
59 text-decoration: none;
60 background-color: #ddddff;
61 }
62 A.qindexHL {
63 text-decoration: none;
64 font-weight: bold;
65 background-color: #6666cc;
66 color: #ffffff;
67 border: 1px double #9295C2;
68 }
69 A.qindexHL:hover {
70 text-decoration: none;
71 background-color: #6666cc;
72 color: #ffffff;
73 }
74 A.qindexHL:visited {
75 text-decoration: none; background-color: #6666cc; color: #ffffff }
776 A.el { text-decoration: none; font-weight: bold }
877 A.elRef { font-weight: bold }
9 A.code { text-decoration: none; font-weight: normal; color: #4444ee }
10 A.codeRef { font-weight: normal; color: #4444ee }
11 A:link {
12 cursor: pointer;
13 text-decoration: none;
14 font-weight: bolder;
15 }
16 A:visited {
17 cursor: pointer;
18 text-decoration: underline;
19 font-weight: bolder;
20 }
21 A:hover {
22 cursor: pointer;
23 text-decoration: underline;
24 font-weight: bolder;
25 }
26 A:active {
27 cursor: pointer;
28 text-decoration: underline;
29 font-weight: bolder;
30 font-style: italic;
31 }
78 A.code:link { text-decoration: none; font-weight: normal; color: #0000FF}
79 A.code:visited { text-decoration: none; font-weight: normal; color: #0000FF}
80 A.codeRef:link { font-weight: normal; color: #0000FF}
81 A.codeRef:visited { font-weight: normal; color: #0000FF}
82 A:hover { text-decoration: none; background-color: #f2f2ff }
3283 DL.el { margin-left: -1cm }
33 DIV.fragment { width: 100%; border: none; background-color: #eeeeee }
84 .fragment {
85 font-family: Fixed, monospace;
86 font-size: 95%;
87 }
88 PRE.fragment {
89 border: 1px solid #CCCCCC;
90 background-color: #f5f5f5;
91 margin-top: 4px;
92 margin-bottom: 4px;
93 margin-left: 2px;
94 margin-right: 8px;
95 padding-left: 6px;
96 padding-right: 6px;
97 padding-top: 4px;
98 padding-bottom: 4px;
99 }
34100 DIV.ah { background-color: black; font-weight: bold; color: #ffffff; margin-bottom: 3px; margin-top: 3px }
35 TD.md { background-color: #f2f2ff; font-weight: bold; }
36 TD.mdname1 { background-color: #f2f2ff; font-weight: bold; color: #602020; }
37 TD.mdname { background-color: #f2f2ff; font-weight: bold; color: #602020; width: 600px; }
38 DIV.groupHeader { margin-left: 16px; margin-top: 12px; margin-bottom: 6px; font-weight: bold }
39 DIV.groupText { margin-left: 16px; font-style: italic; font-size: smaller }
40 TD.indexkey {
41 background-color: #eeeeff;
42 font-weight: bold;
43 padding-right : 10px;
44 padding-top : 2px;
45 padding-left : 10px;
46 padding-bottom : 2px;
47 margin-left : 0px;
48 margin-right : 0px;
49 margin-top : 2px;
50 margin-bottom : 2px
51 }
52 TD.indexvalue {
53 background-color: #eeeeff;
54 font-style: italic;
55 padding-right : 10px;
56 padding-top : 2px;
57 padding-left : 10px;
58 padding-bottom : 2px;
59 margin-left : 0px;
60 margin-right : 0px;
61 margin-top : 2px;
62 margin-bottom : 2px
63 }
64 span.keyword { color: #008000 }
65 span.keywordtype { color: #604020 }
66 span.keywordflow { color: #e08000 }
67 span.comment { color: #800000 }
68 span.preprocessor { color: #806020 }
69 span.stringliteral { color: #002080 }
70 span.charliteral { color: #008080 }
101 TD.md { background-color: #F4F4FB; font-weight: bold; }
102 TD.mdPrefix {
103 background-color: #F4F4FB;
104 color: #606060;
105 font-size: 80%;
106 }
107 TD.mdname1 { background-color: #F4F4FB; font-weight: bold; color: #602020; }
108 TD.mdname { background-color: #F4F4FB; font-weight: bold; color: #602020; width: 600px; }
109 DIV.groupHeader {
110 margin-left: 16px;
111 margin-top: 12px;
112 margin-bottom: 6px;
113 font-weight: bold;
114 }
115 DIV.groupText { margin-left: 16px; font-style: italic; font-size: 90% }
116 BODY {
117 background: white;
118 color: black;
119 margin-right: 20px;
120 margin-left: 20px;
121 }
122 TD.indexkey {
123 background-color: #eeeeff;
124 font-weight: bold;
125 padding-right : 10px;
126 padding-top : 2px;
127 padding-left : 10px;
128 padding-bottom : 2px;
129 margin-left : 0px;
130 margin-right : 0px;
131 margin-top : 2px;
132 margin-bottom : 2px;
133 border: 1px solid #CCCCCC;
134 }
135 TD.indexvalue {
136 background-color: #eeeeff;
137 font-style: italic;
138 padding-right : 10px;
139 padding-top : 2px;
140 padding-left : 10px;
141 padding-bottom : 2px;
142 margin-left : 0px;
143 margin-right : 0px;
144 margin-top : 2px;
145 margin-bottom : 2px;
146 border: 1px solid #CCCCCC;
147 }
148 TR.memlist {
149 background-color: #f0f0f0;
150 }
151 P.formulaDsp { text-align: center; }
152 IMG.formulaDsp { }
153 IMG.formulaInl { vertical-align: middle; }
154 SPAN.keyword { color: #008000 }
155 SPAN.keywordtype { color: #604020 }
156 SPAN.keywordflow { color: #e08000 }
157 SPAN.comment { color: #800000 }
158 SPAN.preprocessor { color: #806020 }
159 SPAN.stringliteral { color: #002080 }
160 SPAN.charliteral { color: #008080 }
161 .mdTable {
162 border: 1px solid #868686;
163 background-color: #F4F4FB;
164 }
165 .mdRow {
166 padding: 8px 10px;
167 }
168 .mdescLeft {
169 padding: 0px 8px 4px 8px;
170 font-size: 80%;
171 font-style: italic;
172 background-color: #FAFAFA;
173 border-top: 1px none #E0E0E0;
174 border-right: 1px none #E0E0E0;
175 border-bottom: 1px none #E0E0E0;
176 border-left: 1px none #E0E0E0;
177 margin: 0px;
178 }
179 .mdescRight {
180 padding: 0px 8px 4px 8px;
181 font-size: 80%;
182 font-style: italic;
183 background-color: #FAFAFA;
184 border-top: 1px none #E0E0E0;
185 border-right: 1px none #E0E0E0;
186 border-bottom: 1px none #E0E0E0;
187 border-left: 1px none #E0E0E0;
188 margin: 0px;
189 }
190 .memItemLeft {
191 padding: 1px 0px 0px 8px;
192 margin: 4px;
193 border-top-width: 1px;
194 border-right-width: 1px;
195 border-bottom-width: 1px;
196 border-left-width: 1px;
197 border-top-color: #E0E0E0;
198 border-right-color: #E0E0E0;
199 border-bottom-color: #E0E0E0;
200 border-left-color: #E0E0E0;
201 border-top-style: solid;
202 border-right-style: none;
203 border-bottom-style: none;
204 border-left-style: none;
205 background-color: #FAFAFA;
206 font-size: 80%;
207 }
208 .memItemRight {
209 padding: 1px 8px 0px 8px;
210 margin: 4px;
211 border-top-width: 1px;
212 border-right-width: 1px;
213 border-bottom-width: 1px;
214 border-left-width: 1px;
215 border-top-color: #E0E0E0;
216 border-right-color: #E0E0E0;
217 border-bottom-color: #E0E0E0;
218 border-left-color: #E0E0E0;
219 border-top-style: solid;
220 border-right-style: none;
221 border-bottom-style: none;
222 border-left-style: none;
223 background-color: #FAFAFA;
224 font-size: 80%;
225 }
226 .memTemplItemLeft {
227 padding: 1px 0px 0px 8px;
228 margin: 4px;
229 border-top-width: 1px;
230 border-right-width: 1px;
231 border-bottom-width: 1px;
232 border-left-width: 1px;
233 border-top-color: #E0E0E0;
234 border-right-color: #E0E0E0;
235 border-bottom-color: #E0E0E0;
236 border-left-color: #E0E0E0;
237 border-top-style: none;
238 border-right-style: none;
239 border-bottom-style: none;
240 border-left-style: none;
241 background-color: #FAFAFA;
242 font-size: 80%;
243 }
244 .memTemplItemRight {
245 padding: 1px 8px 0px 8px;
246 margin: 4px;
247 border-top-width: 1px;
248 border-right-width: 1px;
249 border-bottom-width: 1px;
250 border-left-width: 1px;
251 border-top-color: #E0E0E0;
252 border-right-color: #E0E0E0;
253 border-bottom-color: #E0E0E0;
254 border-left-color: #E0E0E0;
255 border-top-style: none;
256 border-right-style: none;
257 border-bottom-style: none;
258 border-left-style: none;
259 background-color: #FAFAFA;
260 font-size: 80%;
261 }
262 .memTemplParams {
263 padding: 1px 0px 0px 8px;
264 margin: 4px;
265 border-top-width: 1px;
266 border-right-width: 1px;
267 border-bottom-width: 1px;
268 border-left-width: 1px;
269 border-top-color: #E0E0E0;
270 border-right-color: #E0E0E0;
271 border-bottom-color: #E0E0E0;
272 border-left-color: #E0E0E0;
273 border-top-style: solid;
274 border-right-style: none;
275 border-bottom-style: none;
276 border-left-style: none;
277 color: #606060;
278 background-color: #FAFAFA;
279 font-size: 80%;
280 }
281 .search { color: #003399;
282 font-weight: bold;
283 }
284 FORM.search {
285 margin-bottom: 0px;
286 margin-top: 0px;
287 }
288 INPUT.search { font-size: 75%;
289 color: #000080;
290 font-weight: normal;
291 background-color: #eeeeff;
292 }
293 TD.tiny { font-size: 75%;
294 }
295 a {
296 color: #252E78;
297 }
298 a:visited {
299 color: #3D2185;
300 }
301 .dirtab { padding: 4px;
302 border-collapse: collapse;
303 border: 1px solid #b0b0b0;
304 }
305 TH.dirtab { background: #eeeeff;
306 font-weight: bold;
307 }
308 HR { height: 1px;
309 border: none;
310 border-top: 1px solid black;
311 }
312
313 /*
314 * LLVM Modifications.
315 * Note: Everything above here is generated with "doxygen -w htlm" command. See
316 * "doxygen --help" for details. What follows are CSS overrides for LLVM
317 * specific formatting. We want to keep the above so it can be replaced with
318 * subsequent doxygen upgrades.
319 */
71320
72321 .footer {
73322 font-size: 80%;
87336 padding-top: 1px;
88337 padding-bottom: 2px
89338 }
339 A:link {
340 cursor: pointer;
341 text-decoration: none;
342 font-weight: bolder;
343 }
344 A:visited {
345 cursor: pointer;
346 text-decoration: underline;
347 font-weight: bolder;
348 }
349 A:hover {
350 cursor: pointer;
351 text-decoration: underline;
352 font-weight: bolder;
353 }
354 A:active {
355 cursor: pointer;
356 text-decoration: underline;
357 font-weight: bolder;
358 font-style: italic;
359 }
360 H1 {
361 text-align: center;
362 font-size: 140%;
363 font-weight: bold;
364 }
365 H2 {
366 font-size: 120%;
367 font-style: italic;
368 }
369 H3 {
370 font-size: 100%;
371 }
372 A.qindex {}
373 A.qindexRef {}
374 A.el { text-decoration: none; font-weight: bold }
375 A.elRef { font-weight: bold }
376 A.code { text-decoration: none; font-weight: normal; color: #4444ee }
377 A.codeRef { font-weight: normal; color: #4444ee }
0
1
21
3 Generated on $datetime for LLVM by
4 doxygen $doxygenversion
5 Copyright © 2003,2004 University of Illinois at Urbana-Champaign. All
6 Rights Reserved.

7
2 Generated on $datetime for $projectname by
3 Doxygen
4 align="middle" border="0"/>$doxygenversion
5 Copyright © 2003,2004,2005,2006 University of Illinois at Urbana-Champaign.
6 All Rights Reserved.

87
98