Mercurial > pidgin.yaz
annotate Doxyfile.in @ 18951:11e88e451bfb
- Reorder struct for clarity
author | William Ehlhardt <williamehlhardt@gmail.com> |
---|---|
date | Tue, 26 Jun 2007 19:49:33 +0000 |
parents | b20fa7ebb911 |
children | 5c6f019e48f8 |
rev | line source |
---|---|
12800 | 1 # Doxyfile 1.4.4 |
4554 | 2 |
3 # This file describes the settings to be used by the documentation system | |
4 # doxygen (www.doxygen.org) for a project | |
5 # | |
6 # All text after a hash (#) is considered a comment and will be ignored | |
7 # The format is: | |
8 # TAG = value [value, ...] | |
9 # For lists items can also be appended using: | |
10 # TAG += value [value, ...] | |
11 # Values that contain spaces should be placed between quotes (" ") | |
12 | |
13 #--------------------------------------------------------------------------- | |
7806 | 14 # Project related configuration options |
4554 | 15 #--------------------------------------------------------------------------- |
16 | |
17 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded | |
18 # by quotes) that should identify the project. | |
19 | |
20 PROJECT_NAME = @PACKAGE@ | |
21 | |
22 # The PROJECT_NUMBER tag can be used to enter a project or revision number. | |
23 # This could be handy for archiving the generated documentation or | |
24 # if some version control system is used. | |
25 | |
26 PROJECT_NUMBER = @VERSION@ | |
27 | |
28 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) | |
29 # base path where the generated documentation will be put. | |
30 # If a relative path is entered, it will be relative to the location | |
31 # where doxygen was started. If left blank the current directory will be used. | |
32 | |
33 OUTPUT_DIRECTORY = doc | |
34 | |
12800 | 35 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create |
36 # 4096 sub-directories (in 2 levels) under the output directory of each output | |
37 # format and will distribute the generated files over these directories. | |
38 # Enabling this option can be useful when feeding doxygen a huge amount of | |
39 # source files, where putting all generated files in the same directory would | |
40 # otherwise cause performance problems for the file system. | |
41 | |
42 CREATE_SUBDIRS = NO | |
43 | |
4554 | 44 # The OUTPUT_LANGUAGE tag is used to specify the language in which all |
45 # documentation generated by doxygen is written. Doxygen will use this | |
46 # information to generate all constant output in the proper language. | |
47 # The default language is English, other supported languages are: | |
48 # Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch, | |
49 # Finnish, French, German, Greek, Hungarian, Italian, Japanese, Japanese-en | |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
50 # (Japanese with English messages), Korean, Norwegian, Polish, Portuguese, |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
51 # Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish, and Ukrainian. |
4554 | 52 |
53 OUTPUT_LANGUAGE = English | |
54 | |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
55 # This tag can be used to specify the encoding used in the generated output. |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
56 # The encoding is not always determined by the language that is chosen, |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
57 # but also whether or not the output is meant for Windows or non-Windows users. |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
58 # In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
59 # forces the Windows encoding (this is the default for the Windows binary), |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
60 # whereas setting the tag to NO uses a Unix-style encoding (the default for |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
61 # all platforms other than Windows). |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
62 |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
63 USE_WINDOWS_ENCODING = NO |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
64 |
7806 | 65 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will |
66 # include brief member descriptions after the members that are listed in | |
67 # the file and class documentation (similar to JavaDoc). | |
68 # Set to NO to disable this. | |
69 | |
70 BRIEF_MEMBER_DESC = YES | |
71 | |
72 # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend | |
73 # the brief description of a member or function before the detailed description. | |
74 # Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the | |
75 # brief descriptions will be completely suppressed. | |
76 | |
77 REPEAT_BRIEF = YES | |
78 | |
79 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then | |
80 # Doxygen will generate a detailed section even if there is only a brief | |
81 # description. | |
82 | |
83 ALWAYS_DETAILED_SEC = NO | |
84 | |
85 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all inherited | |
86 # members of a class in the documentation of that class as if those members were | |
87 # ordinary class members. Constructors, destructors and assignment operators of | |
88 # the base classes will not be shown. | |
89 | |
90 INLINE_INHERITED_MEMB = NO | |
91 | |
92 # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full | |
93 # path before files name in the file list and in the header files. If set | |
94 # to NO the shortest path that makes the file name unique will be used. | |
95 | |
96 FULL_PATH_NAMES = NO | |
97 | |
98 # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag | |
99 # can be used to strip a user-defined part of the path. Stripping is | |
100 # only done if one of the specified strings matches the left-hand part of | |
101 # the path. It is allowed to use relative paths in the argument list. | |
102 | |
103 STRIP_FROM_PATH = | |
104 | |
105 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter | |
106 # (but less readable) file names. This can be useful is your file systems | |
107 # doesn't support long names like on DOS, Mac, or CD-ROM. | |
108 | |
109 SHORT_NAMES = NO | |
110 | |
111 # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen | |
112 # will interpret the first line (until the first dot) of a JavaDoc-style | |
113 # comment as the brief description. If set to NO, the JavaDoc | |
114 # comments will behave just like the Qt-style comments (thus requiring an | |
115 # explict @brief command for a brief description. | |
116 | |
117 JAVADOC_AUTOBRIEF = YES | |
118 | |
119 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen | |
120 # treat a multi-line C++ special comment block (i.e. a block of //! or /// | |
121 # comments) as a brief description. This used to be the default behaviour. | |
122 # The new default is to treat a multi-line C++ comment block as a detailed | |
123 # description. Set this tag to YES if you prefer the old behaviour instead. | |
124 | |
125 MULTILINE_CPP_IS_BRIEF = NO | |
126 | |
127 # If the DETAILS_AT_TOP tag is set to YES then Doxygen | |
128 # will output the detailed description near the top, like JavaDoc. | |
129 # If set to NO, the detailed description appears after the member | |
130 # documentation. | |
131 | |
132 DETAILS_AT_TOP = NO | |
133 | |
134 # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented | |
135 # member inherits the documentation from any documented member that it | |
136 # reimplements. | |
137 | |
138 INHERIT_DOCS = YES | |
139 | |
140 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC | |
141 # tag is set to YES, then doxygen will reuse the documentation of the first | |
142 # member in the group (if any) for the other members of the group. By default | |
143 # all members of a group must be documented explicitly. | |
144 | |
145 DISTRIBUTE_GROUP_DOC = NO | |
146 | |
12800 | 147 # If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce |
148 # a new page for each member. If set to NO, the documentation of a member will | |
149 # be part of the file/class/namespace that contains it. | |
150 | |
151 SEPARATE_MEMBER_PAGES = NO | |
152 | |
7806 | 153 # The TAB_SIZE tag can be used to set the number of spaces in a tab. |
154 # Doxygen uses this value to replace tabs by spaces in code fragments. | |
155 | |
156 TAB_SIZE = 4 | |
157 | |
158 # This tag can be used to specify a number of aliases that acts | |
159 # as commands in the documentation. An alias has the form "name=value". | |
160 # For example adding "sideeffect=\par Side Effects:\n" will allow you to | |
161 # put the command \sideeffect (or @sideeffect) in the documentation, which | |
162 # will result in a user-defined paragraph with heading "Side Effects:". | |
163 # You can put \n's in the value part of an alias to insert newlines. | |
164 | |
165 ALIASES = "signal=- @ref" \ | |
11148
be0f164eabc6
[gaim-migrate @ 13227]
Gary Kramlich <grim@reaperworld.com>
parents:
10925
diff
changeset
|
166 "signaldef=@section" \ |
be0f164eabc6
[gaim-migrate @ 13227]
Gary Kramlich <grim@reaperworld.com>
parents:
10925
diff
changeset
|
167 "endsignaldef=" \ |
be0f164eabc6
[gaim-migrate @ 13227]
Gary Kramlich <grim@reaperworld.com>
parents:
10925
diff
changeset
|
168 "signalproto=@code" \ |
be0f164eabc6
[gaim-migrate @ 13227]
Gary Kramlich <grim@reaperworld.com>
parents:
10925
diff
changeset
|
169 "endsignalproto=@endcode" \ |
be0f164eabc6
[gaim-migrate @ 13227]
Gary Kramlich <grim@reaperworld.com>
parents:
10925
diff
changeset
|
170 "signaldesc=@par Description:" \ |
be0f164eabc6
[gaim-migrate @ 13227]
Gary Kramlich <grim@reaperworld.com>
parents:
10925
diff
changeset
|
171 "signals=@b Signals:" \ |
be0f164eabc6
[gaim-migrate @ 13227]
Gary Kramlich <grim@reaperworld.com>
parents:
10925
diff
changeset
|
172 "endsignals=" |
7806 | 173 |
174 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources | |
175 # only. Doxygen will then generate output that is more tailored for C. | |
176 # For instance, some of the names that are used will be different. The list | |
177 # of all members will be omitted, etc. | |
178 | |
179 OPTIMIZE_OUTPUT_FOR_C = YES | |
180 | |
181 # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources | |
182 # only. Doxygen will then generate output that is more tailored for Java. | |
183 # For instance, namespaces will be presented as packages, qualified scopes | |
184 # will look different, etc. | |
185 | |
186 OPTIMIZE_OUTPUT_JAVA = NO | |
187 | |
188 # Set the SUBGROUPING tag to YES (the default) to allow class member groups of | |
189 # the same type (for instance a group of public functions) to be put as a | |
190 # subgroup of that type (e.g. under the Public Functions section). Set it to | |
191 # NO to prevent subgrouping. Alternatively, this can be done per class using | |
192 # the \nosubgrouping command. | |
193 | |
194 SUBGROUPING = YES | |
195 | |
196 #--------------------------------------------------------------------------- | |
197 # Build related configuration options | |
198 #--------------------------------------------------------------------------- | |
199 | |
4554 | 200 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in |
201 # documentation are documented, even if no documentation was available. | |
202 # Private class members and static file members will be hidden unless | |
203 # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES | |
204 | |
205 EXTRACT_ALL = NO | |
206 | |
207 # If the EXTRACT_PRIVATE tag is set to YES all private members of a class | |
208 # will be included in the documentation. | |
209 | |
210 EXTRACT_PRIVATE = NO | |
211 | |
212 # If the EXTRACT_STATIC tag is set to YES all static members of a file | |
213 # will be included in the documentation. | |
214 | |
215 EXTRACT_STATIC = NO | |
216 | |
217 # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) | |
218 # defined locally in source files will be included in the documentation. | |
219 # If set to NO only classes defined in header files are included. | |
220 | |
221 EXTRACT_LOCAL_CLASSES = YES | |
222 | |
12800 | 223 # This flag is only useful for Objective-C code. When set to YES local |
224 # methods, which are defined in the implementation section but not in | |
225 # the interface are included in the documentation. | |
226 # If set to NO (the default) only methods in the interface are included. | |
227 | |
228 EXTRACT_LOCAL_METHODS = YES | |
229 | |
4554 | 230 # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all |
231 # undocumented members of documented classes, files or namespaces. | |
232 # If set to NO (the default) these members will be included in the | |
233 # various overviews, but no documentation section is generated. | |
234 # This option has no effect if EXTRACT_ALL is enabled. | |
235 | |
236 HIDE_UNDOC_MEMBERS = NO | |
237 | |
238 # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all | |
239 # undocumented classes that are normally visible in the class hierarchy. | |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
240 # If set to NO (the default) these classes will be included in the various |
4554 | 241 # overviews. This option has no effect if EXTRACT_ALL is enabled. |
242 | |
243 HIDE_UNDOC_CLASSES = NO | |
244 | |
245 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all | |
246 # friend (class|struct|union) declarations. | |
247 # If set to NO (the default) these declarations will be included in the | |
248 # documentation. | |
249 | |
250 HIDE_FRIEND_COMPOUNDS = NO | |
251 | |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
252 # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
253 # documentation blocks found inside the body of a function. |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
254 # If set to NO (the default) these blocks will be appended to the |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
255 # function's detailed documentation block. |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
256 |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
257 HIDE_IN_BODY_DOCS = NO |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
258 |
4554 | 259 # The INTERNAL_DOCS tag determines if documentation |
260 # that is typed after a \internal command is included. If the tag is set | |
261 # to NO (the default) then the documentation will be excluded. | |
262 # Set it to YES to include the internal documentation. | |
263 | |
264 INTERNAL_DOCS = NO | |
265 | |
266 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate | |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
267 # file names in lower-case letters. If set to YES upper-case letters are also |
4554 | 268 # allowed. This is useful if you have classes or files whose names only differ |
269 # in case and if your file system supports case sensitive file names. Windows | |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
270 # users are advised to set this option to NO. |
4554 | 271 |
272 CASE_SENSE_NAMES = YES | |
273 | |
274 # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen | |
275 # will show members with their full class and namespace scopes in the | |
276 # documentation. If set to YES the scope will be hidden. | |
277 | |
278 HIDE_SCOPE_NAMES = NO | |
279 | |
280 # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen | |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
281 # will put a list of the files that are included by a file in the documentation |
4554 | 282 # of that file. |
283 | |
284 SHOW_INCLUDE_FILES = YES | |
285 | |
286 # If the INLINE_INFO tag is set to YES (the default) then a tag [inline] | |
287 # is inserted in the documentation for inline members. | |
288 | |
289 INLINE_INFO = YES | |
290 | |
291 # If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen | |
292 # will sort the (detailed) documentation of file and class members | |
293 # alphabetically by member name. If set to NO the members will appear in | |
294 # declaration order. | |
295 | |
296 SORT_MEMBER_DOCS = YES | |
297 | |
12800 | 298 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the |
299 # brief documentation of file, namespace and class members alphabetically | |
300 # by member name. If set to NO (the default) the members will appear in | |
301 # declaration order. | |
302 | |
303 SORT_BRIEF_DOCS = YES | |
304 | |
305 # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be | |
306 # sorted by fully-qualified names, including namespaces. If set to | |
307 # NO (the default), the class list will be sorted only by class name, | |
308 # not including the namespace part. | |
309 # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. | |
310 # Note: This option applies only to the class list, not to the | |
311 # alphabetical list. | |
312 | |
313 SORT_BY_SCOPE_NAME = YES | |
314 | |
4554 | 315 # The GENERATE_TODOLIST tag can be used to enable (YES) or |
316 # disable (NO) the todo list. This list is created by putting \todo | |
317 # commands in the documentation. | |
318 | |
319 GENERATE_TODOLIST = YES | |
320 | |
321 # The GENERATE_TESTLIST tag can be used to enable (YES) or | |
322 # disable (NO) the test list. This list is created by putting \test | |
323 # commands in the documentation. | |
324 | |
325 GENERATE_TESTLIST = YES | |
326 | |
327 # The GENERATE_BUGLIST tag can be used to enable (YES) or | |
328 # disable (NO) the bug list. This list is created by putting \bug | |
329 # commands in the documentation. | |
330 | |
331 GENERATE_BUGLIST = YES | |
332 | |
333 # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or | |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
334 # disable (NO) the deprecated list. This list is created by putting |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
335 # \deprecated commands in the documentation. |
4554 | 336 |
337 GENERATE_DEPRECATEDLIST= YES | |
338 | |
339 # The ENABLED_SECTIONS tag can be used to enable conditional | |
340 # documentation sections, marked by \if sectionname ... \endif. | |
341 | |
342 ENABLED_SECTIONS = | |
343 | |
344 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines | |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
345 # the initial value of a variable or define consists of for it to appear in |
4554 | 346 # the documentation. If the initializer consists of more lines than specified |
347 # here it will be hidden. Use a value of 0 to hide initializers completely. | |
348 # The appearance of the initializer of individual variables and defines in the | |
349 # documentation can be controlled using \showinitializer or \hideinitializer | |
350 # command in the documentation regardless of this setting. | |
351 | |
352 MAX_INITIALIZER_LINES = 30 | |
353 | |
354 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated | |
355 # at the bottom of the documentation of classes and structs. If set to YES the | |
356 # list will mention the files that were used to generate the documentation. | |
357 | |
358 SHOW_USED_FILES = YES | |
359 | |
12800 | 360 # If the sources in your project are distributed over multiple directories |
361 # then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy | |
362 # in the documentation. The default is YES. | |
363 | |
364 SHOW_DIRECTORIES = YES | |
365 | |
366 # The FILE_VERSION_FILTER tag can be used to specify a program or script that | |
367 # doxygen should invoke to get the current version for each file (typically from the | |
368 # version control system). Doxygen will invoke the program by executing (via | |
369 # popen()) the command <command> <input-file>, where <command> is the value of | |
370 # the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file | |
371 # provided by doxygen. Whatever the progam writes to standard output | |
372 # is used as the file version. See the manual for examples. | |
373 | |
374 FILE_VERSION_FILTER = | |
375 | |
4554 | 376 #--------------------------------------------------------------------------- |
377 # configuration options related to warning and progress messages | |
378 #--------------------------------------------------------------------------- | |
379 | |
380 # The QUIET tag can be used to turn on/off the messages that are generated | |
381 # by doxygen. Possible values are YES and NO. If left blank NO is used. | |
382 | |
383 QUIET = NO | |
384 | |
385 # The WARNINGS tag can be used to turn on/off the warning messages that are | |
386 # generated by doxygen. Possible values are YES and NO. If left blank | |
387 # NO is used. | |
388 | |
389 WARNINGS = YES | |
390 | |
391 # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings | |
392 # for undocumented members. If EXTRACT_ALL is set to YES then this flag will | |
393 # automatically be disabled. | |
394 | |
395 WARN_IF_UNDOCUMENTED = NO | |
396 | |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
397 # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
398 # potential errors in the documentation, such as not documenting some |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
399 # parameters in a documented function, or documenting parameters that |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
400 # don't exist or using markup commands wrongly. |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
401 |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
402 WARN_IF_DOC_ERROR = YES |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
403 |
12800 | 404 # This WARN_NO_PARAMDOC option can be abled to get warnings for |
405 # functions that are documented, but have no documentation for their parameters | |
406 # or return value. If set to NO (the default) doxygen will only warn about | |
407 # wrong or incomplete parameter documentation, but not about the absence of | |
408 # documentation. | |
409 | |
410 WARN_NO_PARAMDOC = YES | |
411 | |
4554 | 412 # The WARN_FORMAT tag determines the format of the warning messages that |
413 # doxygen can produce. The string should contain the $file, $line, and $text | |
414 # tags, which will be replaced by the file and line number from which the | |
415 # warning originated and the warning text. | |
416 | |
417 WARN_FORMAT = "$file:$line: $text" | |
418 | |
419 # The WARN_LOGFILE tag can be used to specify a file to which warning | |
420 # and error messages should be written. If left blank the output is written | |
421 # to stderr. | |
422 | |
423 WARN_LOGFILE = | |
424 | |
425 #--------------------------------------------------------------------------- | |
426 # configuration options related to the input files | |
427 #--------------------------------------------------------------------------- | |
428 | |
429 # The INPUT tag can be used to specify the files and/or directories that contain | |
430 # documented source files. You may enter file names like "myfile.cpp" or | |
431 # directories like "/usr/src/myproject". Separate the files or directories | |
432 # with spaces. | |
433 | |
15936
b449dc6b8a20
A little doxygen love and some tiny gaim->purpleisms
Mark Doliner <mark@kingant.net>
parents:
14553
diff
changeset
|
434 INPUT = libpurple \ |
b449dc6b8a20
A little doxygen love and some tiny gaim->purpleisms
Mark Doliner <mark@kingant.net>
parents:
14553
diff
changeset
|
435 finch \ |
b449dc6b8a20
A little doxygen love and some tiny gaim->purpleisms
Mark Doliner <mark@kingant.net>
parents:
14553
diff
changeset
|
436 pidgin \ |
7806 | 437 doc |
4554 | 438 |
439 # If the value of the INPUT tag contains directories, you can use the | |
440 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp | |
441 # and *.h) to filter out the source-files in the directories. If left | |
442 # blank the following patterns are tested: | |
443 # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp | |
7806 | 444 # *.h++ *.idl *.odl *.cs *.php *.php3 *.inc |
4554 | 445 |
7806 | 446 FILE_PATTERNS = *.h \ |
447 *.dox | |
4554 | 448 |
449 # The RECURSIVE tag can be used to turn specify whether or not subdirectories | |
450 # should be searched for input files as well. Possible values are YES and NO. | |
451 # If left blank NO is used. | |
452 | |
453 RECURSIVE = NO | |
454 | |
455 # The EXCLUDE tag can be used to specify files and/or directories that should | |
456 # excluded from the INPUT source files. This way you can easily exclude a | |
457 # subdirectory from a directory tree whose root is specified with the INPUT tag. | |
458 | |
459 EXCLUDE = | |
460 | |
461 # The EXCLUDE_SYMLINKS tag can be used select whether or not files or directories | |
462 # that are symbolic links (a Unix filesystem feature) are excluded from the input. | |
463 | |
464 EXCLUDE_SYMLINKS = NO | |
465 | |
466 # If the value of the INPUT tag contains directories, you can use the | |
467 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude | |
468 # certain files from those directories. | |
469 | |
470 EXCLUDE_PATTERNS = | |
471 | |
472 # The EXAMPLE_PATH tag can be used to specify one or more files or | |
473 # directories that contain example code fragments that are included (see | |
474 # the \include command). | |
475 | |
476 EXAMPLE_PATH = | |
477 | |
478 # If the value of the EXAMPLE_PATH tag contains directories, you can use the | |
479 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp | |
480 # and *.h) to filter out the source-files in the directories. If left | |
481 # blank all files are included. | |
482 | |
483 EXAMPLE_PATTERNS = | |
484 | |
485 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be | |
486 # searched for input files to be used with the \include or \dontinclude | |
487 # commands irrespective of the value of the RECURSIVE tag. | |
488 # Possible values are YES and NO. If left blank NO is used. | |
489 | |
490 EXAMPLE_RECURSIVE = NO | |
491 | |
492 # The IMAGE_PATH tag can be used to specify one or more files or | |
493 # directories that contain image that are included in the documentation (see | |
494 # the \image command). | |
495 | |
496 IMAGE_PATH = | |
497 | |
498 # The INPUT_FILTER tag can be used to specify a program that doxygen should | |
499 # invoke to filter for each input file. Doxygen will invoke the filter program | |
500 # by executing (via popen()) the command <filter> <input-file>, where <filter> | |
501 # is the value of the INPUT_FILTER tag, and <input-file> is the name of an | |
502 # input file. Doxygen will then use the output that the filter program writes | |
503 # to standard output. | |
504 | |
505 INPUT_FILTER = | |
506 | |
12800 | 507 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern |
508 # basis. Doxygen will compare the file name with each pattern and apply the | |
509 # filter if there is a match. The filters are a list of the form: | |
510 # pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further | |
511 # info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER | |
512 # is applied to all files. | |
513 | |
514 FILTER_PATTERNS = | |
515 | |
4554 | 516 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using |
517 # INPUT_FILTER) will be used to filter the input files when producing source | |
518 # files to browse (i.e. when SOURCE_BROWSER is set to YES). | |
519 | |
520 FILTER_SOURCE_FILES = NO | |
521 | |
522 #--------------------------------------------------------------------------- | |
523 # configuration options related to source browsing | |
524 #--------------------------------------------------------------------------- | |
525 | |
526 # If the SOURCE_BROWSER tag is set to YES then a list of source files will | |
527 # be generated. Documented entities will be cross-referenced with these sources. | |
528 | |
529 SOURCE_BROWSER = NO | |
530 | |
531 # Setting the INLINE_SOURCES tag to YES will include the body | |
532 # of functions and classes directly in the documentation. | |
533 | |
534 INLINE_SOURCES = NO | |
535 | |
536 # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct | |
537 # doxygen to hide any special comment blocks from generated source code | |
538 # fragments. Normal C and C++ comments will always remain visible. | |
539 | |
540 STRIP_CODE_COMMENTS = YES | |
541 | |
542 # If the REFERENCED_BY_RELATION tag is set to YES (the default) | |
543 # then for each documented function all documented | |
544 # functions referencing it will be listed. | |
545 | |
546 REFERENCED_BY_RELATION = YES | |
547 | |
548 # If the REFERENCES_RELATION tag is set to YES (the default) | |
549 # then for each documented function all documented entities | |
550 # called/used by that function will be listed. | |
551 | |
552 REFERENCES_RELATION = YES | |
553 | |
12800 | 554 # If the USE_HTAGS tag is set to YES then the references to source code |
555 # will point to the HTML generated by the htags(1) tool instead of doxygen | |
556 # built-in source browser. The htags tool is part of GNU's global source | |
557 # tagging system (see http://www.gnu.org/software/global/global.html). You | |
558 # will need version 4.8.6 or higher. | |
559 | |
560 USE_HTAGS = NO | |
561 | |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
562 # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
563 # will generate a verbatim copy of the header file for each class for |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
564 # which an include is specified. Set to NO to disable this. |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
565 |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
566 VERBATIM_HEADERS = YES |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
567 |
4554 | 568 #--------------------------------------------------------------------------- |
569 # configuration options related to the alphabetical class index | |
570 #--------------------------------------------------------------------------- | |
571 | |
572 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index | |
573 # of all compounds will be generated. Enable this if the project | |
574 # contains a lot of classes, structs, unions or interfaces. | |
575 | |
7336
ef6a33dcd0dd
[gaim-migrate @ 7924]
Christian Hammond <chipx86@chipx86.com>
parents:
6720
diff
changeset
|
576 ALPHABETICAL_INDEX = YES |
4554 | 577 |
578 # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then | |
579 # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns | |
580 # in which this list will be split (can be a number in the range [1..20]) | |
581 | |
7337
32800d26dc68
[gaim-migrate @ 7925]
Christian Hammond <chipx86@chipx86.com>
parents:
7336
diff
changeset
|
582 COLS_IN_ALPHA_INDEX = 3 |
4554 | 583 |
584 # In case all classes in a project start with a common prefix, all | |
585 # classes will be put under the same header in the alphabetical index. | |
586 # The IGNORE_PREFIX tag can be used to specify one or more prefixes that | |
587 # should be ignored while generating the index headers. | |
588 | |
15936
b449dc6b8a20
A little doxygen love and some tiny gaim->purpleisms
Mark Doliner <mark@kingant.net>
parents:
14553
diff
changeset
|
589 IGNORE_PREFIX = Purple \ |
b449dc6b8a20
A little doxygen love and some tiny gaim->purpleisms
Mark Doliner <mark@kingant.net>
parents:
14553
diff
changeset
|
590 _Purple \ |
b449dc6b8a20
A little doxygen love and some tiny gaim->purpleisms
Mark Doliner <mark@kingant.net>
parents:
14553
diff
changeset
|
591 purple |
4554 | 592 |
593 #--------------------------------------------------------------------------- | |
594 # configuration options related to the HTML output | |
595 #--------------------------------------------------------------------------- | |
596 | |
597 # If the GENERATE_HTML tag is set to YES (the default) Doxygen will | |
598 # generate HTML output. | |
599 | |
600 GENERATE_HTML = YES | |
601 | |
602 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. | |
603 # If a relative path is entered the value of OUTPUT_DIRECTORY will be | |
604 # put in front of it. If left blank `html' will be used as the default path. | |
605 | |
606 HTML_OUTPUT = html | |
607 | |
608 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for | |
609 # each generated HTML page (for example: .htm,.php,.asp). If it is left blank | |
610 # doxygen will generate files with .html extension. | |
611 | |
612 HTML_FILE_EXTENSION = .html | |
613 | |
614 # The HTML_HEADER tag can be used to specify a personal HTML header for | |
615 # each generated HTML page. If it is left blank doxygen will generate a | |
616 # standard header. | |
617 | |
16257
b20fa7ebb911
Ari sent in a patch, saying:
Richard Laager <rlaager@wiktel.com>
parents:
16048
diff
changeset
|
618 HTML_HEADER = @top_srcdir@/doc/TracHeader.html |
4554 | 619 |
620 # The HTML_FOOTER tag can be used to specify a personal HTML footer for | |
621 # each generated HTML page. If it is left blank doxygen will generate a | |
622 # standard footer. | |
623 | |
16257
b20fa7ebb911
Ari sent in a patch, saying:
Richard Laager <rlaager@wiktel.com>
parents:
16048
diff
changeset
|
624 HTML_FOOTER = @top_srcdir@/doc/TracFooter.html |
4554 | 625 |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
626 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading |
4554 | 627 # style sheet that is used by each HTML page. It can be used to |
628 # fine-tune the look of the HTML output. If the tag is left blank doxygen | |
629 # will generate a default style sheet | |
630 | |
631 HTML_STYLESHEET = | |
632 | |
633 # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, | |
634 # files or namespaces will be aligned in HTML using tables. If set to | |
635 # NO a bullet list will be used. | |
636 | |
637 HTML_ALIGN_MEMBERS = YES | |
638 | |
639 # If the GENERATE_HTMLHELP tag is set to YES, additional index files | |
640 # will be generated that can be used as input for tools like the | |
641 # Microsoft HTML help workshop to generate a compressed HTML help file (.chm) | |
642 # of the generated HTML documentation. | |
643 | |
12800 | 644 GENERATE_HTMLHELP = YES |
4554 | 645 |
646 # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can | |
647 # be used to specify the file name of the resulting .chm file. You | |
648 # can add a path in front of the file if the result should not be | |
649 # written to the html output dir. | |
650 | |
651 CHM_FILE = | |
652 | |
653 # If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can | |
654 # be used to specify the location (absolute path including file name) of | |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
655 # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
656 # the HTML help compiler on the generated index.hhp. |
4554 | 657 |
658 HHC_LOCATION = | |
659 | |
660 # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag | |
661 # controls if a separate .chi index file is generated (YES) or that | |
662 # it should be included in the master .chm file (NO). | |
663 | |
664 GENERATE_CHI = NO | |
665 | |
666 # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag | |
667 # controls whether a binary table of contents is generated (YES) or a | |
668 # normal table of contents (NO) in the .chm file. | |
669 | |
670 BINARY_TOC = NO | |
671 | |
672 # The TOC_EXPAND flag can be set to YES to add extra items for group members | |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
673 # to the contents of the HTML help documentation and to the tree view. |
4554 | 674 |
12800 | 675 TOC_EXPAND = YES |
4554 | 676 |
677 # The DISABLE_INDEX tag can be used to turn on/off the condensed index at | |
678 # top of each HTML page. The value NO (the default) enables the index and | |
679 # the value YES disables it. | |
680 | |
681 DISABLE_INDEX = NO | |
682 | |
683 # This tag can be used to set the number of enum values (range [1..20]) | |
684 # that doxygen will group on one line in the generated HTML documentation. | |
685 | |
686 ENUM_VALUES_PER_LINE = 4 | |
687 | |
688 # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be | |
689 # generated containing a tree-like index structure (just like the one that | |
690 # is generated for HTML Help). For this to work a browser that supports | |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
691 # JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+, |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
692 # Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
693 # probably better off using the HTML help feature. |
4554 | 694 |
12800 | 695 GENERATE_TREEVIEW = YES |
4554 | 696 |
697 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be | |
698 # used to set the initial width (in pixels) of the frame in which the tree | |
699 # is shown. | |
700 | |
701 TREEVIEW_WIDTH = 250 | |
702 | |
703 #--------------------------------------------------------------------------- | |
704 # configuration options related to the LaTeX output | |
705 #--------------------------------------------------------------------------- | |
706 | |
707 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will | |
708 # generate Latex output. | |
709 | |
710 GENERATE_LATEX = NO | |
711 | |
712 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. | |
713 # If a relative path is entered the value of OUTPUT_DIRECTORY will be | |
714 # put in front of it. If left blank `latex' will be used as the default path. | |
715 | |
716 LATEX_OUTPUT = latex | |
717 | |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
718 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
719 # invoked. If left blank `latex' will be used as the default command name. |
4554 | 720 |
721 LATEX_CMD_NAME = latex | |
722 | |
723 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to | |
724 # generate index for LaTeX. If left blank `makeindex' will be used as the | |
725 # default command name. | |
726 | |
727 MAKEINDEX_CMD_NAME = makeindex | |
728 | |
729 # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact | |
730 # LaTeX documents. This may be useful for small projects and may help to | |
731 # save some trees in general. | |
732 | |
733 COMPACT_LATEX = NO | |
734 | |
735 # The PAPER_TYPE tag can be used to set the paper type that is used | |
736 # by the printer. Possible values are: a4, a4wide, letter, legal and | |
737 # executive. If left blank a4wide will be used. | |
738 | |
739 PAPER_TYPE = a4wide | |
740 | |
741 # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX | |
742 # packages that should be included in the LaTeX output. | |
743 | |
744 EXTRA_PACKAGES = | |
745 | |
746 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for | |
747 # the generated latex document. The header should contain everything until | |
748 # the first chapter. If it is left blank doxygen will generate a | |
749 # standard header. Notice: only use this tag if you know what you are doing! | |
750 | |
751 LATEX_HEADER = | |
752 | |
753 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated | |
754 # is prepared for conversion to pdf (using ps2pdf). The pdf file will | |
755 # contain links (just like the HTML output) instead of page references | |
756 # This makes the output suitable for online browsing using a pdf viewer. | |
757 | |
758 PDF_HYPERLINKS = NO | |
759 | |
760 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of | |
761 # plain latex in the generated Makefile. Set this option to YES to get a | |
762 # higher quality PDF documentation. | |
763 | |
764 USE_PDFLATEX = NO | |
765 | |
766 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. | |
767 # command to the generated LaTeX files. This will instruct LaTeX to keep | |
768 # running if errors occur, instead of asking the user for help. | |
769 # This option is also used when generating formulas in HTML. | |
770 | |
771 LATEX_BATCHMODE = NO | |
772 | |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
773 # If LATEX_HIDE_INDICES is set to YES then doxygen will not |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
774 # include the index chapters (such as File Index, Compound Index, etc.) |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
775 # in the output. |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
776 |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
777 LATEX_HIDE_INDICES = NO |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
778 |
4554 | 779 #--------------------------------------------------------------------------- |
780 # configuration options related to the RTF output | |
781 #--------------------------------------------------------------------------- | |
782 | |
783 # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output | |
784 # The RTF output is optimised for Word 97 and may not look very pretty with | |
785 # other RTF readers or editors. | |
786 | |
787 GENERATE_RTF = NO | |
788 | |
789 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. | |
790 # If a relative path is entered the value of OUTPUT_DIRECTORY will be | |
791 # put in front of it. If left blank `rtf' will be used as the default path. | |
792 | |
793 RTF_OUTPUT = rtf | |
794 | |
795 # If the COMPACT_RTF tag is set to YES Doxygen generates more compact | |
796 # RTF documents. This may be useful for small projects and may help to | |
797 # save some trees in general. | |
798 | |
799 COMPACT_RTF = NO | |
800 | |
801 # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated | |
802 # will contain hyperlink fields. The RTF file will | |
803 # contain links (just like the HTML output) instead of page references. | |
804 # This makes the output suitable for online browsing using WORD or other | |
805 # programs which support those fields. | |
806 # Note: wordpad (write) and others do not support links. | |
807 | |
808 RTF_HYPERLINKS = NO | |
809 | |
810 # Load stylesheet definitions from file. Syntax is similar to doxygen's | |
811 # config file, i.e. a series of assigments. You only have to provide | |
812 # replacements, missing definitions are set to their default value. | |
813 | |
814 RTF_STYLESHEET_FILE = | |
815 | |
816 # Set optional variables used in the generation of an rtf document. | |
817 # Syntax is similar to doxygen's config file. | |
818 | |
819 RTF_EXTENSIONS_FILE = | |
820 | |
821 #--------------------------------------------------------------------------- | |
822 # configuration options related to the man page output | |
823 #--------------------------------------------------------------------------- | |
824 | |
825 # If the GENERATE_MAN tag is set to YES (the default) Doxygen will | |
826 # generate man pages | |
827 | |
828 GENERATE_MAN = NO | |
829 | |
830 # The MAN_OUTPUT tag is used to specify where the man pages will be put. | |
831 # If a relative path is entered the value of OUTPUT_DIRECTORY will be | |
832 # put in front of it. If left blank `man' will be used as the default path. | |
833 | |
834 MAN_OUTPUT = man | |
835 | |
836 # The MAN_EXTENSION tag determines the extension that is added to | |
837 # the generated man pages (default is the subroutine's section .3) | |
838 | |
839 MAN_EXTENSION = .3 | |
840 | |
841 # If the MAN_LINKS tag is set to YES and Doxygen generates man output, | |
842 # then it will generate one additional man file for each entity | |
843 # documented in the real man page(s). These additional files | |
844 # only source the real man page, but without them the man command | |
845 # would be unable to find the correct page. The default is NO. | |
846 | |
847 MAN_LINKS = NO | |
848 | |
849 #--------------------------------------------------------------------------- | |
850 # configuration options related to the XML output | |
851 #--------------------------------------------------------------------------- | |
852 | |
853 # If the GENERATE_XML tag is set to YES Doxygen will | |
854 # generate an XML file that captures the structure of | |
855 # the code including all documentation. Note that this | |
856 # feature is still experimental and incomplete at the | |
857 # moment. | |
858 | |
859 GENERATE_XML = NO | |
860 | |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
861 # The XML_OUTPUT tag is used to specify where the XML pages will be put. |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
862 # If a relative path is entered the value of OUTPUT_DIRECTORY will be |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
863 # put in front of it. If left blank `xml' will be used as the default path. |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
864 |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
865 XML_OUTPUT = xml |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
866 |
4554 | 867 # The XML_SCHEMA tag can be used to specify an XML schema, |
868 # which can be used by a validating XML parser to check the | |
869 # syntax of the XML files. | |
870 | |
871 XML_SCHEMA = | |
872 | |
873 # The XML_DTD tag can be used to specify an XML DTD, | |
874 # which can be used by a validating XML parser to check the | |
875 # syntax of the XML files. | |
876 | |
877 XML_DTD = | |
878 | |
879 #--------------------------------------------------------------------------- | |
880 # configuration options for the AutoGen Definitions output | |
881 #--------------------------------------------------------------------------- | |
882 | |
883 # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will | |
884 # generate an AutoGen Definitions (see autogen.sf.net) file | |
885 # that captures the structure of the code including all | |
886 # documentation. Note that this feature is still experimental | |
887 # and incomplete at the moment. | |
888 | |
889 GENERATE_AUTOGEN_DEF = NO | |
890 | |
891 #--------------------------------------------------------------------------- | |
892 # configuration options related to the Perl module output | |
893 #--------------------------------------------------------------------------- | |
894 | |
895 # If the GENERATE_PERLMOD tag is set to YES Doxygen will | |
896 # generate a Perl module file that captures the structure of | |
897 # the code including all documentation. Note that this | |
898 # feature is still experimental and incomplete at the | |
899 # moment. | |
900 | |
901 GENERATE_PERLMOD = NO | |
902 | |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
903 # If the PERLMOD_LATEX tag is set to YES Doxygen will generate |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
904 # the necessary Makefile rules, Perl scripts and LaTeX code to be able |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
905 # to generate PDF and DVI output from the Perl module output. |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
906 |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
907 PERLMOD_LATEX = NO |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
908 |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
909 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
910 # nicely formatted so it can be parsed by a human reader. This is useful |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
911 # if you want to understand what is going on. On the other hand, if this |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
912 # tag is set to NO the size of the Perl module output will be much smaller |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
913 # and Perl will parse it just the same. |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
914 |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
915 PERLMOD_PRETTY = YES |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
916 |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
917 # The names of the make variables in the generated doxyrules.make file |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
918 # are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
919 # This is useful so different doxyrules.make files included by the same |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
920 # Makefile don't overwrite each other's variables. |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
921 |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
922 PERLMOD_MAKEVAR_PREFIX = |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
923 |
4554 | 924 #--------------------------------------------------------------------------- |
925 # Configuration options related to the preprocessor | |
926 #--------------------------------------------------------------------------- | |
927 | |
928 # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will | |
929 # evaluate all C-preprocessor directives found in the sources and include | |
930 # files. | |
931 | |
932 ENABLE_PREPROCESSING = YES | |
933 | |
934 # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro | |
935 # names in the source code. If set to NO (the default) only conditional | |
936 # compilation will be performed. Macro expansion can be done in a controlled | |
937 # way by setting EXPAND_ONLY_PREDEF to YES. | |
938 | |
939 MACRO_EXPANSION = NO | |
940 | |
941 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES | |
942 # then the macro expansion is limited to the macros specified with the | |
943 # PREDEFINED and EXPAND_AS_PREDEFINED tags. | |
944 | |
945 EXPAND_ONLY_PREDEF = NO | |
946 | |
947 # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files | |
948 # in the INCLUDE_PATH (see below) will be search if a #include is found. | |
949 | |
950 SEARCH_INCLUDES = YES | |
951 | |
952 # The INCLUDE_PATH tag can be used to specify one or more directories that | |
953 # contain include files that are not input files but should be processed by | |
954 # the preprocessor. | |
955 | |
956 INCLUDE_PATH = | |
957 | |
958 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard | |
959 # patterns (like *.h and *.hpp) to filter out the header-files in the | |
960 # directories. If left blank, the patterns specified with FILE_PATTERNS will | |
961 # be used. | |
962 | |
963 INCLUDE_FILE_PATTERNS = | |
964 | |
965 # The PREDEFINED tag can be used to specify one or more macro names that | |
966 # are defined before the preprocessor is started (similar to the -D option of | |
967 # gcc). The argument of the tag is a list of macros of the form: name | |
968 # or name=definition (no spaces). If the definition and the = are | |
969 # omitted =1 is assumed. | |
970 | |
971 PREDEFINED = | |
972 | |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
973 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then |
4554 | 974 # this tag can be used to specify a list of macro names that should be expanded. |
975 # The macro definition that is found in the sources will be used. | |
976 # Use the PREDEFINED tag if you want to use a different macro definition. | |
977 | |
978 EXPAND_AS_DEFINED = | |
979 | |
980 # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then | |
981 # doxygen's preprocessor will remove all function-like macros that are alone | |
982 # on a line, have an all uppercase name, and do not end with a semicolon. Such | |
983 # function macros are typically used for boiler-plate code, and will confuse the | |
984 # parser if not removed. | |
985 | |
986 SKIP_FUNCTION_MACROS = YES | |
987 | |
988 #--------------------------------------------------------------------------- | |
989 # Configuration::addtions related to external references | |
990 #--------------------------------------------------------------------------- | |
991 | |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
992 # The TAGFILES option can be used to specify one or more tagfiles. |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
993 # Optionally an initial location of the external documentation |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
994 # can be added for each tagfile. The format of a tag file without |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
995 # this location is as follows: |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
996 # TAGFILES = file1 file2 ... |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
997 # Adding location for the tag files is done as follows: |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
998 # TAGFILES = file1=loc1 "file2 = loc2" ... |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
999 # where "loc1" and "loc2" can be relative or absolute paths or |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1000 # URLs. If a location is present for each tag, the installdox tool |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1001 # does not have to be run to correct the links. |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1002 # Note that each tag file must have a unique name |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1003 # (where the name does NOT include the path) |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1004 # If a tag file is not located in the directory in which doxygen |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1005 # is run, you must also specify the path to the tagfile here. |
4554 | 1006 |
1007 TAGFILES = | |
1008 | |
1009 # When a file name is specified after GENERATE_TAGFILE, doxygen will create | |
1010 # a tag file that is based on the input files it reads. | |
1011 | |
1012 GENERATE_TAGFILE = | |
1013 | |
1014 # If the ALLEXTERNALS tag is set to YES all external classes will be listed | |
1015 # in the class index. If set to NO only the inherited external classes | |
1016 # will be listed. | |
1017 | |
1018 ALLEXTERNALS = NO | |
1019 | |
1020 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed | |
1021 # in the modules index. If set to NO, only the current project's groups will | |
1022 # be listed. | |
1023 | |
1024 EXTERNAL_GROUPS = YES | |
1025 | |
1026 # The PERL_PATH should be the absolute path and name of the perl script | |
1027 # interpreter (i.e. the result of `which perl'). | |
1028 | |
1029 PERL_PATH = /usr/bin/perl | |
1030 | |
1031 #--------------------------------------------------------------------------- | |
1032 # Configuration options related to the dot tool | |
1033 #--------------------------------------------------------------------------- | |
1034 | |
1035 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will | |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1036 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base or |
4554 | 1037 # super classes. Setting the tag to NO turns the diagrams off. Note that this |
1038 # option is superceded by the HAVE_DOT option below. This is only a fallback. It is | |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1039 # recommended to install and use dot, since it yields more powerful graphs. |
4554 | 1040 |
1041 CLASS_DIAGRAMS = YES | |
1042 | |
1043 # If set to YES, the inheritance and collaboration graphs will hide | |
1044 # inheritance and usage relations if the target is undocumented | |
1045 # or is not a class. | |
1046 | |
1047 HIDE_UNDOC_RELATIONS = YES | |
1048 | |
1049 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is | |
1050 # available from the path. This tool is part of Graphviz, a graph visualization | |
1051 # toolkit from AT&T and Lucent Bell Labs. The other options in this section | |
1052 # have no effect if this option is set to NO (the default) | |
1053 | |
10925
993db24dae16
[gaim-migrate @ 12696]
Gary Kramlich <grim@reaperworld.com>
parents:
7806
diff
changeset
|
1054 HAVE_DOT = @enable_dot@ |
4554 | 1055 |
1056 # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen | |
1057 # will generate a graph for each documented class showing the direct and | |
1058 # indirect inheritance relations. Setting this tag to YES will force the | |
1059 # the CLASS_DIAGRAMS tag to NO. | |
1060 | |
1061 CLASS_GRAPH = YES | |
1062 | |
1063 # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen | |
1064 # will generate a graph for each documented class showing the direct and | |
1065 # indirect implementation dependencies (inheritance, containment, and | |
1066 # class references variables) of the class with other documented classes. | |
1067 | |
1068 COLLABORATION_GRAPH = YES | |
1069 | |
12800 | 1070 # If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen |
1071 # will generate a graph for groups, showing the direct groups dependencies | |
1072 | |
1073 GROUP_GRAPHS = YES | |
1074 | |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1075 # If the UML_LOOK tag is set to YES doxygen will generate inheritance and |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1076 # collaboration diagrams in a style similiar to the OMG's Unified Modeling |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1077 # Language. |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1078 |
12800 | 1079 UML_LOOK = YES |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1080 |
4554 | 1081 # If set to YES, the inheritance and collaboration graphs will show the |
1082 # relations between templates and their instances. | |
1083 | |
1084 TEMPLATE_RELATIONS = YES | |
1085 | |
1086 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT | |
1087 # tags are set to YES then doxygen will generate a graph for each documented | |
1088 # file showing the direct and indirect include dependencies of the file with | |
1089 # other documented files. | |
1090 | |
1091 INCLUDE_GRAPH = YES | |
1092 | |
1093 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and | |
1094 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each | |
1095 # documented header file showing the documented files that directly or | |
1096 # indirectly include this file. | |
1097 | |
1098 INCLUDED_BY_GRAPH = YES | |
1099 | |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1100 # If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1101 # generate a call dependency graph for every global function or class method. |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1102 # Note that enabling this option will significantly increase the time of a run. |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1103 # So in most cases it will be better to enable call graphs for selected |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1104 # functions only using the \callgraph command. |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1105 |
12800 | 1106 CALL_GRAPH = YES |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1107 |
4554 | 1108 # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen |
1109 # will graphical hierarchy of all classes instead of a textual one. | |
1110 | |
1111 GRAPHICAL_HIERARCHY = YES | |
1112 | |
12800 | 1113 # If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES |
1114 # then doxygen will show the dependencies a directory has on other directories | |
1115 # in a graphical way. The dependency relations are determined by the #include | |
1116 # relations between the files in the directories. | |
1117 | |
1118 DIRECTORY_GRAPH = YES | |
1119 | |
4554 | 1120 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images |
1121 # generated by dot. Possible values are png, jpg, or gif | |
1122 # If left blank png will be used. | |
1123 | |
1124 DOT_IMAGE_FORMAT = png | |
1125 | |
1126 # The tag DOT_PATH can be used to specify the path where the dot tool can be | |
1127 # found. If left blank, it is assumed the dot tool can be found on the path. | |
1128 | |
1129 DOT_PATH = | |
1130 | |
1131 # The DOTFILE_DIRS tag can be used to specify one or more directories that | |
1132 # contain dot files that are included in the documentation (see the | |
1133 # \dotfile command). | |
1134 | |
1135 DOTFILE_DIRS = | |
1136 | |
1137 # The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width | |
1138 # (in pixels) of the graphs generated by dot. If a graph becomes larger than | |
1139 # this value, doxygen will try to truncate the graph, so that it fits within | |
1140 # the specified constraint. Beware that most browsers cannot cope with very | |
1141 # large images. | |
1142 | |
1143 MAX_DOT_GRAPH_WIDTH = 1024 | |
1144 | |
1145 # The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height | |
1146 # (in pixels) of the graphs generated by dot. If a graph becomes larger than | |
1147 # this value, doxygen will try to truncate the graph, so that it fits within | |
1148 # the specified constraint. Beware that most browsers cannot cope with very | |
1149 # large images. | |
1150 | |
1151 MAX_DOT_GRAPH_HEIGHT = 1024 | |
1152 | |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1153 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1154 # graphs generated by dot. A depth value of 3 means that only nodes reachable |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1155 # from the root by following a path via at most 3 edges will be shown. Nodes that |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1156 # lay further from the root node will be omitted. Note that setting this option to |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1157 # 1 or 2 may greatly reduce the computation time needed for large code bases. Also |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1158 # note that a graph may be further truncated if the graph's image dimensions are |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1159 # not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH and MAX_DOT_GRAPH_HEIGHT). |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1160 # If 0 is used for the depth value (the default), the graph is not depth-constrained. |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1161 |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1162 MAX_DOT_GRAPH_DEPTH = 0 |
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1163 |
12800 | 1164 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent |
1165 # background. This is disabled by default, which results in a white background. | |
1166 # Warning: Depending on the platform used, enabling this option may lead to | |
1167 # badly anti-aliased labels on the edges of a graph (i.e. they become hard to | |
1168 # read). | |
1169 | |
1170 DOT_TRANSPARENT = NO | |
1171 | |
1172 # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output | |
1173 # files in one run (i.e. multiple -o and -T options on the command line). This | |
1174 # makes dot run faster, but since only newer versions of dot (>1.8.10) | |
1175 # support this, this feature is disabled by default. | |
1176 | |
1177 DOT_MULTI_TARGETS = YES | |
1178 | |
4554 | 1179 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will |
1180 # generate a legend page explaining the meaning of the various boxes and | |
1181 # arrows in the dot generated graphs. | |
1182 | |
1183 GENERATE_LEGEND = YES | |
1184 | |
1185 # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will | |
6317
285444815c6a
[gaim-migrate @ 6816]
Christian Hammond <chipx86@chipx86.com>
parents:
4554
diff
changeset
|
1186 # remove the intermediate dot files that are used to generate |
4554 | 1187 # the various graphs. |
1188 | |
1189 DOT_CLEANUP = YES | |
1190 | |
1191 #--------------------------------------------------------------------------- | |
1192 # Configuration::addtions related to the search engine | |
1193 #--------------------------------------------------------------------------- | |
1194 | |
1195 # The SEARCHENGINE tag specifies whether or not a search engine should be | |
1196 # used. If set to NO the values of all tags below this one will be ignored. | |
1197 | |
12800 | 1198 SEARCHENGINE = YES |