| @@ -1,23 +1,24 | |||
|
|
1 | 1 | # use glob syntax. |
|
|
2 | 2 | syntax: glob |
|
|
3 | 3 | |
|
|
4 | 4 | *.*~ |
|
|
5 | 5 | *~ |
|
|
6 | 6 | *.o |
|
|
7 | 7 | *.a |
|
|
8 | 8 | *.hex |
|
|
9 | 9 | *.bin |
|
|
10 | 10 | *.d |
|
|
11 | 11 | *.dump |
|
|
12 | 12 | *.map |
|
|
13 | 13 | *.user |
|
|
14 | 14 | *.user.* |
|
|
15 | 15 | *.orig |
|
|
16 | 16 | Makefile.* |
|
|
17 | 17 | *.Makefile.* |
|
|
18 | 18 | *.aux |
|
|
19 | 19 | *.ps |
|
|
20 | 20 | *.out |
|
|
21 | 21 | *.prl |
|
|
22 | 22 | *.dfu |
|
|
23 | ||
|
|
23 | mkspecs/default/qmake.conf | |
|
|
24 | mkspecs/default/qplatformdefs.h | |
| @@ -1,1902 +1,1906 | |||
|
|
1 | 1 | # Doxyfile 1.8.3.1 |
|
|
2 | 2 | |
|
|
3 | 3 | # This file describes the settings to be used by the documentation system |
|
|
4 | 4 | # doxygen (www.doxygen.org) for a project |
|
|
5 | 5 | # |
|
|
6 | 6 | # All text after a hash (#) is considered a comment and will be ignored |
|
|
7 | 7 | # The format is: |
|
|
8 | 8 | # TAG = value [value, ...] |
|
|
9 | 9 | # For lists items can also be appended using: |
|
|
10 | 10 | # TAG += value [value, ...] |
|
|
11 | 11 | # Values that contain spaces should be placed between quotes (" ") |
|
|
12 | 12 | |
|
|
13 | 13 | #--------------------------------------------------------------------------- |
|
|
14 | 14 | # Project related configuration options |
|
|
15 | 15 | #--------------------------------------------------------------------------- |
|
|
16 | 16 | |
|
|
17 | 17 | # This tag specifies the encoding used for all characters in the config file |
|
|
18 | 18 | # that follow. The default is UTF-8 which is also the encoding used for all |
|
|
19 | 19 | # text before the first occurrence of this tag. Doxygen uses libiconv (or the |
|
|
20 | 20 | # iconv built into libc) for the transcoding. See |
|
|
21 | 21 | # http://www.gnu.org/software/libiconv for the list of possible encodings. |
|
|
22 | 22 | |
|
|
23 | 23 | DOXYFILE_ENCODING = UTF-8 |
|
|
24 | 24 | |
|
|
25 | 25 | # The PROJECT_NAME tag is a single word (or sequence of words) that should |
|
|
26 | 26 | # identify the project. Note that if you do not use Doxywizard you need |
|
|
27 | 27 | # to put quotes around the project name if it contains spaces. |
|
|
28 | 28 | |
|
|
29 | 29 | PROJECT_NAME = libuc2 |
|
|
30 | 30 | |
|
|
31 | 31 | # The PROJECT_NUMBER tag can be used to enter a project or revision number. |
|
|
32 | 32 | # This could be handy for archiving the generated documentation or |
|
|
33 | 33 | # if some version control system is used. |
|
|
34 | 34 | |
|
|
35 | 35 | PROJECT_NUMBER = |
|
|
36 | 36 | |
|
|
37 | 37 | # Using the PROJECT_BRIEF tag one can provide an optional one line description |
|
|
38 | 38 | # for a project that appears at the top of each page and should give viewer |
|
|
39 | 39 | # a quick idea about the purpose of the project. Keep the description short. |
|
|
40 | 40 | |
|
|
41 | 41 | PROJECT_BRIEF = |
|
|
42 | 42 | |
|
|
43 | 43 | # With the PROJECT_LOGO tag one can specify an logo or icon that is |
|
|
44 | 44 | # included in the documentation. The maximum height of the logo should not |
|
|
45 | 45 | # exceed 55 pixels and the maximum width should not exceed 200 pixels. |
|
|
46 | 46 | # Doxygen will copy the logo to the output directory. |
|
|
47 | 47 | |
|
|
48 | 48 | PROJECT_LOGO = |
|
|
49 | 49 | |
|
|
50 | 50 | # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) |
|
|
51 | 51 | # base path where the generated documentation will be put. |
|
|
52 | 52 | # If a relative path is entered, it will be relative to the location |
|
|
53 | 53 | # where doxygen was started. If left blank the current directory will be used. |
|
|
54 | 54 | |
|
|
55 | 55 | OUTPUT_DIRECTORY = doc/doxygen |
|
|
56 | 56 | |
|
|
57 | 57 | # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create |
|
|
58 | 58 | # 4096 sub-directories (in 2 levels) under the output directory of each output |
|
|
59 | 59 | # format and will distribute the generated files over these directories. |
|
|
60 | 60 | # Enabling this option can be useful when feeding doxygen a huge amount of |
|
|
61 | 61 | # source files, where putting all generated files in the same directory would |
|
|
62 | 62 | # otherwise cause performance problems for the file system. |
|
|
63 | 63 | |
|
|
64 | 64 | CREATE_SUBDIRS = NO |
|
|
65 | 65 | |
|
|
66 | 66 | # The OUTPUT_LANGUAGE tag is used to specify the language in which all |
|
|
67 | 67 | # documentation generated by doxygen is written. Doxygen will use this |
|
|
68 | 68 | # information to generate all constant output in the proper language. |
|
|
69 | 69 | # The default language is English, other supported languages are: |
|
|
70 | 70 | # Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, |
|
|
71 | 71 | # Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German, |
|
|
72 | 72 | # Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English |
|
|
73 | 73 | # messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, |
|
|
74 | 74 | # Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak, |
|
|
75 | 75 | # Slovene, Spanish, Swedish, Ukrainian, and Vietnamese. |
|
|
76 | 76 | |
|
|
77 | 77 | OUTPUT_LANGUAGE = English |
|
|
78 | 78 | |
|
|
79 | 79 | # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will |
|
|
80 | 80 | # include brief member descriptions after the members that are listed in |
|
|
81 | 81 | # the file and class documentation (similar to JavaDoc). |
|
|
82 | 82 | # Set to NO to disable this. |
|
|
83 | 83 | |
|
|
84 | 84 | BRIEF_MEMBER_DESC = YES |
|
|
85 | 85 | |
|
|
86 | 86 | # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend |
|
|
87 | 87 | # the brief description of a member or function before the detailed description. |
|
|
88 | 88 | # Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the |
|
|
89 | 89 | # brief descriptions will be completely suppressed. |
|
|
90 | 90 | |
|
|
91 | 91 | REPEAT_BRIEF = YES |
|
|
92 | 92 | |
|
|
93 | 93 | # This tag implements a quasi-intelligent brief description abbreviator |
|
|
94 | 94 | # that is used to form the text in various listings. Each string |
|
|
95 | 95 | # in this list, if found as the leading text of the brief description, will be |
|
|
96 | 96 | # stripped from the text and the result after processing the whole list, is |
|
|
97 | 97 | # used as the annotated text. Otherwise, the brief description is used as-is. |
|
|
98 | 98 | # If left blank, the following values are used ("$name" is automatically |
|
|
99 | 99 | # replaced with the name of the entity): "The $name class" "The $name widget" |
|
|
100 | 100 | # "The $name file" "is" "provides" "specifies" "contains" |
|
|
101 | 101 | # "represents" "a" "an" "the" |
|
|
102 | 102 | |
|
|
103 | 103 | ABBREVIATE_BRIEF = "The $name class" \ |
|
|
104 | 104 | "The $name widget" \ |
|
|
105 | 105 | "The $name file" \ |
|
|
106 | 106 | is \ |
|
|
107 | 107 | provides \ |
|
|
108 | 108 | specifies \ |
|
|
109 | 109 | contains \ |
|
|
110 | 110 | represents \ |
|
|
111 | 111 | a \ |
|
|
112 | 112 | an \ |
|
|
113 | 113 | the |
|
|
114 | 114 | |
|
|
115 | 115 | # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then |
|
|
116 | 116 | # Doxygen will generate a detailed section even if there is only a brief |
|
|
117 | 117 | # description. |
|
|
118 | 118 | |
|
|
119 | 119 | ALWAYS_DETAILED_SEC = NO |
|
|
120 | 120 | |
|
|
121 | 121 | # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all |
|
|
122 | 122 | # inherited members of a class in the documentation of that class as if those |
|
|
123 | 123 | # members were ordinary class members. Constructors, destructors and assignment |
|
|
124 | 124 | # operators of the base classes will not be shown. |
|
|
125 | 125 | |
|
|
126 | 126 | INLINE_INHERITED_MEMB = NO |
|
|
127 | 127 | |
|
|
128 | 128 | # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full |
|
|
129 | 129 | # path before files name in the file list and in the header files. If set |
|
|
130 | 130 | # to NO the shortest path that makes the file name unique will be used. |
|
|
131 | 131 | |
|
|
132 | 132 | FULL_PATH_NAMES = YES |
|
|
133 | 133 | |
|
|
134 | 134 | # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag |
|
|
135 | 135 | # can be used to strip a user-defined part of the path. Stripping is |
|
|
136 | 136 | # only done if one of the specified strings matches the left-hand part of |
|
|
137 | 137 | # the path. The tag can be used to show relative paths in the file list. |
|
|
138 | 138 | # If left blank the directory from which doxygen is run is used as the |
|
|
139 | 139 | # path to strip. Note that you specify absolute paths here, but also |
|
|
140 | 140 | # relative paths, which will be relative from the directory where doxygen is |
|
|
141 | 141 | # started. |
|
|
142 | 142 | |
|
|
143 | 143 | STRIP_FROM_PATH = |
|
|
144 | 144 | |
|
|
145 | 145 | # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of |
|
|
146 | 146 | # the path mentioned in the documentation of a class, which tells |
|
|
147 | 147 | # the reader which header file to include in order to use a class. |
|
|
148 | 148 | # If left blank only the name of the header file containing the class |
|
|
149 | 149 | # definition is used. Otherwise one should specify the include paths that |
|
|
150 | 150 | # are normally passed to the compiler using the -I flag. |
|
|
151 | 151 | |
|
|
152 | 152 | STRIP_FROM_INC_PATH = |
|
|
153 | 153 | |
|
|
154 | 154 | # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter |
|
|
155 | 155 | # (but less readable) file names. This can be useful if your file system |
|
|
156 | 156 | # doesn't support long names like on DOS, Mac, or CD-ROM. |
|
|
157 | 157 | |
|
|
158 | 158 | SHORT_NAMES = NO |
|
|
159 | 159 | |
|
|
160 | 160 | # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen |
|
|
161 | 161 | # will interpret the first line (until the first dot) of a JavaDoc-style |
|
|
162 | 162 | # comment as the brief description. If set to NO, the JavaDoc |
|
|
163 | 163 | # comments will behave just like regular Qt-style comments |
|
|
164 | 164 | # (thus requiring an explicit @brief command for a brief description.) |
|
|
165 | 165 | |
|
|
166 | 166 | JAVADOC_AUTOBRIEF = NO |
|
|
167 | 167 | |
|
|
168 | 168 | # If the QT_AUTOBRIEF tag is set to YES then Doxygen will |
|
|
169 | 169 | # interpret the first line (until the first dot) of a Qt-style |
|
|
170 | 170 | # comment as the brief description. If set to NO, the comments |
|
|
171 | 171 | # will behave just like regular Qt-style comments (thus requiring |
|
|
172 | 172 | # an explicit \brief command for a brief description.) |
|
|
173 | 173 | |
|
|
174 |
QT_AUTOBRIEF = |
|
|
|
174 | QT_AUTOBRIEF = YES | |
|
|
175 | 175 | |
|
|
176 | 176 | # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen |
|
|
177 | 177 | # treat a multi-line C++ special comment block (i.e. a block of //! or /// |
|
|
178 | 178 | # comments) as a brief description. This used to be the default behaviour. |
|
|
179 | 179 | # The new default is to treat a multi-line C++ comment block as a detailed |
|
|
180 | 180 | # description. Set this tag to YES if you prefer the old behaviour instead. |
|
|
181 | 181 | |
|
|
182 | 182 | MULTILINE_CPP_IS_BRIEF = NO |
|
|
183 | 183 | |
|
|
184 | 184 | # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented |
|
|
185 | 185 | # member inherits the documentation from any documented member that it |
|
|
186 | 186 | # re-implements. |
|
|
187 | 187 | |
|
|
188 | 188 | INHERIT_DOCS = YES |
|
|
189 | 189 | |
|
|
190 | 190 | # If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce |
|
|
191 | 191 | # a new page for each member. If set to NO, the documentation of a member will |
|
|
192 | 192 | # be part of the file/class/namespace that contains it. |
|
|
193 | 193 | |
|
|
194 | 194 | SEPARATE_MEMBER_PAGES = NO |
|
|
195 | 195 | |
|
|
196 | 196 | # The TAB_SIZE tag can be used to set the number of spaces in a tab. |
|
|
197 | 197 | # Doxygen uses this value to replace tabs by spaces in code fragments. |
|
|
198 | 198 | |
|
|
199 | 199 | TAB_SIZE = 4 |
|
|
200 | 200 | |
|
|
201 | 201 | # This tag can be used to specify a number of aliases that acts |
|
|
202 | 202 | # as commands in the documentation. An alias has the form "name=value". |
|
|
203 | 203 | # For example adding "sideeffect=\par Side Effects:\n" will allow you to |
|
|
204 | 204 | # put the command \sideeffect (or @sideeffect) in the documentation, which |
|
|
205 | 205 | # will result in a user-defined paragraph with heading "Side Effects:". |
|
|
206 | 206 | # You can put \n's in the value part of an alias to insert newlines. |
|
|
207 | 207 | |
|
|
208 | 208 | ALIASES = |
|
|
209 | 209 | |
|
|
210 | 210 | # This tag can be used to specify a number of word-keyword mappings (TCL only). |
|
|
211 | 211 | # A mapping has the form "name=value". For example adding |
|
|
212 | 212 | # "class=itcl::class" will allow you to use the command class in the |
|
|
213 | 213 | # itcl::class meaning. |
|
|
214 | 214 | |
|
|
215 | 215 | TCL_SUBST = |
|
|
216 | 216 | |
|
|
217 | 217 | # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C |
|
|
218 | 218 | # sources only. Doxygen will then generate output that is more tailored for C. |
|
|
219 | 219 | # For instance, some of the names that are used will be different. The list |
|
|
220 | 220 | # of all members will be omitted, etc. |
|
|
221 | 221 | |
|
|
222 | 222 | OPTIMIZE_OUTPUT_FOR_C = YES |
|
|
223 | 223 | |
|
|
224 | 224 | # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java |
|
|
225 | 225 | # sources only. Doxygen will then generate output that is more tailored for |
|
|
226 | 226 | # Java. For instance, namespaces will be presented as packages, qualified |
|
|
227 | 227 | # scopes will look different, etc. |
|
|
228 | 228 | |
|
|
229 | 229 | OPTIMIZE_OUTPUT_JAVA = NO |
|
|
230 | 230 | |
|
|
231 | 231 | # Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran |
|
|
232 | 232 | # sources only. Doxygen will then generate output that is more tailored for |
|
|
233 | 233 | # Fortran. |
|
|
234 | 234 | |
|
|
235 | 235 | OPTIMIZE_FOR_FORTRAN = NO |
|
|
236 | 236 | |
|
|
237 | 237 | # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL |
|
|
238 | 238 | # sources. Doxygen will then generate output that is tailored for |
|
|
239 | 239 | # VHDL. |
|
|
240 | 240 | |
|
|
241 | 241 | OPTIMIZE_OUTPUT_VHDL = NO |
|
|
242 | 242 | |
|
|
243 | 243 | # Doxygen selects the parser to use depending on the extension of the files it |
|
|
244 | 244 | # parses. With this tag you can assign which parser to use for a given |
|
|
245 | 245 | # extension. Doxygen has a built-in mapping, but you can override or extend it |
|
|
246 | 246 | # using this tag. The format is ext=language, where ext is a file extension, |
|
|
247 | 247 | # and language is one of the parsers supported by doxygen: IDL, Java, |
|
|
248 | 248 | # Javascript, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, |
|
|
249 | 249 | # C++. For instance to make doxygen treat .inc files as Fortran files (default |
|
|
250 | 250 | # is PHP), and .f files as C (default is Fortran), use: inc=Fortran f=C. Note |
|
|
251 | 251 | # that for custom extensions you also need to set FILE_PATTERNS otherwise the |
|
|
252 | 252 | # files are not read by doxygen. |
|
|
253 | 253 | |
|
|
254 | 254 | EXTENSION_MAPPING = |
|
|
255 | 255 | |
|
|
256 | 256 | # If MARKDOWN_SUPPORT is enabled (the default) then doxygen pre-processes all |
|
|
257 | 257 | # comments according to the Markdown format, which allows for more readable |
|
|
258 | 258 | # documentation. See http://daringfireball.net/projects/markdown/ for details. |
|
|
259 | 259 | # The output of markdown processing is further processed by doxygen, so you |
|
|
260 | 260 | # can mix doxygen, HTML, and XML commands with Markdown formatting. |
|
|
261 | 261 | # Disable only in case of backward compatibilities issues. |
|
|
262 | 262 | |
|
|
263 | 263 | MARKDOWN_SUPPORT = YES |
|
|
264 | 264 | |
|
|
265 | 265 | # When enabled doxygen tries to link words that correspond to documented classes, |
|
|
266 | 266 | # or namespaces to their corresponding documentation. Such a link can be |
|
|
267 | 267 | # prevented in individual cases by by putting a % sign in front of the word or |
|
|
268 | 268 | # globally by setting AUTOLINK_SUPPORT to NO. |
|
|
269 | 269 | |
|
|
270 | 270 | AUTOLINK_SUPPORT = YES |
|
|
271 | 271 | |
|
|
272 | 272 | # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want |
|
|
273 | 273 | # to include (a tag file for) the STL sources as input, then you should |
|
|
274 | 274 | # set this tag to YES in order to let doxygen match functions declarations and |
|
|
275 | 275 | # definitions whose arguments contain STL classes (e.g. func(std::string); v.s. |
|
|
276 | 276 | # func(std::string) {}). This also makes the inheritance and collaboration |
|
|
277 | 277 | # diagrams that involve STL classes more complete and accurate. |
|
|
278 | 278 | |
|
|
279 | 279 | BUILTIN_STL_SUPPORT = NO |
|
|
280 | 280 | |
|
|
281 | 281 | # If you use Microsoft's C++/CLI language, you should set this option to YES to |
|
|
282 | 282 | # enable parsing support. |
|
|
283 | 283 | |
|
|
284 | 284 | CPP_CLI_SUPPORT = NO |
|
|
285 | 285 | |
|
|
286 | 286 | # Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. |
|
|
287 | 287 | # Doxygen will parse them like normal C++ but will assume all classes use public |
|
|
288 | 288 | # instead of private inheritance when no explicit protection keyword is present. |
|
|
289 | 289 | |
|
|
290 | 290 | SIP_SUPPORT = NO |
|
|
291 | 291 | |
|
|
292 | 292 | # For Microsoft's IDL there are propget and propput attributes to indicate |
|
|
293 | 293 | # getter and setter methods for a property. Setting this option to YES (the |
|
|
294 | 294 | # default) will make doxygen replace the get and set methods by a property in |
|
|
295 | 295 | # the documentation. This will only work if the methods are indeed getting or |
|
|
296 | 296 | # setting a simple type. If this is not the case, or you want to show the |
|
|
297 | 297 | # methods anyway, you should set this option to NO. |
|
|
298 | 298 | |
|
|
299 | 299 | IDL_PROPERTY_SUPPORT = YES |
|
|
300 | 300 | |
|
|
301 | 301 | # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC |
|
|
302 | 302 | # tag is set to YES, then doxygen will reuse the documentation of the first |
|
|
303 | 303 | # member in the group (if any) for the other members of the group. By default |
|
|
304 | 304 | # all members of a group must be documented explicitly. |
|
|
305 | 305 | |
|
|
306 | 306 | DISTRIBUTE_GROUP_DOC = NO |
|
|
307 | 307 | |
|
|
308 | 308 | # Set the SUBGROUPING tag to YES (the default) to allow class member groups of |
|
|
309 | 309 | # the same type (for instance a group of public functions) to be put as a |
|
|
310 | 310 | # subgroup of that type (e.g. under the Public Functions section). Set it to |
|
|
311 | 311 | # NO to prevent subgrouping. Alternatively, this can be done per class using |
|
|
312 | 312 | # the \nosubgrouping command. |
|
|
313 | 313 | |
|
|
314 | 314 | SUBGROUPING = YES |
|
|
315 | 315 | |
|
|
316 | 316 | # When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and |
|
|
317 | 317 | # unions are shown inside the group in which they are included (e.g. using |
|
|
318 | 318 | # @ingroup) instead of on a separate page (for HTML and Man pages) or |
|
|
319 | 319 | # section (for LaTeX and RTF). |
|
|
320 | 320 | |
|
|
321 | 321 | INLINE_GROUPED_CLASSES = NO |
|
|
322 | 322 | |
|
|
323 | 323 | # When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and |
|
|
324 | 324 | # unions with only public data fields will be shown inline in the documentation |
|
|
325 | 325 | # of the scope in which they are defined (i.e. file, namespace, or group |
|
|
326 | 326 | # documentation), provided this scope is documented. If set to NO (the default), |
|
|
327 | 327 | # structs, classes, and unions are shown on a separate page (for HTML and Man |
|
|
328 | 328 | # pages) or section (for LaTeX and RTF). |
|
|
329 | 329 | |
|
|
330 | 330 | INLINE_SIMPLE_STRUCTS = NO |
|
|
331 | 331 | |
|
|
332 | 332 | # When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum |
|
|
333 | 333 | # is documented as struct, union, or enum with the name of the typedef. So |
|
|
334 | 334 | # typedef struct TypeS {} TypeT, will appear in the documentation as a struct |
|
|
335 | 335 | # with name TypeT. When disabled the typedef will appear as a member of a file, |
|
|
336 | 336 | # namespace, or class. And the struct will be named TypeS. This can typically |
|
|
337 | 337 | # be useful for C code in case the coding convention dictates that all compound |
|
|
338 | 338 | # types are typedef'ed and only the typedef is referenced, never the tag name. |
|
|
339 | 339 | |
|
|
340 | 340 | TYPEDEF_HIDES_STRUCT = YES |
|
|
341 | 341 | |
|
|
342 | 342 | # The SYMBOL_CACHE_SIZE determines the size of the internal cache use to |
|
|
343 | 343 | # determine which symbols to keep in memory and which to flush to disk. |
|
|
344 | 344 | # When the cache is full, less often used symbols will be written to disk. |
|
|
345 | 345 | # For small to medium size projects (<1000 input files) the default value is |
|
|
346 | 346 | # probably good enough. For larger projects a too small cache size can cause |
|
|
347 | 347 | # doxygen to be busy swapping symbols to and from disk most of the time |
|
|
348 | 348 | # causing a significant performance penalty. |
|
|
349 | 349 | # If the system has enough physical memory increasing the cache will improve the |
|
|
350 | 350 | # performance by keeping more symbols in memory. Note that the value works on |
|
|
351 | 351 | # a logarithmic scale so increasing the size by one will roughly double the |
|
|
352 | 352 | # memory usage. The cache size is given by this formula: |
|
|
353 | 353 | # 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0, |
|
|
354 | 354 | # corresponding to a cache size of 2^16 = 65536 symbols. |
|
|
355 | 355 | |
|
|
356 | 356 | SYMBOL_CACHE_SIZE = 0 |
|
|
357 | 357 | |
|
|
358 | 358 | # Similar to the SYMBOL_CACHE_SIZE the size of the symbol lookup cache can be |
|
|
359 | 359 | # set using LOOKUP_CACHE_SIZE. This cache is used to resolve symbols given |
|
|
360 | 360 | # their name and scope. Since this can be an expensive process and often the |
|
|
361 | 361 | # same symbol appear multiple times in the code, doxygen keeps a cache of |
|
|
362 | 362 | # pre-resolved symbols. If the cache is too small doxygen will become slower. |
|
|
363 | 363 | # If the cache is too large, memory is wasted. The cache size is given by this |
|
|
364 | 364 | # formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range is 0..9, the default is 0, |
|
|
365 | 365 | # corresponding to a cache size of 2^16 = 65536 symbols. |
|
|
366 | 366 | |
|
|
367 | 367 | LOOKUP_CACHE_SIZE = 0 |
|
|
368 | 368 | |
|
|
369 | 369 | #--------------------------------------------------------------------------- |
|
|
370 | 370 | # Build related configuration options |
|
|
371 | 371 | #--------------------------------------------------------------------------- |
|
|
372 | 372 | |
|
|
373 | 373 | # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in |
|
|
374 | 374 | # documentation are documented, even if no documentation was available. |
|
|
375 | 375 | # Private class members and static file members will be hidden unless |
|
|
376 | 376 | # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES |
|
|
377 | 377 | |
|
|
378 | 378 | EXTRACT_ALL = YES |
|
|
379 | 379 | |
|
|
380 | 380 | # If the EXTRACT_PRIVATE tag is set to YES all private members of a class |
|
|
381 | 381 | # will be included in the documentation. |
|
|
382 | 382 | |
|
|
383 | 383 | EXTRACT_PRIVATE = NO |
|
|
384 | 384 | |
|
|
385 | 385 | # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal |
|
|
386 | 386 | # scope will be included in the documentation. |
|
|
387 | 387 | |
|
|
388 | 388 | EXTRACT_PACKAGE = NO |
|
|
389 | 389 | |
|
|
390 | 390 | # If the EXTRACT_STATIC tag is set to YES all static members of a file |
|
|
391 | 391 | # will be included in the documentation. |
|
|
392 | 392 | |
|
|
393 | 393 | EXTRACT_STATIC = NO |
|
|
394 | 394 | |
|
|
395 | 395 | # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) |
|
|
396 | 396 | # defined locally in source files will be included in the documentation. |
|
|
397 | 397 | # If set to NO only classes defined in header files are included. |
|
|
398 | 398 | |
|
|
399 | 399 | EXTRACT_LOCAL_CLASSES = YES |
|
|
400 | 400 | |
|
|
401 | 401 | # This flag is only useful for Objective-C code. When set to YES local |
|
|
402 | 402 | # methods, which are defined in the implementation section but not in |
|
|
403 | 403 | # the interface are included in the documentation. |
|
|
404 | 404 | # If set to NO (the default) only methods in the interface are included. |
|
|
405 | 405 | |
|
|
406 | 406 | EXTRACT_LOCAL_METHODS = NO |
|
|
407 | 407 | |
|
|
408 | 408 | # If this flag is set to YES, the members of anonymous namespaces will be |
|
|
409 | 409 | # extracted and appear in the documentation as a namespace called |
|
|
410 | 410 | # 'anonymous_namespace{file}', where file will be replaced with the base |
|
|
411 | 411 | # name of the file that contains the anonymous namespace. By default |
|
|
412 | 412 | # anonymous namespaces are hidden. |
|
|
413 | 413 | |
|
|
414 | 414 | EXTRACT_ANON_NSPACES = NO |
|
|
415 | 415 | |
|
|
416 | 416 | # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all |
|
|
417 | 417 | # undocumented members of documented classes, files or namespaces. |
|
|
418 | 418 | # If set to NO (the default) these members will be included in the |
|
|
419 | 419 | # various overviews, but no documentation section is generated. |
|
|
420 | 420 | # This option has no effect if EXTRACT_ALL is enabled. |
|
|
421 | 421 | |
|
|
422 | 422 | HIDE_UNDOC_MEMBERS = NO |
|
|
423 | 423 | |
|
|
424 | 424 | # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all |
|
|
425 | 425 | # undocumented classes that are normally visible in the class hierarchy. |
|
|
426 | 426 | # If set to NO (the default) these classes will be included in the various |
|
|
427 | 427 | # overviews. This option has no effect if EXTRACT_ALL is enabled. |
|
|
428 | 428 | |
|
|
429 | 429 | HIDE_UNDOC_CLASSES = NO |
|
|
430 | 430 | |
|
|
431 | 431 | # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all |
|
|
432 | 432 | # friend (class|struct|union) declarations. |
|
|
433 | 433 | # If set to NO (the default) these declarations will be included in the |
|
|
434 | 434 | # documentation. |
|
|
435 | 435 | |
|
|
436 | 436 | HIDE_FRIEND_COMPOUNDS = NO |
|
|
437 | 437 | |
|
|
438 | 438 | # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any |
|
|
439 | 439 | # documentation blocks found inside the body of a function. |
|
|
440 | 440 | # If set to NO (the default) these blocks will be appended to the |
|
|
441 | 441 | # function's detailed documentation block. |
|
|
442 | 442 | |
|
|
443 | 443 | HIDE_IN_BODY_DOCS = NO |
|
|
444 | 444 | |
|
|
445 | 445 | # The INTERNAL_DOCS tag determines if documentation |
|
|
446 | 446 | # that is typed after a \internal command is included. If the tag is set |
|
|
447 | 447 | # to NO (the default) then the documentation will be excluded. |
|
|
448 | 448 | # Set it to YES to include the internal documentation. |
|
|
449 | 449 | |
|
|
450 | 450 | INTERNAL_DOCS = NO |
|
|
451 | 451 | |
|
|
452 | 452 | # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate |
|
|
453 | 453 | # file names in lower-case letters. If set to YES upper-case letters are also |
|
|
454 | 454 | # allowed. This is useful if you have classes or files whose names only differ |
|
|
455 | 455 | # in case and if your file system supports case sensitive file names. Windows |
|
|
456 | 456 | # and Mac users are advised to set this option to NO. |
|
|
457 | 457 | |
|
|
458 |
CASE_SENSE_NAMES = |
|
|
|
458 | CASE_SENSE_NAMES = YES | |
|
|
459 | 459 | |
|
|
460 | 460 | # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen |
|
|
461 | 461 | # will show members with their full class and namespace scopes in the |
|
|
462 | 462 | # documentation. If set to YES the scope will be hidden. |
|
|
463 | 463 | |
|
|
464 |
HIDE_SCOPE_NAMES = |
|
|
|
464 | HIDE_SCOPE_NAMES = NO | |
|
|
465 | 465 | |
|
|
466 | 466 | # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen |
|
|
467 | 467 | # will put a list of the files that are included by a file in the documentation |
|
|
468 | 468 | # of that file. |
|
|
469 | 469 | |
|
|
470 | 470 | SHOW_INCLUDE_FILES = YES |
|
|
471 | 471 | |
|
|
472 | 472 | # If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen |
|
|
473 | 473 | # will list include files with double quotes in the documentation |
|
|
474 | 474 | # rather than with sharp brackets. |
|
|
475 | 475 | |
|
|
476 | 476 | FORCE_LOCAL_INCLUDES = NO |
|
|
477 | 477 | |
|
|
478 | 478 | # If the INLINE_INFO tag is set to YES (the default) then a tag [inline] |
|
|
479 | 479 | # is inserted in the documentation for inline members. |
|
|
480 | 480 | |
|
|
481 | 481 | INLINE_INFO = YES |
|
|
482 | 482 | |
|
|
483 | 483 | # If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen |
|
|
484 | 484 | # will sort the (detailed) documentation of file and class members |
|
|
485 | 485 | # alphabetically by member name. If set to NO the members will appear in |
|
|
486 | 486 | # declaration order. |
|
|
487 | 487 | |
|
|
488 | 488 | SORT_MEMBER_DOCS = YES |
|
|
489 | 489 | |
|
|
490 | 490 | # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the |
|
|
491 | 491 | # brief documentation of file, namespace and class members alphabetically |
|
|
492 | 492 | # by member name. If set to NO (the default) the members will appear in |
|
|
493 | 493 | # declaration order. |
|
|
494 | 494 | |
|
|
495 | 495 | SORT_BRIEF_DOCS = NO |
|
|
496 | 496 | |
|
|
497 | 497 | # If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen |
|
|
498 | 498 | # will sort the (brief and detailed) documentation of class members so that |
|
|
499 | 499 | # constructors and destructors are listed first. If set to NO (the default) |
|
|
500 | 500 | # the constructors will appear in the respective orders defined by |
|
|
501 | 501 | # SORT_MEMBER_DOCS and SORT_BRIEF_DOCS. |
|
|
502 | 502 | # This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO |
|
|
503 | 503 | # and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO. |
|
|
504 | 504 | |
|
|
505 | 505 | SORT_MEMBERS_CTORS_1ST = NO |
|
|
506 | 506 | |
|
|
507 | 507 | # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the |
|
|
508 | 508 | # hierarchy of group names into alphabetical order. If set to NO (the default) |
|
|
509 | 509 | # the group names will appear in their defined order. |
|
|
510 | 510 | |
|
|
511 | 511 | SORT_GROUP_NAMES = NO |
|
|
512 | 512 | |
|
|
513 | 513 | # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be |
|
|
514 | 514 | # sorted by fully-qualified names, including namespaces. If set to |
|
|
515 | 515 | # NO (the default), the class list will be sorted only by class name, |
|
|
516 | 516 | # not including the namespace part. |
|
|
517 | 517 | # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. |
|
|
518 | 518 | # Note: This option applies only to the class list, not to the |
|
|
519 | 519 | # alphabetical list. |
|
|
520 | 520 | |
|
|
521 | 521 | SORT_BY_SCOPE_NAME = NO |
|
|
522 | 522 | |
|
|
523 | 523 | # If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to |
|
|
524 | 524 | # do proper type resolution of all parameters of a function it will reject a |
|
|
525 | 525 | # match between the prototype and the implementation of a member function even |
|
|
526 | 526 | # if there is only one candidate or it is obvious which candidate to choose |
|
|
527 | 527 | # by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen |
|
|
528 | 528 | # will still accept a match between prototype and implementation in such cases. |
|
|
529 | 529 | |
|
|
530 |
STRICT_PROTO_MATCHING = |
|
|
|
530 | STRICT_PROTO_MATCHING = YES | |
|
|
531 | 531 | |
|
|
532 | 532 | # The GENERATE_TODOLIST tag can be used to enable (YES) or |
|
|
533 | 533 | # disable (NO) the todo list. This list is created by putting \todo |
|
|
534 | 534 | # commands in the documentation. |
|
|
535 | 535 | |
|
|
536 | 536 | GENERATE_TODOLIST = YES |
|
|
537 | 537 | |
|
|
538 | 538 | # The GENERATE_TESTLIST tag can be used to enable (YES) or |
|
|
539 | 539 | # disable (NO) the test list. This list is created by putting \test |
|
|
540 | 540 | # commands in the documentation. |
|
|
541 | 541 | |
|
|
542 | 542 | GENERATE_TESTLIST = YES |
|
|
543 | 543 | |
|
|
544 | 544 | # The GENERATE_BUGLIST tag can be used to enable (YES) or |
|
|
545 | 545 | # disable (NO) the bug list. This list is created by putting \bug |
|
|
546 | 546 | # commands in the documentation. |
|
|
547 | 547 | |
|
|
548 | 548 | GENERATE_BUGLIST = YES |
|
|
549 | 549 | |
|
|
550 | 550 | # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or |
|
|
551 | 551 | # disable (NO) the deprecated list. This list is created by putting |
|
|
552 | 552 | # \deprecated commands in the documentation. |
|
|
553 | 553 | |
|
|
554 | 554 | GENERATE_DEPRECATEDLIST= YES |
|
|
555 | 555 | |
|
|
556 | 556 | # The ENABLED_SECTIONS tag can be used to enable conditional |
|
|
557 | 557 | # documentation sections, marked by \if section-label ... \endif |
|
|
558 | 558 | # and \cond section-label ... \endcond blocks. |
|
|
559 | 559 | |
|
|
560 | 560 | ENABLED_SECTIONS = |
|
|
561 | 561 | |
|
|
562 | 562 | # The MAX_INITIALIZER_LINES tag determines the maximum number of lines |
|
|
563 | 563 | # the initial value of a variable or macro consists of for it to appear in |
|
|
564 | 564 | # the documentation. If the initializer consists of more lines than specified |
|
|
565 | 565 | # here it will be hidden. Use a value of 0 to hide initializers completely. |
|
|
566 | 566 | # The appearance of the initializer of individual variables and macros in the |
|
|
567 | 567 | # documentation can be controlled using \showinitializer or \hideinitializer |
|
|
568 | 568 | # command in the documentation regardless of this setting. |
|
|
569 | 569 | |
|
|
570 | 570 | MAX_INITIALIZER_LINES = 30 |
|
|
571 | 571 | |
|
|
572 | 572 | # Set the SHOW_USED_FILES tag to NO to disable the list of files generated |
|
|
573 | 573 | # at the bottom of the documentation of classes and structs. If set to YES the |
|
|
574 | 574 | # list will mention the files that were used to generate the documentation. |
|
|
575 | 575 | |
|
|
576 | 576 | SHOW_USED_FILES = YES |
|
|
577 | 577 | |
|
|
578 | 578 | # Set the SHOW_FILES tag to NO to disable the generation of the Files page. |
|
|
579 | 579 | # This will remove the Files entry from the Quick Index and from the |
|
|
580 | 580 | # Folder Tree View (if specified). The default is YES. |
|
|
581 | 581 | |
|
|
582 | 582 | SHOW_FILES = YES |
|
|
583 | 583 | |
|
|
584 | 584 | # Set the SHOW_NAMESPACES tag to NO to disable the generation of the |
|
|
585 | 585 | # Namespaces page. This will remove the Namespaces entry from the Quick Index |
|
|
586 | 586 | # and from the Folder Tree View (if specified). The default is YES. |
|
|
587 | 587 | |
|
|
588 | 588 | SHOW_NAMESPACES = YES |
|
|
589 | 589 | |
|
|
590 | 590 | # The FILE_VERSION_FILTER tag can be used to specify a program or script that |
|
|
591 | 591 | # doxygen should invoke to get the current version for each file (typically from |
|
|
592 | 592 | # the version control system). Doxygen will invoke the program by executing (via |
|
|
593 | 593 | # popen()) the command <command> <input-file>, where <command> is the value of |
|
|
594 | 594 | # the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file |
|
|
595 | 595 | # provided by doxygen. Whatever the program writes to standard output |
|
|
596 | 596 | # is used as the file version. See the manual for examples. |
|
|
597 | 597 | |
|
|
598 | 598 | FILE_VERSION_FILTER = |
|
|
599 | 599 | |
|
|
600 | 600 | # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed |
|
|
601 | 601 | # by doxygen. The layout file controls the global structure of the generated |
|
|
602 | 602 | # output files in an output format independent way. To create the layout file |
|
|
603 | 603 | # that represents doxygen's defaults, run doxygen with the -l option. |
|
|
604 | 604 | # You can optionally specify a file name after the option, if omitted |
|
|
605 | 605 | # DoxygenLayout.xml will be used as the name of the layout file. |
|
|
606 | 606 | |
|
|
607 | 607 | LAYOUT_FILE = |
|
|
608 | 608 | |
|
|
609 | 609 | # The CITE_BIB_FILES tag can be used to specify one or more bib files |
|
|
610 | 610 | # containing the references data. This must be a list of .bib files. The |
|
|
611 | 611 | # .bib extension is automatically appended if omitted. Using this command |
|
|
612 | 612 | # requires the bibtex tool to be installed. See also |
|
|
613 | 613 | # http://en.wikipedia.org/wiki/BibTeX for more info. For LaTeX the style |
|
|
614 | 614 | # of the bibliography can be controlled using LATEX_BIB_STYLE. To use this |
|
|
615 | 615 | # feature you need bibtex and perl available in the search path. Do not use |
|
|
616 | 616 | # file names with spaces, bibtex cannot handle them. |
|
|
617 | 617 | |
|
|
618 | 618 | CITE_BIB_FILES = |
|
|
619 | 619 | |
|
|
620 | 620 | #--------------------------------------------------------------------------- |
|
|
621 | 621 | # configuration options related to warning and progress messages |
|
|
622 | 622 | #--------------------------------------------------------------------------- |
|
|
623 | 623 | |
|
|
624 | 624 | # The QUIET tag can be used to turn on/off the messages that are generated |
|
|
625 | 625 | # by doxygen. Possible values are YES and NO. If left blank NO is used. |
|
|
626 | 626 | |
|
|
627 | 627 | QUIET = NO |
|
|
628 | 628 | |
|
|
629 | 629 | # The WARNINGS tag can be used to turn on/off the warning messages that are |
|
|
630 | 630 | # generated by doxygen. Possible values are YES and NO. If left blank |
|
|
631 | 631 | # NO is used. |
|
|
632 | 632 | |
|
|
633 | 633 | WARNINGS = YES |
|
|
634 | 634 | |
|
|
635 | 635 | # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings |
|
|
636 | 636 | # for undocumented members. If EXTRACT_ALL is set to YES then this flag will |
|
|
637 | 637 | # automatically be disabled. |
|
|
638 | 638 | |
|
|
639 | 639 | WARN_IF_UNDOCUMENTED = YES |
|
|
640 | 640 | |
|
|
641 | 641 | # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for |
|
|
642 | 642 | # potential errors in the documentation, such as not documenting some |
|
|
643 | 643 | # parameters in a documented function, or documenting parameters that |
|
|
644 | 644 | # don't exist or using markup commands wrongly. |
|
|
645 | 645 | |
|
|
646 | 646 | WARN_IF_DOC_ERROR = YES |
|
|
647 | 647 | |
|
|
648 | 648 | # The WARN_NO_PARAMDOC option can be enabled to get warnings for |
|
|
649 | 649 | # functions that are documented, but have no documentation for their parameters |
|
|
650 | 650 | # or return value. If set to NO (the default) doxygen will only warn about |
|
|
651 | 651 | # wrong or incomplete parameter documentation, but not about the absence of |
|
|
652 | 652 | # documentation. |
|
|
653 | 653 | |
|
|
654 | 654 | WARN_NO_PARAMDOC = NO |
|
|
655 | 655 | |
|
|
656 | 656 | # The WARN_FORMAT tag determines the format of the warning messages that |
|
|
657 | 657 | # doxygen can produce. The string should contain the $file, $line, and $text |
|
|
658 | 658 | # tags, which will be replaced by the file and line number from which the |
|
|
659 | 659 | # warning originated and the warning text. Optionally the format may contain |
|
|
660 | 660 | # $version, which will be replaced by the version of the file (if it could |
|
|
661 | 661 | # be obtained via FILE_VERSION_FILTER) |
|
|
662 | 662 | |
|
|
663 | 663 | WARN_FORMAT = "$file:$line: $text" |
|
|
664 | 664 | |
|
|
665 | 665 | # The WARN_LOGFILE tag can be used to specify a file to which warning |
|
|
666 | 666 | # and error messages should be written. If left blank the output is written |
|
|
667 | 667 | # to stderr. |
|
|
668 | 668 | |
|
|
669 | 669 | WARN_LOGFILE = |
|
|
670 | 670 | |
|
|
671 | 671 | #--------------------------------------------------------------------------- |
|
|
672 | 672 | # configuration options related to the input files |
|
|
673 | 673 | #--------------------------------------------------------------------------- |
|
|
674 | 674 | |
|
|
675 | 675 | # The INPUT tag can be used to specify the files and/or directories that contain |
|
|
676 | 676 | # documented source files. You may enter file names like "myfile.cpp" or |
|
|
677 | 677 | # directories like "/usr/src/myproject". Separate the files or directories |
|
|
678 | 678 | # with spaces. |
|
|
679 | 679 | |
|
|
680 | INPUT = include | |
|
|
680 | INPUT = include \ | |
|
|
681 | src | |
|
|
681 | 682 | |
|
|
682 | 683 | # This tag can be used to specify the character encoding of the source files |
|
|
683 | 684 | # that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is |
|
|
684 | 685 | # also the default input encoding. Doxygen uses libiconv (or the iconv built |
|
|
685 | 686 | # into libc) for the transcoding. See http://www.gnu.org/software/libiconv for |
|
|
686 | 687 | # the list of possible encodings. |
|
|
687 | 688 | |
|
|
688 | 689 | INPUT_ENCODING = UTF-8 |
|
|
689 | 690 | |
|
|
690 | 691 | # If the value of the INPUT tag contains directories, you can use the |
|
|
691 | 692 | # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp |
|
|
692 | 693 | # and *.h) to filter out the source-files in the directories. If left |
|
|
693 | 694 | # blank the following patterns are tested: |
|
|
694 | 695 | # *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh |
|
|
695 | 696 | # *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py |
|
|
696 | 697 | # *.f90 *.f *.for *.vhd *.vhdl |
|
|
697 | 698 | |
|
|
698 | 699 | FILE_PATTERNS = *.c \ |
|
|
699 | 700 | *.cc \ |
|
|
700 | 701 | *.cxx \ |
|
|
701 | 702 | *.cpp \ |
|
|
702 | 703 | *.c++ \ |
|
|
703 | 704 | *.d \ |
|
|
704 | 705 | *.java \ |
|
|
705 | 706 | *.ii \ |
|
|
706 | 707 | *.ixx \ |
|
|
707 | 708 | *.ipp \ |
|
|
708 | 709 | *.i++ \ |
|
|
709 | 710 | *.inl \ |
|
|
710 | 711 | *.h \ |
|
|
711 | 712 | *.hh \ |
|
|
712 | 713 | *.hxx \ |
|
|
713 | 714 | *.hpp \ |
|
|
714 | 715 | *.h++ \ |
|
|
715 | 716 | *.idl \ |
|
|
716 | 717 | *.odl \ |
|
|
717 | 718 | *.cs \ |
|
|
718 | 719 | *.php \ |
|
|
719 | 720 | *.php3 \ |
|
|
720 | 721 | *.inc \ |
|
|
721 | 722 | *.m \ |
|
|
722 | 723 | *.markdown \ |
|
|
723 | 724 | *.md \ |
|
|
724 | 725 | *.mm \ |
|
|
725 | 726 | *.dox \ |
|
|
726 | 727 | *.py \ |
|
|
727 | 728 | *.f90 \ |
|
|
728 | 729 | *.f \ |
|
|
729 | 730 | *.for \ |
|
|
730 | 731 | *.vhd \ |
|
|
731 | 732 | *.vhdl |
|
|
732 | 733 | |
|
|
733 | 734 | # The RECURSIVE tag can be used to turn specify whether or not subdirectories |
|
|
734 | 735 | # should be searched for input files as well. Possible values are YES and NO. |
|
|
735 | 736 | # If left blank NO is used. |
|
|
736 | 737 | |
|
|
737 | 738 | RECURSIVE = YES |
|
|
738 | 739 | |
|
|
739 | 740 | # The EXCLUDE tag can be used to specify files and/or directories that should be |
|
|
740 | 741 | # excluded from the INPUT source files. This way you can easily exclude a |
|
|
741 | 742 | # subdirectory from a directory tree whose root is specified with the INPUT tag. |
|
|
742 | 743 | # Note that relative paths are relative to the directory from which doxygen is |
|
|
743 | 744 | # run. |
|
|
744 | 745 | |
|
|
745 | EXCLUDE = | |
|
|
746 | EXCLUDE = src/stm32f4/CPU/CMSIS \ | |
|
|
747 | src/stm32f4/CPU/STM32F4xx_StdPeriph_Driver \ | |
|
|
748 | src/stm32f4/CPU/USB \ | |
|
|
749 | src/lpc17XX | |
|
|
746 | 750 | |
|
|
747 | 751 | # The EXCLUDE_SYMLINKS tag can be used to select whether or not files or |
|
|
748 | 752 | # directories that are symbolic links (a Unix file system feature) are excluded |
|
|
749 | 753 | # from the input. |
|
|
750 | 754 | |
|
|
751 | 755 | EXCLUDE_SYMLINKS = NO |
|
|
752 | 756 | |
|
|
753 | 757 | # If the value of the INPUT tag contains directories, you can use the |
|
|
754 | 758 | # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude |
|
|
755 | 759 | # certain files from those directories. Note that the wildcards are matched |
|
|
756 | 760 | # against the file with absolute path, so to exclude all test directories |
|
|
757 | 761 | # for example use the pattern */test/* |
|
|
758 | 762 | |
|
|
759 | 763 | EXCLUDE_PATTERNS = |
|
|
760 | 764 | |
|
|
761 | 765 | # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names |
|
|
762 | 766 | # (namespaces, classes, functions, etc.) that should be excluded from the |
|
|
763 | 767 | # output. The symbol name can be a fully qualified name, a word, or if the |
|
|
764 | 768 | # wildcard * is used, a substring. Examples: ANamespace, AClass, |
|
|
765 | 769 | # AClass::ANamespace, ANamespace::*Test |
|
|
766 | 770 | |
|
|
767 | 771 | EXCLUDE_SYMBOLS = |
|
|
768 | 772 | |
|
|
769 | 773 | # The EXAMPLE_PATH tag can be used to specify one or more files or |
|
|
770 | 774 | # directories that contain example code fragments that are included (see |
|
|
771 | 775 | # the \include command). |
|
|
772 | 776 | |
|
|
773 | 777 | EXAMPLE_PATH = |
|
|
774 | 778 | |
|
|
775 | 779 | # If the value of the EXAMPLE_PATH tag contains directories, you can use the |
|
|
776 | 780 | # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp |
|
|
777 | 781 | # and *.h) to filter out the source-files in the directories. If left |
|
|
778 | 782 | # blank all files are included. |
|
|
779 | 783 | |
|
|
780 | 784 | EXAMPLE_PATTERNS = * |
|
|
781 | 785 | |
|
|
782 | 786 | # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be |
|
|
783 | 787 | # searched for input files to be used with the \include or \dontinclude |
|
|
784 | 788 | # commands irrespective of the value of the RECURSIVE tag. |
|
|
785 | 789 | # Possible values are YES and NO. If left blank NO is used. |
|
|
786 | 790 | |
|
|
787 | 791 | EXAMPLE_RECURSIVE = NO |
|
|
788 | 792 | |
|
|
789 | 793 | # The IMAGE_PATH tag can be used to specify one or more files or |
|
|
790 | 794 | # directories that contain image that are included in the documentation (see |
|
|
791 | 795 | # the \image command). |
|
|
792 | 796 | |
|
|
793 | 797 | IMAGE_PATH = |
|
|
794 | 798 | |
|
|
795 | 799 | # The INPUT_FILTER tag can be used to specify a program that doxygen should |
|
|
796 | 800 | # invoke to filter for each input file. Doxygen will invoke the filter program |
|
|
797 | 801 | # by executing (via popen()) the command <filter> <input-file>, where <filter> |
|
|
798 | 802 | # is the value of the INPUT_FILTER tag, and <input-file> is the name of an |
|
|
799 | 803 | # input file. Doxygen will then use the output that the filter program writes |
|
|
800 | 804 | # to standard output. If FILTER_PATTERNS is specified, this tag will be |
|
|
801 | 805 | # ignored. |
|
|
802 | 806 | |
|
|
803 | 807 | INPUT_FILTER = |
|
|
804 | 808 | |
|
|
805 | 809 | # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern |
|
|
806 | 810 | # basis. Doxygen will compare the file name with each pattern and apply the |
|
|
807 | 811 | # filter if there is a match. The filters are a list of the form: |
|
|
808 | 812 | # pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further |
|
|
809 | 813 | # info on how filters are used. If FILTER_PATTERNS is empty or if |
|
|
810 | 814 | # non of the patterns match the file name, INPUT_FILTER is applied. |
|
|
811 | 815 | |
|
|
812 | 816 | FILTER_PATTERNS = |
|
|
813 | 817 | |
|
|
814 | 818 | # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using |
|
|
815 | 819 | # INPUT_FILTER) will be used to filter the input files when producing source |
|
|
816 | 820 | # files to browse (i.e. when SOURCE_BROWSER is set to YES). |
|
|
817 | 821 | |
|
|
818 | 822 | FILTER_SOURCE_FILES = NO |
|
|
819 | 823 | |
|
|
820 | 824 | # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file |
|
|
821 | 825 | # pattern. A pattern will override the setting for FILTER_PATTERN (if any) |
|
|
822 | 826 | # and it is also possible to disable source filtering for a specific pattern |
|
|
823 | 827 | # using *.ext= (so without naming a filter). This option only has effect when |
|
|
824 | 828 | # FILTER_SOURCE_FILES is enabled. |
|
|
825 | 829 | |
|
|
826 | 830 | FILTER_SOURCE_PATTERNS = |
|
|
827 | 831 | |
|
|
828 | 832 | # If the USE_MD_FILE_AS_MAINPAGE tag refers to the name of a markdown file that |
|
|
829 | 833 | # is part of the input, its contents will be placed on the main page (index.html). |
|
|
830 | 834 | # This can be useful if you have a project on for instance GitHub and want reuse |
|
|
831 | 835 | # the introduction page also for the doxygen output. |
|
|
832 | 836 | |
|
|
833 | 837 | USE_MDFILE_AS_MAINPAGE = |
|
|
834 | 838 | |
|
|
835 | 839 | #--------------------------------------------------------------------------- |
|
|
836 | 840 | # configuration options related to source browsing |
|
|
837 | 841 | #--------------------------------------------------------------------------- |
|
|
838 | 842 | |
|
|
839 | 843 | # If the SOURCE_BROWSER tag is set to YES then a list of source files will |
|
|
840 | 844 | # be generated. Documented entities will be cross-referenced with these sources. |
|
|
841 | 845 | # Note: To get rid of all source code in the generated output, make sure also |
|
|
842 | 846 | # VERBATIM_HEADERS is set to NO. |
|
|
843 | 847 | |
|
|
844 | 848 | SOURCE_BROWSER = NO |
|
|
845 | 849 | |
|
|
846 | 850 | # Setting the INLINE_SOURCES tag to YES will include the body |
|
|
847 | 851 | # of functions and classes directly in the documentation. |
|
|
848 | 852 | |
|
|
849 | 853 | INLINE_SOURCES = NO |
|
|
850 | 854 | |
|
|
851 | 855 | # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct |
|
|
852 | 856 | # doxygen to hide any special comment blocks from generated source code |
|
|
853 | 857 | # fragments. Normal C, C++ and Fortran comments will always remain visible. |
|
|
854 | 858 | |
|
|
855 | 859 | STRIP_CODE_COMMENTS = YES |
|
|
856 | 860 | |
|
|
857 | 861 | # If the REFERENCED_BY_RELATION tag is set to YES |
|
|
858 | 862 | # then for each documented function all documented |
|
|
859 | 863 | # functions referencing it will be listed. |
|
|
860 | 864 | |
|
|
861 | 865 | REFERENCED_BY_RELATION = NO |
|
|
862 | 866 | |
|
|
863 | 867 | # If the REFERENCES_RELATION tag is set to YES |
|
|
864 | 868 | # then for each documented function all documented entities |
|
|
865 | 869 | # called/used by that function will be listed. |
|
|
866 | 870 | |
|
|
867 | 871 | REFERENCES_RELATION = NO |
|
|
868 | 872 | |
|
|
869 | 873 | # If the REFERENCES_LINK_SOURCE tag is set to YES (the default) |
|
|
870 | 874 | # and SOURCE_BROWSER tag is set to YES, then the hyperlinks from |
|
|
871 | 875 | # functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will |
|
|
872 | 876 | # link to the source code. Otherwise they will link to the documentation. |
|
|
873 | 877 | |
|
|
874 | 878 | REFERENCES_LINK_SOURCE = YES |
|
|
875 | 879 | |
|
|
876 | 880 | # If the USE_HTAGS tag is set to YES then the references to source code |
|
|
877 | 881 | # will point to the HTML generated by the htags(1) tool instead of doxygen |
|
|
878 | 882 | # built-in source browser. The htags tool is part of GNU's global source |
|
|
879 | 883 | # tagging system (see http://www.gnu.org/software/global/global.html). You |
|
|
880 | 884 | # will need version 4.8.6 or higher. |
|
|
881 | 885 | |
|
|
882 | 886 | USE_HTAGS = NO |
|
|
883 | 887 | |
|
|
884 | 888 | # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen |
|
|
885 | 889 | # will generate a verbatim copy of the header file for each class for |
|
|
886 | 890 | # which an include is specified. Set to NO to disable this. |
|
|
887 | 891 | |
|
|
888 | 892 | VERBATIM_HEADERS = YES |
|
|
889 | 893 | |
|
|
890 | 894 | #--------------------------------------------------------------------------- |
|
|
891 | 895 | # configuration options related to the alphabetical class index |
|
|
892 | 896 | #--------------------------------------------------------------------------- |
|
|
893 | 897 | |
|
|
894 | 898 | # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index |
|
|
895 | 899 | # of all compounds will be generated. Enable this if the project |
|
|
896 | 900 | # contains a lot of classes, structs, unions or interfaces. |
|
|
897 | 901 | |
|
|
898 | 902 | ALPHABETICAL_INDEX = YES |
|
|
899 | 903 | |
|
|
900 | 904 | # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then |
|
|
901 | 905 | # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns |
|
|
902 | 906 | # in which this list will be split (can be a number in the range [1..20]) |
|
|
903 | 907 | |
|
|
904 | 908 | COLS_IN_ALPHA_INDEX = 5 |
|
|
905 | 909 | |
|
|
906 | 910 | # In case all classes in a project start with a common prefix, all |
|
|
907 | 911 | # classes will be put under the same header in the alphabetical index. |
|
|
908 | 912 | # The IGNORE_PREFIX tag can be used to specify one or more prefixes that |
|
|
909 | 913 | # should be ignored while generating the index headers. |
|
|
910 | 914 | |
|
|
911 | 915 | IGNORE_PREFIX = |
|
|
912 | 916 | |
|
|
913 | 917 | #--------------------------------------------------------------------------- |
|
|
914 | 918 | # configuration options related to the HTML output |
|
|
915 | 919 | #--------------------------------------------------------------------------- |
|
|
916 | 920 | |
|
|
917 | 921 | # If the GENERATE_HTML tag is set to YES (the default) Doxygen will |
|
|
918 | 922 | # generate HTML output. |
|
|
919 | 923 | |
|
|
920 | 924 | GENERATE_HTML = YES |
|
|
921 | 925 | |
|
|
922 | 926 | # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. |
|
|
923 | 927 | # If a relative path is entered the value of OUTPUT_DIRECTORY will be |
|
|
924 | 928 | # put in front of it. If left blank `html' will be used as the default path. |
|
|
925 | 929 | |
|
|
926 | 930 | HTML_OUTPUT = html |
|
|
927 | 931 | |
|
|
928 | 932 | # The HTML_FILE_EXTENSION tag can be used to specify the file extension for |
|
|
929 | 933 | # each generated HTML page (for example: .htm,.php,.asp). If it is left blank |
|
|
930 | 934 | # doxygen will generate files with .html extension. |
|
|
931 | 935 | |
|
|
932 | 936 | HTML_FILE_EXTENSION = .html |
|
|
933 | 937 | |
|
|
934 | 938 | # The HTML_HEADER tag can be used to specify a personal HTML header for |
|
|
935 | 939 | # each generated HTML page. If it is left blank doxygen will generate a |
|
|
936 | 940 | # standard header. Note that when using a custom header you are responsible |
|
|
937 | 941 | # for the proper inclusion of any scripts and style sheets that doxygen |
|
|
938 | 942 | # needs, which is dependent on the configuration options used. |
|
|
939 | 943 | # It is advised to generate a default header using "doxygen -w html |
|
|
940 | 944 | # header.html footer.html stylesheet.css YourConfigFile" and then modify |
|
|
941 | 945 | # that header. Note that the header is subject to change so you typically |
|
|
942 | 946 | # have to redo this when upgrading to a newer version of doxygen or when |
|
|
943 | 947 | # changing the value of configuration settings such as GENERATE_TREEVIEW! |
|
|
944 | 948 | |
|
|
945 | 949 | HTML_HEADER = |
|
|
946 | 950 | |
|
|
947 | 951 | # The HTML_FOOTER tag can be used to specify a personal HTML footer for |
|
|
948 | 952 | # each generated HTML page. If it is left blank doxygen will generate a |
|
|
949 | 953 | # standard footer. |
|
|
950 | 954 | |
|
|
951 | 955 | HTML_FOOTER = |
|
|
952 | 956 | |
|
|
953 | 957 | # The HTML_STYLESHEET tag can be used to specify a user-defined cascading |
|
|
954 | 958 | # style sheet that is used by each HTML page. It can be used to |
|
|
955 | 959 | # fine-tune the look of the HTML output. If left blank doxygen will |
|
|
956 | 960 | # generate a default style sheet. Note that it is recommended to use |
|
|
957 | 961 | # HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this |
|
|
958 | 962 | # tag will in the future become obsolete. |
|
|
959 | 963 | |
|
|
960 | 964 | HTML_STYLESHEET = |
|
|
961 | 965 | |
|
|
962 | 966 | # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional |
|
|
963 | 967 | # user-defined cascading style sheet that is included after the standard |
|
|
964 | 968 | # style sheets created by doxygen. Using this option one can overrule |
|
|
965 | 969 | # certain style aspects. This is preferred over using HTML_STYLESHEET |
|
|
966 | 970 | # since it does not replace the standard style sheet and is therefor more |
|
|
967 | 971 | # robust against future updates. Doxygen will copy the style sheet file to |
|
|
968 | 972 | # the output directory. |
|
|
969 | 973 | |
|
|
970 | 974 | HTML_EXTRA_STYLESHEET = |
|
|
971 | 975 | |
|
|
972 | 976 | # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or |
|
|
973 | 977 | # other source files which should be copied to the HTML output directory. Note |
|
|
974 | 978 | # that these files will be copied to the base HTML output directory. Use the |
|
|
975 | 979 | # $relpath$ marker in the HTML_HEADER and/or HTML_FOOTER files to load these |
|
|
976 | 980 | # files. In the HTML_STYLESHEET file, use the file name only. Also note that |
|
|
977 | 981 | # the files will be copied as-is; there are no commands or markers available. |
|
|
978 | 982 | |
|
|
979 | 983 | HTML_EXTRA_FILES = |
|
|
980 | 984 | |
|
|
981 | 985 | # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. |
|
|
982 | 986 | # Doxygen will adjust the colors in the style sheet and background images |
|
|
983 | 987 | # according to this color. Hue is specified as an angle on a colorwheel, |
|
|
984 | 988 | # see http://en.wikipedia.org/wiki/Hue for more information. |
|
|
985 | 989 | # For instance the value 0 represents red, 60 is yellow, 120 is green, |
|
|
986 | 990 | # 180 is cyan, 240 is blue, 300 purple, and 360 is red again. |
|
|
987 | 991 | # The allowed range is 0 to 359. |
|
|
988 | 992 | |
|
|
989 | 993 | HTML_COLORSTYLE_HUE = 220 |
|
|
990 | 994 | |
|
|
991 | 995 | # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of |
|
|
992 | 996 | # the colors in the HTML output. For a value of 0 the output will use |
|
|
993 | 997 | # grayscales only. A value of 255 will produce the most vivid colors. |
|
|
994 | 998 | |
|
|
995 | 999 | HTML_COLORSTYLE_SAT = 100 |
|
|
996 | 1000 | |
|
|
997 | 1001 | # The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to |
|
|
998 | 1002 | # the luminance component of the colors in the HTML output. Values below |
|
|
999 | 1003 | # 100 gradually make the output lighter, whereas values above 100 make |
|
|
1000 | 1004 | # the output darker. The value divided by 100 is the actual gamma applied, |
|
|
1001 | 1005 | # so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2, |
|
|
1002 | 1006 | # and 100 does not change the gamma. |
|
|
1003 | 1007 | |
|
|
1004 | 1008 | HTML_COLORSTYLE_GAMMA = 80 |
|
|
1005 | 1009 | |
|
|
1006 | 1010 | # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML |
|
|
1007 | 1011 | # page will contain the date and time when the page was generated. Setting |
|
|
1008 | 1012 | # this to NO can help when comparing the output of multiple runs. |
|
|
1009 | 1013 | |
|
|
1010 | 1014 | HTML_TIMESTAMP = YES |
|
|
1011 | 1015 | |
|
|
1012 | 1016 | # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML |
|
|
1013 | 1017 | # documentation will contain sections that can be hidden and shown after the |
|
|
1014 | 1018 | # page has loaded. |
|
|
1015 | 1019 | |
|
|
1016 |
HTML_DYNAMIC_SECTIONS = |
|
|
|
1020 | HTML_DYNAMIC_SECTIONS = YES | |
|
|
1017 | 1021 | |
|
|
1018 | 1022 | # With HTML_INDEX_NUM_ENTRIES one can control the preferred number of |
|
|
1019 | 1023 | # entries shown in the various tree structured indices initially; the user |
|
|
1020 | 1024 | # can expand and collapse entries dynamically later on. Doxygen will expand |
|
|
1021 | 1025 | # the tree to such a level that at most the specified number of entries are |
|
|
1022 | 1026 | # visible (unless a fully collapsed tree already exceeds this amount). |
|
|
1023 | 1027 | # So setting the number of entries 1 will produce a full collapsed tree by |
|
|
1024 | 1028 | # default. 0 is a special value representing an infinite number of entries |
|
|
1025 | 1029 | # and will result in a full expanded tree by default. |
|
|
1026 | 1030 | |
|
|
1027 | 1031 | HTML_INDEX_NUM_ENTRIES = 100 |
|
|
1028 | 1032 | |
|
|
1029 | 1033 | # If the GENERATE_DOCSET tag is set to YES, additional index files |
|
|
1030 | 1034 | # will be generated that can be used as input for Apple's Xcode 3 |
|
|
1031 | 1035 | # integrated development environment, introduced with OSX 10.5 (Leopard). |
|
|
1032 | 1036 | # To create a documentation set, doxygen will generate a Makefile in the |
|
|
1033 | 1037 | # HTML output directory. Running make will produce the docset in that |
|
|
1034 | 1038 | # directory and running "make install" will install the docset in |
|
|
1035 | 1039 | # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find |
|
|
1036 | 1040 | # it at startup. |
|
|
1037 | 1041 | # See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html |
|
|
1038 | 1042 | # for more information. |
|
|
1039 | 1043 | |
|
|
1040 | 1044 | GENERATE_DOCSET = NO |
|
|
1041 | 1045 | |
|
|
1042 | 1046 | # When GENERATE_DOCSET tag is set to YES, this tag determines the name of the |
|
|
1043 | 1047 | # feed. A documentation feed provides an umbrella under which multiple |
|
|
1044 | 1048 | # documentation sets from a single provider (such as a company or product suite) |
|
|
1045 | 1049 | # can be grouped. |
|
|
1046 | 1050 | |
|
|
1047 | 1051 | DOCSET_FEEDNAME = "Doxygen generated docs" |
|
|
1048 | 1052 | |
|
|
1049 | 1053 | # When GENERATE_DOCSET tag is set to YES, this tag specifies a string that |
|
|
1050 | 1054 | # should uniquely identify the documentation set bundle. This should be a |
|
|
1051 | 1055 | # reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen |
|
|
1052 | 1056 | # will append .docset to the name. |
|
|
1053 | 1057 | |
|
|
1054 | 1058 | DOCSET_BUNDLE_ID = org.doxygen.Project |
|
|
1055 | 1059 | |
|
|
1056 | 1060 | # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely |
|
|
1057 | 1061 | # identify the documentation publisher. This should be a reverse domain-name |
|
|
1058 | 1062 | # style string, e.g. com.mycompany.MyDocSet.documentation. |
|
|
1059 | 1063 | |
|
|
1060 | 1064 | DOCSET_PUBLISHER_ID = org.doxygen.Publisher |
|
|
1061 | 1065 | |
|
|
1062 | 1066 | # The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher. |
|
|
1063 | 1067 | |
|
|
1064 | 1068 | DOCSET_PUBLISHER_NAME = Publisher |
|
|
1065 | 1069 | |
|
|
1066 | 1070 | # If the GENERATE_HTMLHELP tag is set to YES, additional index files |
|
|
1067 | 1071 | # will be generated that can be used as input for tools like the |
|
|
1068 | 1072 | # Microsoft HTML help workshop to generate a compiled HTML help file (.chm) |
|
|
1069 | 1073 | # of the generated HTML documentation. |
|
|
1070 | 1074 | |
|
|
1071 | 1075 | GENERATE_HTMLHELP = NO |
|
|
1072 | 1076 | |
|
|
1073 | 1077 | # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can |
|
|
1074 | 1078 | # be used to specify the file name of the resulting .chm file. You |
|
|
1075 | 1079 | # can add a path in front of the file if the result should not be |
|
|
1076 | 1080 | # written to the html output directory. |
|
|
1077 | 1081 | |
|
|
1078 | 1082 | CHM_FILE = |
|
|
1079 | 1083 | |
|
|
1080 | 1084 | # If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can |
|
|
1081 | 1085 | # be used to specify the location (absolute path including file name) of |
|
|
1082 | 1086 | # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run |
|
|
1083 | 1087 | # the HTML help compiler on the generated index.hhp. |
|
|
1084 | 1088 | |
|
|
1085 | 1089 | HHC_LOCATION = |
|
|
1086 | 1090 | |
|
|
1087 | 1091 | # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag |
|
|
1088 | 1092 | # controls if a separate .chi index file is generated (YES) or that |
|
|
1089 | 1093 | # it should be included in the master .chm file (NO). |
|
|
1090 | 1094 | |
|
|
1091 | 1095 | GENERATE_CHI = NO |
|
|
1092 | 1096 | |
|
|
1093 | 1097 | # If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING |
|
|
1094 | 1098 | # is used to encode HtmlHelp index (hhk), content (hhc) and project file |
|
|
1095 | 1099 | # content. |
|
|
1096 | 1100 | |
|
|
1097 | 1101 | CHM_INDEX_ENCODING = |
|
|
1098 | 1102 | |
|
|
1099 | 1103 | # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag |
|
|
1100 | 1104 | # controls whether a binary table of contents is generated (YES) or a |
|
|
1101 | 1105 | # normal table of contents (NO) in the .chm file. |
|
|
1102 | 1106 | |
|
|
1103 | 1107 | BINARY_TOC = NO |
|
|
1104 | 1108 | |
|
|
1105 | 1109 | # The TOC_EXPAND flag can be set to YES to add extra items for group members |
|
|
1106 | 1110 | # to the contents of the HTML help documentation and to the tree view. |
|
|
1107 | 1111 | |
|
|
1108 | 1112 | TOC_EXPAND = NO |
|
|
1109 | 1113 | |
|
|
1110 | 1114 | # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and |
|
|
1111 | 1115 | # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated |
|
|
1112 | 1116 | # that can be used as input for Qt's qhelpgenerator to generate a |
|
|
1113 | 1117 | # Qt Compressed Help (.qch) of the generated HTML documentation. |
|
|
1114 | 1118 | |
|
|
1115 |
GENERATE_QHP = |
|
|
|
1119 | GENERATE_QHP = YES | |
|
|
1116 | 1120 | |
|
|
1117 | 1121 | # If the QHG_LOCATION tag is specified, the QCH_FILE tag can |
|
|
1118 | 1122 | # be used to specify the file name of the resulting .qch file. |
|
|
1119 | 1123 | # The path specified is relative to the HTML output folder. |
|
|
1120 | 1124 | |
|
|
1121 | QCH_FILE = | |
|
|
1125 | QCH_FILE = ../../qthelp/libuc2.qch | |
|
|
1122 | 1126 | |
|
|
1123 | 1127 | # The QHP_NAMESPACE tag specifies the namespace to use when generating |
|
|
1124 | 1128 | # Qt Help Project output. For more information please see |
|
|
1125 | 1129 | # http://doc.trolltech.com/qthelpproject.html#namespace |
|
|
1126 | 1130 | |
|
|
1127 |
QHP_NAMESPACE = |
|
|
|
1131 | QHP_NAMESPACE = | |
|
|
1128 | 1132 | |
|
|
1129 | 1133 | # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating |
|
|
1130 | 1134 | # Qt Help Project output. For more information please see |
|
|
1131 | 1135 | # http://doc.trolltech.com/qthelpproject.html#virtual-folders |
|
|
1132 | 1136 | |
|
|
1133 |
QHP_VIRTUAL_FOLDER = |
|
|
|
1137 | QHP_VIRTUAL_FOLDER = libuc2 | |
|
|
1134 | 1138 | |
|
|
1135 | 1139 | # If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to |
|
|
1136 | 1140 | # add. For more information please see |
|
|
1137 | 1141 | # http://doc.trolltech.com/qthelpproject.html#custom-filters |
|
|
1138 | 1142 | |
|
|
1139 | 1143 | QHP_CUST_FILTER_NAME = |
|
|
1140 | 1144 | |
|
|
1141 | 1145 | # The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the |
|
|
1142 | 1146 | # custom filter to add. For more information please see |
|
|
1143 | 1147 | # <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters"> |
|
|
1144 | 1148 | # Qt Help Project / Custom Filters</a>. |
|
|
1145 | 1149 | |
|
|
1146 | 1150 | QHP_CUST_FILTER_ATTRS = |
|
|
1147 | 1151 | |
|
|
1148 | 1152 | # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this |
|
|
1149 | 1153 | # project's |
|
|
1150 | 1154 | # filter section matches. |
|
|
1151 | 1155 | # <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes"> |
|
|
1152 | 1156 | # Qt Help Project / Filter Attributes</a>. |
|
|
1153 | 1157 | |
|
|
1154 | 1158 | QHP_SECT_FILTER_ATTRS = |
|
|
1155 | 1159 | |
|
|
1156 | 1160 | # If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can |
|
|
1157 | 1161 | # be used to specify the location of Qt's qhelpgenerator. |
|
|
1158 | 1162 | # If non-empty doxygen will try to run qhelpgenerator on the generated |
|
|
1159 | 1163 | # .qhp file. |
|
|
1160 | 1164 | |
|
|
1161 | QHG_LOCATION = | |
|
|
1165 | QHG_LOCATION = qhelpgenerator | |
|
|
1162 | 1166 | |
|
|
1163 | 1167 | # If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files |
|
|
1164 | 1168 | # will be generated, which together with the HTML files, form an Eclipse help |
|
|
1165 | 1169 | # plugin. To install this plugin and make it available under the help contents |
|
|
1166 | 1170 | # menu in Eclipse, the contents of the directory containing the HTML and XML |
|
|
1167 | 1171 | # files needs to be copied into the plugins directory of eclipse. The name of |
|
|
1168 | 1172 | # the directory within the plugins directory should be the same as |
|
|
1169 | 1173 | # the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before |
|
|
1170 | 1174 | # the help appears. |
|
|
1171 | 1175 | |
|
|
1172 | 1176 | GENERATE_ECLIPSEHELP = NO |
|
|
1173 | 1177 | |
|
|
1174 | 1178 | # A unique identifier for the eclipse help plugin. When installing the plugin |
|
|
1175 | 1179 | # the directory name containing the HTML and XML files should also have |
|
|
1176 | 1180 | # this name. |
|
|
1177 | 1181 | |
|
|
1178 | 1182 | ECLIPSE_DOC_ID = org.doxygen.Project |
|
|
1179 | 1183 | |
|
|
1180 | 1184 | # The DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) |
|
|
1181 | 1185 | # at top of each HTML page. The value NO (the default) enables the index and |
|
|
1182 | 1186 | # the value YES disables it. Since the tabs have the same information as the |
|
|
1183 | 1187 | # navigation tree you can set this option to NO if you already set |
|
|
1184 | 1188 | # GENERATE_TREEVIEW to YES. |
|
|
1185 | 1189 | |
|
|
1186 | 1190 | DISABLE_INDEX = NO |
|
|
1187 | 1191 | |
|
|
1188 | 1192 | # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index |
|
|
1189 | 1193 | # structure should be generated to display hierarchical information. |
|
|
1190 | 1194 | # If the tag value is set to YES, a side panel will be generated |
|
|
1191 | 1195 | # containing a tree-like index structure (just like the one that |
|
|
1192 | 1196 | # is generated for HTML Help). For this to work a browser that supports |
|
|
1193 | 1197 | # JavaScript, DHTML, CSS and frames is required (i.e. any modern browser). |
|
|
1194 | 1198 | # Windows users are probably better off using the HTML help feature. |
|
|
1195 | 1199 | # Since the tree basically has the same information as the tab index you |
|
|
1196 | 1200 | # could consider to set DISABLE_INDEX to NO when enabling this option. |
|
|
1197 | 1201 | |
|
|
1198 | 1202 | GENERATE_TREEVIEW = NO |
|
|
1199 | 1203 | |
|
|
1200 | 1204 | # The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values |
|
|
1201 | 1205 | # (range [0,1..20]) that doxygen will group on one line in the generated HTML |
|
|
1202 | 1206 | # documentation. Note that a value of 0 will completely suppress the enum |
|
|
1203 | 1207 | # values from appearing in the overview section. |
|
|
1204 | 1208 | |
|
|
1205 | 1209 | ENUM_VALUES_PER_LINE = 4 |
|
|
1206 | 1210 | |
|
|
1207 | 1211 | # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be |
|
|
1208 | 1212 | # used to set the initial width (in pixels) of the frame in which the tree |
|
|
1209 | 1213 | # is shown. |
|
|
1210 | 1214 | |
|
|
1211 | 1215 | TREEVIEW_WIDTH = 250 |
|
|
1212 | 1216 | |
|
|
1213 | 1217 | # When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open |
|
|
1214 | 1218 | # links to external symbols imported via tag files in a separate window. |
|
|
1215 | 1219 | |
|
|
1216 | 1220 | EXT_LINKS_IN_WINDOW = NO |
|
|
1217 | 1221 | |
|
|
1218 | 1222 | # Use this tag to change the font size of Latex formulas included |
|
|
1219 | 1223 | # as images in the HTML documentation. The default is 10. Note that |
|
|
1220 | 1224 | # when you change the font size after a successful doxygen run you need |
|
|
1221 | 1225 | # to manually remove any form_*.png images from the HTML output directory |
|
|
1222 | 1226 | # to force them to be regenerated. |
|
|
1223 | 1227 | |
|
|
1224 | 1228 | FORMULA_FONTSIZE = 10 |
|
|
1225 | 1229 | |
|
|
1226 | 1230 | # Use the FORMULA_TRANPARENT tag to determine whether or not the images |
|
|
1227 | 1231 | # generated for formulas are transparent PNGs. Transparent PNGs are |
|
|
1228 | 1232 | # not supported properly for IE 6.0, but are supported on all modern browsers. |
|
|
1229 | 1233 | # Note that when changing this option you need to delete any form_*.png files |
|
|
1230 | 1234 | # in the HTML output before the changes have effect. |
|
|
1231 | 1235 | |
|
|
1232 | 1236 | FORMULA_TRANSPARENT = YES |
|
|
1233 | 1237 | |
|
|
1234 | 1238 | # Enable the USE_MATHJAX option to render LaTeX formulas using MathJax |
|
|
1235 | 1239 | # (see http://www.mathjax.org) which uses client side Javascript for the |
|
|
1236 | 1240 | # rendering instead of using prerendered bitmaps. Use this if you do not |
|
|
1237 | 1241 | # have LaTeX installed or if you want to formulas look prettier in the HTML |
|
|
1238 | 1242 | # output. When enabled you may also need to install MathJax separately and |
|
|
1239 | 1243 | # configure the path to it using the MATHJAX_RELPATH option. |
|
|
1240 | 1244 | |
|
|
1241 | 1245 | USE_MATHJAX = NO |
|
|
1242 | 1246 | |
|
|
1243 | 1247 | # When MathJax is enabled you can set the default output format to be used for |
|
|
1244 | 1248 | # thA MathJax output. Supported types are HTML-CSS, NativeMML (i.e. MathML) and |
|
|
1245 | 1249 | # SVG. The default value is HTML-CSS, which is slower, but has the best |
|
|
1246 | 1250 | # compatibility. |
|
|
1247 | 1251 | |
|
|
1248 | 1252 | MATHJAX_FORMAT = HTML-CSS |
|
|
1249 | 1253 | |
|
|
1250 | 1254 | # When MathJax is enabled you need to specify the location relative to the |
|
|
1251 | 1255 | # HTML output directory using the MATHJAX_RELPATH option. The destination |
|
|
1252 | 1256 | # directory should contain the MathJax.js script. For instance, if the mathjax |
|
|
1253 | 1257 | # directory is located at the same level as the HTML output directory, then |
|
|
1254 | 1258 | # MATHJAX_RELPATH should be ../mathjax. The default value points to |
|
|
1255 | 1259 | # the MathJax Content Delivery Network so you can quickly see the result without |
|
|
1256 | 1260 | # installing MathJax. However, it is strongly recommended to install a local |
|
|
1257 | 1261 | # copy of MathJax from http://www.mathjax.org before deployment. |
|
|
1258 | 1262 | |
|
|
1259 | 1263 | MATHJAX_RELPATH = http://cdn.mathjax.org/mathjax/latest |
|
|
1260 | 1264 | |
|
|
1261 | 1265 | # The MATHJAX_EXTENSIONS tag can be used to specify one or MathJax extension |
|
|
1262 | 1266 | # names that should be enabled during MathJax rendering. |
|
|
1263 | 1267 | |
|
|
1264 | 1268 | MATHJAX_EXTENSIONS = |
|
|
1265 | 1269 | |
|
|
1266 | 1270 | # When the SEARCHENGINE tag is enabled doxygen will generate a search box |
|
|
1267 | 1271 | # for the HTML output. The underlying search engine uses javascript |
|
|
1268 | 1272 | # and DHTML and should work on any modern browser. Note that when using |
|
|
1269 | 1273 | # HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets |
|
|
1270 | 1274 | # (GENERATE_DOCSET) there is already a search function so this one should |
|
|
1271 | 1275 | # typically be disabled. For large projects the javascript based search engine |
|
|
1272 | 1276 | # can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution. |
|
|
1273 | 1277 | |
|
|
1274 | 1278 | SEARCHENGINE = YES |
|
|
1275 | 1279 | |
|
|
1276 | 1280 | # When the SERVER_BASED_SEARCH tag is enabled the search engine will be |
|
|
1277 | 1281 | # implemented using a web server instead of a web client using Javascript. |
|
|
1278 | 1282 | # There are two flavours of web server based search depending on the |
|
|
1279 | 1283 | # EXTERNAL_SEARCH setting. When disabled, doxygen will generate a PHP script for |
|
|
1280 | 1284 | # searching and an index file used by the script. When EXTERNAL_SEARCH is |
|
|
1281 | 1285 | # enabled the indexing and searching needs to be provided by external tools. |
|
|
1282 | 1286 | # See the manual for details. |
|
|
1283 | 1287 | |
|
|
1284 | 1288 | SERVER_BASED_SEARCH = NO |
|
|
1285 | 1289 | |
|
|
1286 | 1290 | # When EXTERNAL_SEARCH is enabled doxygen will no longer generate the PHP |
|
|
1287 | 1291 | # script for searching. Instead the search results are written to an XML file |
|
|
1288 | 1292 | # which needs to be processed by an external indexer. Doxygen will invoke an |
|
|
1289 | 1293 | # external search engine pointed to by the SEARCHENGINE_URL option to obtain |
|
|
1290 | 1294 | # the search results. Doxygen ships with an example indexer (doxyindexer) and |
|
|
1291 | 1295 | # search engine (doxysearch.cgi) which are based on the open source search engine |
|
|
1292 | 1296 | # library Xapian. See the manual for configuration details. |
|
|
1293 | 1297 | |
|
|
1294 | 1298 | EXTERNAL_SEARCH = NO |
|
|
1295 | 1299 | |
|
|
1296 | 1300 | # The SEARCHENGINE_URL should point to a search engine hosted by a web server |
|
|
1297 | 1301 | # which will returned the search results when EXTERNAL_SEARCH is enabled. |
|
|
1298 | 1302 | # Doxygen ships with an example search engine (doxysearch) which is based on |
|
|
1299 | 1303 | # the open source search engine library Xapian. See the manual for configuration |
|
|
1300 | 1304 | # details. |
|
|
1301 | 1305 | |
|
|
1302 | 1306 | SEARCHENGINE_URL = |
|
|
1303 | 1307 | |
|
|
1304 | 1308 | # When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the unindexed |
|
|
1305 | 1309 | # search data is written to a file for indexing by an external tool. With the |
|
|
1306 | 1310 | # SEARCHDATA_FILE tag the name of this file can be specified. |
|
|
1307 | 1311 | |
|
|
1308 | 1312 | SEARCHDATA_FILE = searchdata.xml |
|
|
1309 | 1313 | |
|
|
1310 | 1314 | # When SERVER_BASED_SEARCH AND EXTERNAL_SEARCH are both enabled the |
|
|
1311 | 1315 | # EXTERNAL_SEARCH_ID tag can be used as an identifier for the project. This is |
|
|
1312 | 1316 | # useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple |
|
|
1313 | 1317 | # projects and redirect the results back to the right project. |
|
|
1314 | 1318 | |
|
|
1315 | 1319 | EXTERNAL_SEARCH_ID = |
|
|
1316 | 1320 | |
|
|
1317 | 1321 | # The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen |
|
|
1318 | 1322 | # projects other than the one defined by this configuration file, but that are |
|
|
1319 | 1323 | # all added to the same external search index. Each project needs to have a |
|
|
1320 | 1324 | # unique id set via EXTERNAL_SEARCH_ID. The search mapping then maps the id |
|
|
1321 | 1325 | # of to a relative location where the documentation can be found. |
|
|
1322 | 1326 | # The format is: EXTRA_SEARCH_MAPPINGS = id1=loc1 id2=loc2 ... |
|
|
1323 | 1327 | |
|
|
1324 | 1328 | EXTRA_SEARCH_MAPPINGS = |
|
|
1325 | 1329 | |
|
|
1326 | 1330 | #--------------------------------------------------------------------------- |
|
|
1327 | 1331 | # configuration options related to the LaTeX output |
|
|
1328 | 1332 | #--------------------------------------------------------------------------- |
|
|
1329 | 1333 | |
|
|
1330 | 1334 | # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will |
|
|
1331 | 1335 | # generate Latex output. |
|
|
1332 | 1336 | |
|
|
1333 | 1337 | GENERATE_LATEX = YES |
|
|
1334 | 1338 | |
|
|
1335 | 1339 | # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. |
|
|
1336 | 1340 | # If a relative path is entered the value of OUTPUT_DIRECTORY will be |
|
|
1337 | 1341 | # put in front of it. If left blank `latex' will be used as the default path. |
|
|
1338 | 1342 | |
|
|
1339 | 1343 | LATEX_OUTPUT = latex |
|
|
1340 | 1344 | |
|
|
1341 | 1345 | # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be |
|
|
1342 | 1346 | # invoked. If left blank `latex' will be used as the default command name. |
|
|
1343 | 1347 | # Note that when enabling USE_PDFLATEX this option is only used for |
|
|
1344 | 1348 | # generating bitmaps for formulas in the HTML output, but not in the |
|
|
1345 | 1349 | # Makefile that is written to the output directory. |
|
|
1346 | 1350 | |
|
|
1347 | 1351 | LATEX_CMD_NAME = latex |
|
|
1348 | 1352 | |
|
|
1349 | 1353 | # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to |
|
|
1350 | 1354 | # generate index for LaTeX. If left blank `makeindex' will be used as the |
|
|
1351 | 1355 | # default command name. |
|
|
1352 | 1356 | |
|
|
1353 | 1357 | MAKEINDEX_CMD_NAME = makeindex |
|
|
1354 | 1358 | |
|
|
1355 | 1359 | # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact |
|
|
1356 | 1360 | # LaTeX documents. This may be useful for small projects and may help to |
|
|
1357 | 1361 | # save some trees in general. |
|
|
1358 | 1362 | |
|
|
1359 | 1363 | COMPACT_LATEX = NO |
|
|
1360 | 1364 | |
|
|
1361 | 1365 | # The PAPER_TYPE tag can be used to set the paper type that is used |
|
|
1362 | 1366 | # by the printer. Possible values are: a4, letter, legal and |
|
|
1363 | 1367 | # executive. If left blank a4wide will be used. |
|
|
1364 | 1368 | |
|
|
1365 | 1369 | PAPER_TYPE = a4 |
|
|
1366 | 1370 | |
|
|
1367 | 1371 | # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX |
|
|
1368 | 1372 | # packages that should be included in the LaTeX output. |
|
|
1369 | 1373 | |
|
|
1370 | 1374 | EXTRA_PACKAGES = |
|
|
1371 | 1375 | |
|
|
1372 | 1376 | # The LATEX_HEADER tag can be used to specify a personal LaTeX header for |
|
|
1373 | 1377 | # the generated latex document. The header should contain everything until |
|
|
1374 | 1378 | # the first chapter. If it is left blank doxygen will generate a |
|
|
1375 | 1379 | # standard header. Notice: only use this tag if you know what you are doing! |
|
|
1376 | 1380 | |
|
|
1377 | 1381 | LATEX_HEADER = |
|
|
1378 | 1382 | |
|
|
1379 | 1383 | # The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for |
|
|
1380 | 1384 | # the generated latex document. The footer should contain everything after |
|
|
1381 | 1385 | # the last chapter. If it is left blank doxygen will generate a |
|
|
1382 | 1386 | # standard footer. Notice: only use this tag if you know what you are doing! |
|
|
1383 | 1387 | |
|
|
1384 | 1388 | LATEX_FOOTER = |
|
|
1385 | 1389 | |
|
|
1386 | 1390 | # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated |
|
|
1387 | 1391 | # is prepared for conversion to pdf (using ps2pdf). The pdf file will |
|
|
1388 | 1392 | # contain links (just like the HTML output) instead of page references |
|
|
1389 | 1393 | # This makes the output suitable for online browsing using a pdf viewer. |
|
|
1390 | 1394 | |
|
|
1391 | 1395 | PDF_HYPERLINKS = YES |
|
|
1392 | 1396 | |
|
|
1393 | 1397 | # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of |
|
|
1394 | 1398 | # plain latex in the generated Makefile. Set this option to YES to get a |
|
|
1395 | 1399 | # higher quality PDF documentation. |
|
|
1396 | 1400 | |
|
|
1397 | 1401 | USE_PDFLATEX = YES |
|
|
1398 | 1402 | |
|
|
1399 | 1403 | # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. |
|
|
1400 | 1404 | # command to the generated LaTeX files. This will instruct LaTeX to keep |
|
|
1401 | 1405 | # running if errors occur, instead of asking the user for help. |
|
|
1402 | 1406 | # This option is also used when generating formulas in HTML. |
|
|
1403 | 1407 | |
|
|
1404 | 1408 | LATEX_BATCHMODE = NO |
|
|
1405 | 1409 | |
|
|
1406 | 1410 | # If LATEX_HIDE_INDICES is set to YES then doxygen will not |
|
|
1407 | 1411 | # include the index chapters (such as File Index, Compound Index, etc.) |
|
|
1408 | 1412 | # in the output. |
|
|
1409 | 1413 | |
|
|
1410 | 1414 | LATEX_HIDE_INDICES = NO |
|
|
1411 | 1415 | |
|
|
1412 | 1416 | # If LATEX_SOURCE_CODE is set to YES then doxygen will include |
|
|
1413 | 1417 | # source code with syntax highlighting in the LaTeX output. |
|
|
1414 | 1418 | # Note that which sources are shown also depends on other settings |
|
|
1415 | 1419 | # such as SOURCE_BROWSER. |
|
|
1416 | 1420 | |
|
|
1417 | 1421 | LATEX_SOURCE_CODE = NO |
|
|
1418 | 1422 | |
|
|
1419 | 1423 | # The LATEX_BIB_STYLE tag can be used to specify the style to use for the |
|
|
1420 | 1424 | # bibliography, e.g. plainnat, or ieeetr. The default style is "plain". See |
|
|
1421 | 1425 | # http://en.wikipedia.org/wiki/BibTeX for more info. |
|
|
1422 | 1426 | |
|
|
1423 | 1427 | LATEX_BIB_STYLE = plain |
|
|
1424 | 1428 | |
|
|
1425 | 1429 | #--------------------------------------------------------------------------- |
|
|
1426 | 1430 | # configuration options related to the RTF output |
|
|
1427 | 1431 | #--------------------------------------------------------------------------- |
|
|
1428 | 1432 | |
|
|
1429 | 1433 | # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output |
|
|
1430 | 1434 | # The RTF output is optimized for Word 97 and may not look very pretty with |
|
|
1431 | 1435 | # other RTF readers or editors. |
|
|
1432 | 1436 | |
|
|
1433 | 1437 | GENERATE_RTF = NO |
|
|
1434 | 1438 | |
|
|
1435 | 1439 | # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. |
|
|
1436 | 1440 | # If a relative path is entered the value of OUTPUT_DIRECTORY will be |
|
|
1437 | 1441 | # put in front of it. If left blank `rtf' will be used as the default path. |
|
|
1438 | 1442 | |
|
|
1439 | 1443 | RTF_OUTPUT = rtf |
|
|
1440 | 1444 | |
|
|
1441 | 1445 | # If the COMPACT_RTF tag is set to YES Doxygen generates more compact |
|
|
1442 | 1446 | # RTF documents. This may be useful for small projects and may help to |
|
|
1443 | 1447 | # save some trees in general. |
|
|
1444 | 1448 | |
|
|
1445 | 1449 | COMPACT_RTF = NO |
|
|
1446 | 1450 | |
|
|
1447 | 1451 | # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated |
|
|
1448 | 1452 | # will contain hyperlink fields. The RTF file will |
|
|
1449 | 1453 | # contain links (just like the HTML output) instead of page references. |
|
|
1450 | 1454 | # This makes the output suitable for online browsing using WORD or other |
|
|
1451 | 1455 | # programs which support those fields. |
|
|
1452 | 1456 | # Note: wordpad (write) and others do not support links. |
|
|
1453 | 1457 | |
|
|
1454 | 1458 | RTF_HYPERLINKS = NO |
|
|
1455 | 1459 | |
|
|
1456 | 1460 | # Load style sheet definitions from file. Syntax is similar to doxygen's |
|
|
1457 | 1461 | # config file, i.e. a series of assignments. You only have to provide |
|
|
1458 | 1462 | # replacements, missing definitions are set to their default value. |
|
|
1459 | 1463 | |
|
|
1460 | 1464 | RTF_STYLESHEET_FILE = |
|
|
1461 | 1465 | |
|
|
1462 | 1466 | # Set optional variables used in the generation of an rtf document. |
|
|
1463 | 1467 | # Syntax is similar to doxygen's config file. |
|
|
1464 | 1468 | |
|
|
1465 | 1469 | RTF_EXTENSIONS_FILE = |
|
|
1466 | 1470 | |
|
|
1467 | 1471 | #--------------------------------------------------------------------------- |
|
|
1468 | 1472 | # configuration options related to the man page output |
|
|
1469 | 1473 | #--------------------------------------------------------------------------- |
|
|
1470 | 1474 | |
|
|
1471 | 1475 | # If the GENERATE_MAN tag is set to YES (the default) Doxygen will |
|
|
1472 | 1476 | # generate man pages |
|
|
1473 | 1477 | |
|
|
1474 | 1478 | GENERATE_MAN = NO |
|
|
1475 | 1479 | |
|
|
1476 | 1480 | # The MAN_OUTPUT tag is used to specify where the man pages will be put. |
|
|
1477 | 1481 | # If a relative path is entered the value of OUTPUT_DIRECTORY will be |
|
|
1478 | 1482 | # put in front of it. If left blank `man' will be used as the default path. |
|
|
1479 | 1483 | |
|
|
1480 | 1484 | MAN_OUTPUT = man |
|
|
1481 | 1485 | |
|
|
1482 | 1486 | # The MAN_EXTENSION tag determines the extension that is added to |
|
|
1483 | 1487 | # the generated man pages (default is the subroutine's section .3) |
|
|
1484 | 1488 | |
|
|
1485 | 1489 | MAN_EXTENSION = .3 |
|
|
1486 | 1490 | |
|
|
1487 | 1491 | # If the MAN_LINKS tag is set to YES and Doxygen generates man output, |
|
|
1488 | 1492 | # then it will generate one additional man file for each entity |
|
|
1489 | 1493 | # documented in the real man page(s). These additional files |
|
|
1490 | 1494 | # only source the real man page, but without them the man command |
|
|
1491 | 1495 | # would be unable to find the correct page. The default is NO. |
|
|
1492 | 1496 | |
|
|
1493 | 1497 | MAN_LINKS = NO |
|
|
1494 | 1498 | |
|
|
1495 | 1499 | #--------------------------------------------------------------------------- |
|
|
1496 | 1500 | # configuration options related to the XML output |
|
|
1497 | 1501 | #--------------------------------------------------------------------------- |
|
|
1498 | 1502 | |
|
|
1499 | 1503 | # If the GENERATE_XML tag is set to YES Doxygen will |
|
|
1500 | 1504 | # generate an XML file that captures the structure of |
|
|
1501 | 1505 | # the code including all documentation. |
|
|
1502 | 1506 | |
|
|
1503 | 1507 | GENERATE_XML = NO |
|
|
1504 | 1508 | |
|
|
1505 | 1509 | # The XML_OUTPUT tag is used to specify where the XML pages will be put. |
|
|
1506 | 1510 | # If a relative path is entered the value of OUTPUT_DIRECTORY will be |
|
|
1507 | 1511 | # put in front of it. If left blank `xml' will be used as the default path. |
|
|
1508 | 1512 | |
|
|
1509 | 1513 | XML_OUTPUT = xml |
|
|
1510 | 1514 | |
|
|
1511 | 1515 | # The XML_SCHEMA tag can be used to specify an XML schema, |
|
|
1512 | 1516 | # which can be used by a validating XML parser to check the |
|
|
1513 | 1517 | # syntax of the XML files. |
|
|
1514 | 1518 | |
|
|
1515 | 1519 | XML_SCHEMA = |
|
|
1516 | 1520 | |
|
|
1517 | 1521 | # The XML_DTD tag can be used to specify an XML DTD, |
|
|
1518 | 1522 | # which can be used by a validating XML parser to check the |
|
|
1519 | 1523 | # syntax of the XML files. |
|
|
1520 | 1524 | |
|
|
1521 | 1525 | XML_DTD = |
|
|
1522 | 1526 | |
|
|
1523 | 1527 | # If the XML_PROGRAMLISTING tag is set to YES Doxygen will |
|
|
1524 | 1528 | # dump the program listings (including syntax highlighting |
|
|
1525 | 1529 | # and cross-referencing information) to the XML output. Note that |
|
|
1526 | 1530 | # enabling this will significantly increase the size of the XML output. |
|
|
1527 | 1531 | |
|
|
1528 | 1532 | XML_PROGRAMLISTING = YES |
|
|
1529 | 1533 | |
|
|
1530 | 1534 | #--------------------------------------------------------------------------- |
|
|
1531 | 1535 | # configuration options for the AutoGen Definitions output |
|
|
1532 | 1536 | #--------------------------------------------------------------------------- |
|
|
1533 | 1537 | |
|
|
1534 | 1538 | # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will |
|
|
1535 | 1539 | # generate an AutoGen Definitions (see autogen.sf.net) file |
|
|
1536 | 1540 | # that captures the structure of the code including all |
|
|
1537 | 1541 | # documentation. Note that this feature is still experimental |
|
|
1538 | 1542 | # and incomplete at the moment. |
|
|
1539 | 1543 | |
|
|
1540 | 1544 | GENERATE_AUTOGEN_DEF = NO |
|
|
1541 | 1545 | |
|
|
1542 | 1546 | #--------------------------------------------------------------------------- |
|
|
1543 | 1547 | # configuration options related to the Perl module output |
|
|
1544 | 1548 | #--------------------------------------------------------------------------- |
|
|
1545 | 1549 | |
|
|
1546 | 1550 | # If the GENERATE_PERLMOD tag is set to YES Doxygen will |
|
|
1547 | 1551 | # generate a Perl module file that captures the structure of |
|
|
1548 | 1552 | # the code including all documentation. Note that this |
|
|
1549 | 1553 | # feature is still experimental and incomplete at the |
|
|
1550 | 1554 | # moment. |
|
|
1551 | 1555 | |
|
|
1552 | 1556 | GENERATE_PERLMOD = NO |
|
|
1553 | 1557 | |
|
|
1554 | 1558 | # If the PERLMOD_LATEX tag is set to YES Doxygen will generate |
|
|
1555 | 1559 | # the necessary Makefile rules, Perl scripts and LaTeX code to be able |
|
|
1556 | 1560 | # to generate PDF and DVI output from the Perl module output. |
|
|
1557 | 1561 | |
|
|
1558 | 1562 | PERLMOD_LATEX = NO |
|
|
1559 | 1563 | |
|
|
1560 | 1564 | # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be |
|
|
1561 | 1565 | # nicely formatted so it can be parsed by a human reader. This is useful |
|
|
1562 | 1566 | # if you want to understand what is going on. On the other hand, if this |
|
|
1563 | 1567 | # tag is set to NO the size of the Perl module output will be much smaller |
|
|
1564 | 1568 | # and Perl will parse it just the same. |
|
|
1565 | 1569 | |
|
|
1566 | 1570 | PERLMOD_PRETTY = YES |
|
|
1567 | 1571 | |
|
|
1568 | 1572 | # The names of the make variables in the generated doxyrules.make file |
|
|
1569 | 1573 | # are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. |
|
|
1570 | 1574 | # This is useful so different doxyrules.make files included by the same |
|
|
1571 | 1575 | # Makefile don't overwrite each other's variables. |
|
|
1572 | 1576 | |
|
|
1573 | 1577 | PERLMOD_MAKEVAR_PREFIX = |
|
|
1574 | 1578 | |
|
|
1575 | 1579 | #--------------------------------------------------------------------------- |
|
|
1576 | 1580 | # Configuration options related to the preprocessor |
|
|
1577 | 1581 | #--------------------------------------------------------------------------- |
|
|
1578 | 1582 | |
|
|
1579 | 1583 | # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will |
|
|
1580 | 1584 | # evaluate all C-preprocessor directives found in the sources and include |
|
|
1581 | 1585 | # files. |
|
|
1582 | 1586 | |
|
|
1583 | 1587 | ENABLE_PREPROCESSING = YES |
|
|
1584 | 1588 | |
|
|
1585 | 1589 | # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro |
|
|
1586 | 1590 | # names in the source code. If set to NO (the default) only conditional |
|
|
1587 | 1591 | # compilation will be performed. Macro expansion can be done in a controlled |
|
|
1588 | 1592 | # way by setting EXPAND_ONLY_PREDEF to YES. |
|
|
1589 | 1593 | |
|
|
1590 | 1594 | MACRO_EXPANSION = NO |
|
|
1591 | 1595 | |
|
|
1592 | 1596 | # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES |
|
|
1593 | 1597 | # then the macro expansion is limited to the macros specified with the |
|
|
1594 | 1598 | # PREDEFINED and EXPAND_AS_DEFINED tags. |
|
|
1595 | 1599 | |
|
|
1596 | 1600 | EXPAND_ONLY_PREDEF = NO |
|
|
1597 | 1601 | |
|
|
1598 | 1602 | # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files |
|
|
1599 | 1603 | # pointed to by INCLUDE_PATH will be searched when a #include is found. |
|
|
1600 | 1604 | |
|
|
1601 | 1605 | SEARCH_INCLUDES = YES |
|
|
1602 | 1606 | |
|
|
1603 | 1607 | # The INCLUDE_PATH tag can be used to specify one or more directories that |
|
|
1604 | 1608 | # contain include files that are not input files but should be processed by |
|
|
1605 | 1609 | # the preprocessor. |
|
|
1606 | 1610 | |
|
|
1607 | 1611 | INCLUDE_PATH = |
|
|
1608 | 1612 | |
|
|
1609 | 1613 | # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard |
|
|
1610 | 1614 | # patterns (like *.h and *.hpp) to filter out the header-files in the |
|
|
1611 | 1615 | # directories. If left blank, the patterns specified with FILE_PATTERNS will |
|
|
1612 | 1616 | # be used. |
|
|
1613 | 1617 | |
|
|
1614 | 1618 | INCLUDE_FILE_PATTERNS = |
|
|
1615 | 1619 | |
|
|
1616 | 1620 | # The PREDEFINED tag can be used to specify one or more macro names that |
|
|
1617 | 1621 | # are defined before the preprocessor is started (similar to the -D option of |
|
|
1618 | 1622 | # gcc). The argument of the tag is a list of macros of the form: name |
|
|
1619 | 1623 | # or name=definition (no spaces). If the definition and the = are |
|
|
1620 | 1624 | # omitted =1 is assumed. To prevent a macro definition from being |
|
|
1621 | 1625 | # undefined via #undef or recursively expanded use the := operator |
|
|
1622 | 1626 | # instead of the = operator. |
|
|
1623 | 1627 | |
|
|
1624 | 1628 | PREDEFINED = DOXYGEN_SHOULD_SKIP_THIS |
|
|
1625 | 1629 | |
|
|
1626 | 1630 | # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then |
|
|
1627 | 1631 | # this tag can be used to specify a list of macro names that should be expanded. |
|
|
1628 | 1632 | # The macro definition that is found in the sources will be used. |
|
|
1629 | 1633 | # Use the PREDEFINED tag if you want to use a different macro definition that |
|
|
1630 | 1634 | # overrules the definition found in the source code. |
|
|
1631 | 1635 | |
|
|
1632 | 1636 | EXPAND_AS_DEFINED = |
|
|
1633 | 1637 | |
|
|
1634 | 1638 | # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then |
|
|
1635 | 1639 | # doxygen's preprocessor will remove all references to function-like macros |
|
|
1636 | 1640 | # that are alone on a line, have an all uppercase name, and do not end with a |
|
|
1637 | 1641 | # semicolon, because these will confuse the parser if not removed. |
|
|
1638 | 1642 | |
|
|
1639 | 1643 | SKIP_FUNCTION_MACROS = YES |
|
|
1640 | 1644 | |
|
|
1641 | 1645 | #--------------------------------------------------------------------------- |
|
|
1642 | 1646 | # Configuration::additions related to external references |
|
|
1643 | 1647 | #--------------------------------------------------------------------------- |
|
|
1644 | 1648 | |
|
|
1645 | 1649 | # The TAGFILES option can be used to specify one or more tagfiles. For each |
|
|
1646 | 1650 | # tag file the location of the external documentation should be added. The |
|
|
1647 | 1651 | # format of a tag file without this location is as follows: |
|
|
1648 | 1652 | # TAGFILES = file1 file2 ... |
|
|
1649 | 1653 | # Adding location for the tag files is done as follows: |
|
|
1650 | 1654 | # TAGFILES = file1=loc1 "file2 = loc2" ... |
|
|
1651 | 1655 | # where "loc1" and "loc2" can be relative or absolute paths |
|
|
1652 | 1656 | # or URLs. Note that each tag file must have a unique name (where the name does |
|
|
1653 | 1657 | # NOT include the path). If a tag file is not located in the directory in which |
|
|
1654 | 1658 | # doxygen is run, you must also specify the path to the tagfile here. |
|
|
1655 | 1659 | |
|
|
1656 | 1660 | TAGFILES = |
|
|
1657 | 1661 | |
|
|
1658 | 1662 | # When a file name is specified after GENERATE_TAGFILE, doxygen will create |
|
|
1659 | 1663 | # a tag file that is based on the input files it reads. |
|
|
1660 | 1664 | |
|
|
1661 | 1665 | GENERATE_TAGFILE = |
|
|
1662 | 1666 | |
|
|
1663 | 1667 | # If the ALLEXTERNALS tag is set to YES all external classes will be listed |
|
|
1664 | 1668 | # in the class index. If set to NO only the inherited external classes |
|
|
1665 | 1669 | # will be listed. |
|
|
1666 | 1670 | |
|
|
1667 | 1671 | ALLEXTERNALS = NO |
|
|
1668 | 1672 | |
|
|
1669 | 1673 | # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed |
|
|
1670 | 1674 | # in the modules index. If set to NO, only the current project's groups will |
|
|
1671 | 1675 | # be listed. |
|
|
1672 | 1676 | |
|
|
1673 | 1677 | EXTERNAL_GROUPS = YES |
|
|
1674 | 1678 | |
|
|
1675 | 1679 | # The PERL_PATH should be the absolute path and name of the perl script |
|
|
1676 | 1680 | # interpreter (i.e. the result of `which perl'). |
|
|
1677 | 1681 | |
|
|
1678 | 1682 | PERL_PATH = /usr/bin/perl |
|
|
1679 | 1683 | |
|
|
1680 | 1684 | #--------------------------------------------------------------------------- |
|
|
1681 | 1685 | # Configuration options related to the dot tool |
|
|
1682 | 1686 | #--------------------------------------------------------------------------- |
|
|
1683 | 1687 | |
|
|
1684 | 1688 | # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will |
|
|
1685 | 1689 | # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base |
|
|
1686 | 1690 | # or super classes. Setting the tag to NO turns the diagrams off. Note that |
|
|
1687 | 1691 | # this option also works with HAVE_DOT disabled, but it is recommended to |
|
|
1688 | 1692 | # install and use dot, since it yields more powerful graphs. |
|
|
1689 | 1693 | |
|
|
1690 | 1694 | CLASS_DIAGRAMS = NO |
|
|
1691 | 1695 | |
|
|
1692 | 1696 | # You can define message sequence charts within doxygen comments using the \msc |
|
|
1693 | 1697 | # command. Doxygen will then run the mscgen tool (see |
|
|
1694 | 1698 | # http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the |
|
|
1695 | 1699 | # documentation. The MSCGEN_PATH tag allows you to specify the directory where |
|
|
1696 | 1700 | # the mscgen tool resides. If left empty the tool is assumed to be found in the |
|
|
1697 | 1701 | # default search path. |
|
|
1698 | 1702 | |
|
|
1699 | 1703 | MSCGEN_PATH = |
|
|
1700 | 1704 | |
|
|
1701 | 1705 | # If set to YES, the inheritance and collaboration graphs will hide |
|
|
1702 | 1706 | # inheritance and usage relations if the target is undocumented |
|
|
1703 | 1707 | # or is not a class. |
|
|
1704 | 1708 | |
|
|
1705 | 1709 | HIDE_UNDOC_RELATIONS = YES |
|
|
1706 | 1710 | |
|
|
1707 | 1711 | # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is |
|
|
1708 | 1712 | # available from the path. This tool is part of Graphviz, a graph visualization |
|
|
1709 | 1713 | # toolkit from AT&T and Lucent Bell Labs. The other options in this section |
|
|
1710 | 1714 | # have no effect if this option is set to NO (the default) |
|
|
1711 | 1715 | |
|
|
1712 | 1716 | HAVE_DOT = YES |
|
|
1713 | 1717 | |
|
|
1714 | 1718 | # The DOT_NUM_THREADS specifies the number of dot invocations doxygen is |
|
|
1715 | 1719 | # allowed to run in parallel. When set to 0 (the default) doxygen will |
|
|
1716 | 1720 | # base this on the number of processors available in the system. You can set it |
|
|
1717 | 1721 | # explicitly to a value larger than 0 to get control over the balance |
|
|
1718 | 1722 | # between CPU load and processing speed. |
|
|
1719 | 1723 | |
|
|
1720 | 1724 | DOT_NUM_THREADS = 4 |
|
|
1721 | 1725 | |
|
|
1722 | 1726 | # By default doxygen will use the Helvetica font for all dot files that |
|
|
1723 | 1727 | # doxygen generates. When you want a differently looking font you can specify |
|
|
1724 | 1728 | # the font name using DOT_FONTNAME. You need to make sure dot is able to find |
|
|
1725 | 1729 | # the font, which can be done by putting it in a standard location or by setting |
|
|
1726 | 1730 | # the DOTFONTPATH environment variable or by setting DOT_FONTPATH to the |
|
|
1727 | 1731 | # directory containing the font. |
|
|
1728 | 1732 | |
|
|
1729 | 1733 | DOT_FONTNAME = Helvetica |
|
|
1730 | 1734 | |
|
|
1731 | 1735 | # The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs. |
|
|
1732 | 1736 | # The default size is 10pt. |
|
|
1733 | 1737 | |
|
|
1734 | 1738 | DOT_FONTSIZE = 10 |
|
|
1735 | 1739 | |
|
|
1736 | 1740 | # By default doxygen will tell dot to use the Helvetica font. |
|
|
1737 | 1741 | # If you specify a different font using DOT_FONTNAME you can use DOT_FONTPATH to |
|
|
1738 | 1742 | # set the path where dot can find it. |
|
|
1739 | 1743 | |
|
|
1740 | 1744 | DOT_FONTPATH = |
|
|
1741 | 1745 | |
|
|
1742 | 1746 | # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen |
|
|
1743 | 1747 | # will generate a graph for each documented class showing the direct and |
|
|
1744 | 1748 | # indirect inheritance relations. Setting this tag to YES will force the |
|
|
1745 | 1749 | # CLASS_DIAGRAMS tag to NO. |
|
|
1746 | 1750 | |
|
|
1747 | 1751 | CLASS_GRAPH = YES |
|
|
1748 | 1752 | |
|
|
1749 | 1753 | # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen |
|
|
1750 | 1754 | # will generate a graph for each documented class showing the direct and |
|
|
1751 | 1755 | # indirect implementation dependencies (inheritance, containment, and |
|
|
1752 | 1756 | # class references variables) of the class with other documented classes. |
|
|
1753 | 1757 | |
|
|
1754 | 1758 | COLLABORATION_GRAPH = YES |
|
|
1755 | 1759 | |
|
|
1756 | 1760 | # If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen |
|
|
1757 | 1761 | # will generate a graph for groups, showing the direct groups dependencies |
|
|
1758 | 1762 | |
|
|
1759 | 1763 | GROUP_GRAPHS = YES |
|
|
1760 | 1764 | |
|
|
1761 | 1765 | # If the UML_LOOK tag is set to YES doxygen will generate inheritance and |
|
|
1762 | 1766 | # collaboration diagrams in a style similar to the OMG's Unified Modeling |
|
|
1763 | 1767 | # Language. |
|
|
1764 | 1768 | |
|
|
1765 | 1769 | UML_LOOK = NO |
|
|
1766 | 1770 | |
|
|
1767 | 1771 | # If the UML_LOOK tag is enabled, the fields and methods are shown inside |
|
|
1768 | 1772 | # the class node. If there are many fields or methods and many nodes the |
|
|
1769 | 1773 | # graph may become too big to be useful. The UML_LIMIT_NUM_FIELDS |
|
|
1770 | 1774 | # threshold limits the number of items for each type to make the size more |
|
|
1771 | 1775 | # managable. Set this to 0 for no limit. Note that the threshold may be |
|
|
1772 | 1776 | # exceeded by 50% before the limit is enforced. |
|
|
1773 | 1777 | |
|
|
1774 | 1778 | UML_LIMIT_NUM_FIELDS = 10 |
|
|
1775 | 1779 | |
|
|
1776 | 1780 | # If set to YES, the inheritance and collaboration graphs will show the |
|
|
1777 | 1781 | # relations between templates and their instances. |
|
|
1778 | 1782 | |
|
|
1779 | 1783 | TEMPLATE_RELATIONS = NO |
|
|
1780 | 1784 | |
|
|
1781 | 1785 | # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT |
|
|
1782 | 1786 | # tags are set to YES then doxygen will generate a graph for each documented |
|
|
1783 | 1787 | # file showing the direct and indirect include dependencies of the file with |
|
|
1784 | 1788 | # other documented files. |
|
|
1785 | 1789 | |
|
|
1786 | 1790 | INCLUDE_GRAPH = YES |
|
|
1787 | 1791 | |
|
|
1788 | 1792 | # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and |
|
|
1789 | 1793 | # HAVE_DOT tags are set to YES then doxygen will generate a graph for each |
|
|
1790 | 1794 | # documented header file showing the documented files that directly or |
|
|
1791 | 1795 | # indirectly include this file. |
|
|
1792 | 1796 | |
|
|
1793 | 1797 | INCLUDED_BY_GRAPH = YES |
|
|
1794 | 1798 | |
|
|
1795 | 1799 | # If the CALL_GRAPH and HAVE_DOT options are set to YES then |
|
|
1796 | 1800 | # doxygen will generate a call dependency graph for every global function |
|
|
1797 | 1801 | # or class method. Note that enabling this option will significantly increase |
|
|
1798 | 1802 | # the time of a run. So in most cases it will be better to enable call graphs |
|
|
1799 | 1803 | # for selected functions only using the \callgraph command. |
|
|
1800 | 1804 | |
|
|
1801 | 1805 | CALL_GRAPH = YES |
|
|
1802 | 1806 | |
|
|
1803 | 1807 | # If the CALLER_GRAPH and HAVE_DOT tags are set to YES then |
|
|
1804 | 1808 | # doxygen will generate a caller dependency graph for every global function |
|
|
1805 | 1809 | # or class method. Note that enabling this option will significantly increase |
|
|
1806 | 1810 | # the time of a run. So in most cases it will be better to enable caller |
|
|
1807 | 1811 | # graphs for selected functions only using the \callergraph command. |
|
|
1808 | 1812 | |
|
|
1809 | 1813 | CALLER_GRAPH = YES |
|
|
1810 | 1814 | |
|
|
1811 | 1815 | # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen |
|
|
1812 | 1816 | # will generate a graphical hierarchy of all classes instead of a textual one. |
|
|
1813 | 1817 | |
|
|
1814 | 1818 | GRAPHICAL_HIERARCHY = YES |
|
|
1815 | 1819 | |
|
|
1816 | 1820 | # If the DIRECTORY_GRAPH and HAVE_DOT tags are set to YES |
|
|
1817 | 1821 | # then doxygen will show the dependencies a directory has on other directories |
|
|
1818 | 1822 | # in a graphical way. The dependency relations are determined by the #include |
|
|
1819 | 1823 | # relations between the files in the directories. |
|
|
1820 | 1824 | |
|
|
1821 | 1825 | DIRECTORY_GRAPH = YES |
|
|
1822 | 1826 | |
|
|
1823 | 1827 | # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images |
|
|
1824 | 1828 | # generated by dot. Possible values are svg, png, jpg, or gif. |
|
|
1825 | 1829 | # If left blank png will be used. If you choose svg you need to set |
|
|
1826 | 1830 | # HTML_FILE_EXTENSION to xhtml in order to make the SVG files |
|
|
1827 | 1831 | # visible in IE 9+ (other browsers do not have this requirement). |
|
|
1828 | 1832 | |
|
|
1829 | 1833 | DOT_IMAGE_FORMAT = png |
|
|
1830 | 1834 | |
|
|
1831 | 1835 | # If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to |
|
|
1832 | 1836 | # enable generation of interactive SVG images that allow zooming and panning. |
|
|
1833 | 1837 | # Note that this requires a modern browser other than Internet Explorer. |
|
|
1834 | 1838 | # Tested and working are Firefox, Chrome, Safari, and Opera. For IE 9+ you |
|
|
1835 | 1839 | # need to set HTML_FILE_EXTENSION to xhtml in order to make the SVG files |
|
|
1836 | 1840 | # visible. Older versions of IE do not have SVG support. |
|
|
1837 | 1841 | |
|
|
1838 | 1842 | INTERACTIVE_SVG = YES |
|
|
1839 | 1843 | |
|
|
1840 | 1844 | # The tag DOT_PATH can be used to specify the path where the dot tool can be |
|
|
1841 | 1845 | # found. If left blank, it is assumed the dot tool can be found in the path. |
|
|
1842 | 1846 | |
|
|
1843 | 1847 | DOT_PATH = |
|
|
1844 | 1848 | |
|
|
1845 | 1849 | # The DOTFILE_DIRS tag can be used to specify one or more directories that |
|
|
1846 | 1850 | # contain dot files that are included in the documentation (see the |
|
|
1847 | 1851 | # \dotfile command). |
|
|
1848 | 1852 | |
|
|
1849 | 1853 | DOTFILE_DIRS = |
|
|
1850 | 1854 | |
|
|
1851 | 1855 | # The MSCFILE_DIRS tag can be used to specify one or more directories that |
|
|
1852 | 1856 | # contain msc files that are included in the documentation (see the |
|
|
1853 | 1857 | # \mscfile command). |
|
|
1854 | 1858 | |
|
|
1855 | 1859 | MSCFILE_DIRS = |
|
|
1856 | 1860 | |
|
|
1857 | 1861 | # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of |
|
|
1858 | 1862 | # nodes that will be shown in the graph. If the number of nodes in a graph |
|
|
1859 | 1863 | # becomes larger than this value, doxygen will truncate the graph, which is |
|
|
1860 | 1864 | # visualized by representing a node as a red box. Note that doxygen if the |
|
|
1861 | 1865 | # number of direct children of the root node in a graph is already larger than |
|
|
1862 | 1866 | # DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note |
|
|
1863 | 1867 | # that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH. |
|
|
1864 | 1868 | |
|
|
1865 | 1869 | DOT_GRAPH_MAX_NODES = 50 |
|
|
1866 | 1870 | |
|
|
1867 | 1871 | # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the |
|
|
1868 | 1872 | # graphs generated by dot. A depth value of 3 means that only nodes reachable |
|
|
1869 | 1873 | # from the root by following a path via at most 3 edges will be shown. Nodes |
|
|
1870 | 1874 | # that lay further from the root node will be omitted. Note that setting this |
|
|
1871 | 1875 | # option to 1 or 2 may greatly reduce the computation time needed for large |
|
|
1872 | 1876 | # code bases. Also note that the size of a graph can be further restricted by |
|
|
1873 | 1877 | # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction. |
|
|
1874 | 1878 | |
|
|
1875 | 1879 | MAX_DOT_GRAPH_DEPTH = 0 |
|
|
1876 | 1880 | |
|
|
1877 | 1881 | # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent |
|
|
1878 | 1882 | # background. This is disabled by default, because dot on Windows does not |
|
|
1879 | 1883 | # seem to support this out of the box. Warning: Depending on the platform used, |
|
|
1880 | 1884 | # enabling this option may lead to badly anti-aliased labels on the edges of |
|
|
1881 | 1885 | # a graph (i.e. they become hard to read). |
|
|
1882 | 1886 | |
|
|
1883 | 1887 | DOT_TRANSPARENT = NO |
|
|
1884 | 1888 | |
|
|
1885 | 1889 | # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output |
|
|
1886 | 1890 | # files in one run (i.e. multiple -o and -T options on the command line). This |
|
|
1887 | 1891 | # makes dot run faster, but since only newer versions of dot (>1.8.10) |
|
|
1888 | 1892 | # support this, this feature is disabled by default. |
|
|
1889 | 1893 | |
|
|
1890 | 1894 | DOT_MULTI_TARGETS = NO |
|
|
1891 | 1895 | |
|
|
1892 | 1896 | # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will |
|
|
1893 | 1897 | # generate a legend page explaining the meaning of the various boxes and |
|
|
1894 | 1898 | # arrows in the dot generated graphs. |
|
|
1895 | 1899 | |
|
|
1896 | 1900 | GENERATE_LEGEND = YES |
|
|
1897 | 1901 | |
|
|
1898 | 1902 | # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will |
|
|
1899 | 1903 | # remove the intermediate dot files that are used to generate |
|
|
1900 | 1904 | # the various graphs. |
|
|
1901 | 1905 | |
|
|
1902 | 1906 | DOT_CLEANUP = YES |
General Comments 0
You need to be logged in to leave comments.
Login now