1 Description: Upstream changes introduced in version 2.2.0-1
2 This patch has been created by dpkg-source during the package build.
3 Here's the last changelog entry, hopefully it gives details on why
4 those changes were made:
6 dlt-daemon (2.2.0-1) unstable; urgency=low
8 * Initial GENIVI release
9 + Currently no way to automatically close bugs via changelog
12 The person named in the Author field signed this changelog entry.
13 Author: jeremiah <jeremiah.foster@pelagicore.com>
16 The information above should follow the Patch Tagging Guidelines, please
17 checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
18 are templates for supplementary fields that you might want to add:
20 Origin: <vendor|upstream|other>, <url of original patch>
21 Bug: <url in upstream bugtracker>
22 Bug-Debian: http://bugs.debian.org/<bugnumber>
23 Bug-Ubuntu: https://launchpad.net/bugs/<bugnumber>
24 Forwarded: <no|not-needed|url proving that it has been forwarded>
25 Reviewed-By: <name and email of someone who approved the patch>
26 Last-Update: <YYYY-MM-DD>
29 +++ dlt-daemon-2.2.0/automotive-dlt.pc
33 +libdir=${exec_prefix}/lib
34 +includedir=${exec_prefix}/include
37 +Description: Diagnostic Log and Trace
40 +Libs: -L${libdir} -ldlt -lrt -lpthread
41 +Cflags: -I${includedir}/dlt -DDLT_2_2
44 +++ dlt-daemon-2.2.0/doxygen.cfg
48 +# This file describes the settings to be used by the documentation system
49 +# doxygen (www.doxygen.org) for a project
51 +# All text after a hash (#) is considered a comment and will be ignored
53 +# TAG = value [value, ...]
54 +# For lists items can also be appended using:
55 +# TAG += value [value, ...]
56 +# Values that contain spaces should be placed between quotes (" ")
58 +#---------------------------------------------------------------------------
59 +# Project related configuration options
60 +#---------------------------------------------------------------------------
62 +# This tag specifies the encoding used for all characters in the config file
63 +# that follow. The default is UTF-8 which is also the encoding used for all
64 +# text before the first occurrence of this tag. Doxygen uses libiconv (or the
65 +# iconv built into libc) for the transcoding. See
66 +# http://www.gnu.org/software/libiconv for the list of possible encodings.
68 +DOXYFILE_ENCODING = UTF-8
70 +# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
71 +# by quotes) that should identify the project.
75 +# The PROJECT_NUMBER tag can be used to enter a project or revision number.
76 +# This could be handy for archiving the generated documentation or
77 +# if some version control system is used.
81 +# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
82 +# base path where the generated documentation will be put.
83 +# If a relative path is entered, it will be relative to the location
84 +# where doxygen was started. If left blank the current directory will be used.
86 +OUTPUT_DIRECTORY = doc
88 +# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
89 +# 4096 sub-directories (in 2 levels) under the output directory of each output
90 +# format and will distribute the generated files over these directories.
91 +# Enabling this option can be useful when feeding doxygen a huge amount of
92 +# source files, where putting all generated files in the same directory would
93 +# otherwise cause performance problems for the file system.
97 +# The OUTPUT_LANGUAGE tag is used to specify the language in which all
98 +# documentation generated by doxygen is written. Doxygen will use this
99 +# information to generate all constant output in the proper language.
100 +# The default language is English, other supported languages are:
101 +# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,
102 +# Croatian, Czech, Danish, Dutch, Farsi, Finnish, French, German, Greek,
103 +# Hungarian, Italian, Japanese, Japanese-en (Japanese with English messages),
104 +# Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, Polish,
105 +# Portuguese, Romanian, Russian, Serbian, Serbian-Cyrilic, Slovak, Slovene,
106 +# Spanish, Swedish, and Ukrainian.
108 +OUTPUT_LANGUAGE = English
110 +# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
111 +# include brief member descriptions after the members that are listed in
112 +# the file and class documentation (similar to JavaDoc).
113 +# Set to NO to disable this.
115 +BRIEF_MEMBER_DESC = YES
117 +# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
118 +# the brief description of a member or function before the detailed description.
119 +# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
120 +# brief descriptions will be completely suppressed.
124 +# This tag implements a quasi-intelligent brief description abbreviator
125 +# that is used to form the text in various listings. Each string
126 +# in this list, if found as the leading text of the brief description, will be
127 +# stripped from the text and the result after processing the whole list, is
128 +# used as the annotated text. Otherwise, the brief description is used as-is.
129 +# If left blank, the following values are used ("$name" is automatically
130 +# replaced with the name of the entity): "The $name class" "The $name widget"
131 +# "The $name file" "is" "provides" "specifies" "contains"
132 +# "represents" "a" "an" "the"
134 +ABBREVIATE_BRIEF = "The $name class" \
135 + "The $name widget" \
146 +# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
147 +# Doxygen will generate a detailed section even if there is only a brief
150 +ALWAYS_DETAILED_SEC = NO
152 +# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
153 +# inherited members of a class in the documentation of that class as if those
154 +# members were ordinary class members. Constructors, destructors and assignment
155 +# operators of the base classes will not be shown.
157 +INLINE_INHERITED_MEMB = NO
159 +# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
160 +# path before files name in the file list and in the header files. If set
161 +# to NO the shortest path that makes the file name unique will be used.
163 +FULL_PATH_NAMES = YES
165 +# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
166 +# can be used to strip a user-defined part of the path. Stripping is
167 +# only done if one of the specified strings matches the left-hand part of
168 +# the path. The tag can be used to show relative paths in the file list.
169 +# If left blank the directory from which doxygen is run is used as the
174 +# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
175 +# the path mentioned in the documentation of a class, which tells
176 +# the reader which header file to include in order to use a class.
177 +# If left blank only the name of the header file containing the class
178 +# definition is used. Otherwise one should specify the include paths that
179 +# are normally passed to the compiler using the -I flag.
181 +STRIP_FROM_INC_PATH =
183 +# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
184 +# (but less readable) file names. This can be useful is your file systems
185 +# doesn't support long names like on DOS, Mac, or CD-ROM.
189 +# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
190 +# will interpret the first line (until the first dot) of a JavaDoc-style
191 +# comment as the brief description. If set to NO, the JavaDoc
192 +# comments will behave just like regular Qt-style comments
193 +# (thus requiring an explicit @brief command for a brief description.)
195 +JAVADOC_AUTOBRIEF = NO
197 +# If the QT_AUTOBRIEF tag is set to YES then Doxygen will
198 +# interpret the first line (until the first dot) of a Qt-style
199 +# comment as the brief description. If set to NO, the comments
200 +# will behave just like regular Qt-style comments (thus requiring
201 +# an explicit \brief command for a brief description.)
205 +# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
206 +# treat a multi-line C++ special comment block (i.e. a block of //! or ///
207 +# comments) as a brief description. This used to be the default behaviour.
208 +# The new default is to treat a multi-line C++ comment block as a detailed
209 +# description. Set this tag to YES if you prefer the old behaviour instead.
211 +MULTILINE_CPP_IS_BRIEF = NO
213 +# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
214 +# member inherits the documentation from any documented member that it
219 +# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
220 +# a new page for each member. If set to NO, the documentation of a member will
221 +# be part of the file/class/namespace that contains it.
223 +SEPARATE_MEMBER_PAGES = NO
225 +# The TAB_SIZE tag can be used to set the number of spaces in a tab.
226 +# Doxygen uses this value to replace tabs by spaces in code fragments.
230 +# This tag can be used to specify a number of aliases that acts
231 +# as commands in the documentation. An alias has the form "name=value".
232 +# For example adding "sideeffect=\par Side Effects:\n" will allow you to
233 +# put the command \sideeffect (or @sideeffect) in the documentation, which
234 +# will result in a user-defined paragraph with heading "Side Effects:".
235 +# You can put \n's in the value part of an alias to insert newlines.
239 +# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
240 +# sources only. Doxygen will then generate output that is more tailored for C.
241 +# For instance, some of the names that are used will be different. The list
242 +# of all members will be omitted, etc.
244 +OPTIMIZE_OUTPUT_FOR_C = YES
246 +# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java
247 +# sources only. Doxygen will then generate output that is more tailored for
248 +# Java. For instance, namespaces will be presented as packages, qualified
249 +# scopes will look different, etc.
251 +OPTIMIZE_OUTPUT_JAVA = NO
253 +# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
254 +# sources only. Doxygen will then generate output that is more tailored for
257 +OPTIMIZE_FOR_FORTRAN = NO
259 +# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
260 +# sources. Doxygen will then generate output that is tailored for
263 +OPTIMIZE_OUTPUT_VHDL = NO
265 +# Doxygen selects the parser to use depending on the extension of the files it parses.
266 +# With this tag you can assign which parser to use for a given extension.
267 +# Doxygen has a built-in mapping, but you can override or extend it using this tag.
268 +# The format is ext=language, where ext is a file extension, and language is one of
269 +# the parsers supported by doxygen: IDL, Java, Javascript, C#, C, C++, D, PHP,
270 +# Objective-C, Python, Fortran, VHDL, C, C++. For instance to make doxygen treat
271 +# .inc files as Fortran files (default is PHP), and .f files as C (default is Fortran),
272 +# use: inc=Fortran f=C
276 +# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
277 +# to include (a tag file for) the STL sources as input, then you should
278 +# set this tag to YES in order to let doxygen match functions declarations and
279 +# definitions whose arguments contain STL classes (e.g. func(std::string); v.s.
280 +# func(std::string) {}). This also make the inheritance and collaboration
281 +# diagrams that involve STL classes more complete and accurate.
283 +BUILTIN_STL_SUPPORT = NO
285 +# If you use Microsoft's C++/CLI language, you should set this option to YES to
286 +# enable parsing support.
288 +CPP_CLI_SUPPORT = NO
290 +# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only.
291 +# Doxygen will parse them like normal C++ but will assume all classes use public
292 +# instead of private inheritance when no explicit protection keyword is present.
296 +# For Microsoft's IDL there are propget and propput attributes to indicate getter
297 +# and setter methods for a property. Setting this option to YES (the default)
298 +# will make doxygen to replace the get and set methods by a property in the
299 +# documentation. This will only work if the methods are indeed getting or
300 +# setting a simple type. If this is not the case, or you want to show the
301 +# methods anyway, you should set this option to NO.
303 +IDL_PROPERTY_SUPPORT = NO
305 +# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
306 +# tag is set to YES, then doxygen will reuse the documentation of the first
307 +# member in the group (if any) for the other members of the group. By default
308 +# all members of a group must be documented explicitly.
310 +DISTRIBUTE_GROUP_DOC = NO
312 +# Set the SUBGROUPING tag to YES (the default) to allow class member groups of
313 +# the same type (for instance a group of public functions) to be put as a
314 +# subgroup of that type (e.g. under the Public Functions section). Set it to
315 +# NO to prevent subgrouping. Alternatively, this can be done per class using
316 +# the \nosubgrouping command.
320 +# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum
321 +# is documented as struct, union, or enum with the name of the typedef. So
322 +# typedef struct TypeS {} TypeT, will appear in the documentation as a struct
323 +# with name TypeT. When disabled the typedef will appear as a member of a file,
324 +# namespace, or class. And the struct will be named TypeS. This can typically
325 +# be useful for C code in case the coding convention dictates that all compound
326 +# types are typedef'ed and only the typedef is referenced, never the tag name.
328 +TYPEDEF_HIDES_STRUCT = NO
330 +# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to
331 +# determine which symbols to keep in memory and which to flush to disk.
332 +# When the cache is full, less often used symbols will be written to disk.
333 +# For small to medium size projects (<1000 input files) the default value is
334 +# probably good enough. For larger projects a too small cache size can cause
335 +# doxygen to be busy swapping symbols to and from disk most of the time
336 +# causing a significant performance penality.
337 +# If the system has enough physical memory increasing the cache will improve the
338 +# performance by keeping more symbols in memory. Note that the value works on
339 +# a logarithmic scale so increasing the size by one will rougly double the
340 +# memory usage. The cache size is given by this formula:
341 +# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,
342 +# corresponding to a cache size of 2^16 = 65536 symbols
344 +SYMBOL_CACHE_SIZE = 0
346 +#---------------------------------------------------------------------------
347 +# Build related configuration options
348 +#---------------------------------------------------------------------------
350 +# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
351 +# documentation are documented, even if no documentation was available.
352 +# Private class members and static file members will be hidden unless
353 +# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
357 +# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
358 +# will be included in the documentation.
360 +EXTRACT_PRIVATE = YES
362 +# If the EXTRACT_STATIC tag is set to YES all static members of a file
363 +# will be included in the documentation.
365 +EXTRACT_STATIC = YES
367 +# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
368 +# defined locally in source files will be included in the documentation.
369 +# If set to NO only classes defined in header files are included.
371 +EXTRACT_LOCAL_CLASSES = YES
373 +# This flag is only useful for Objective-C code. When set to YES local
374 +# methods, which are defined in the implementation section but not in
375 +# the interface are included in the documentation.
376 +# If set to NO (the default) only methods in the interface are included.
378 +EXTRACT_LOCAL_METHODS = NO
380 +# If this flag is set to YES, the members of anonymous namespaces will be
381 +# extracted and appear in the documentation as a namespace called
382 +# 'anonymous_namespace{file}', where file will be replaced with the base
383 +# name of the file that contains the anonymous namespace. By default
384 +# anonymous namespace are hidden.
386 +EXTRACT_ANON_NSPACES = NO
388 +# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
389 +# undocumented members of documented classes, files or namespaces.
390 +# If set to NO (the default) these members will be included in the
391 +# various overviews, but no documentation section is generated.
392 +# This option has no effect if EXTRACT_ALL is enabled.
394 +HIDE_UNDOC_MEMBERS = NO
396 +# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
397 +# undocumented classes that are normally visible in the class hierarchy.
398 +# If set to NO (the default) these classes will be included in the various
399 +# overviews. This option has no effect if EXTRACT_ALL is enabled.
401 +HIDE_UNDOC_CLASSES = NO
403 +# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
404 +# friend (class|struct|union) declarations.
405 +# If set to NO (the default) these declarations will be included in the
408 +HIDE_FRIEND_COMPOUNDS = NO
410 +# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
411 +# documentation blocks found inside the body of a function.
412 +# If set to NO (the default) these blocks will be appended to the
413 +# function's detailed documentation block.
415 +HIDE_IN_BODY_DOCS = NO
417 +# The INTERNAL_DOCS tag determines if documentation
418 +# that is typed after a \internal command is included. If the tag is set
419 +# to NO (the default) then the documentation will be excluded.
420 +# Set it to YES to include the internal documentation.
424 +# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
425 +# file names in lower-case letters. If set to YES upper-case letters are also
426 +# allowed. This is useful if you have classes or files whose names only differ
427 +# in case and if your file system supports case sensitive file names. Windows
428 +# and Mac users are advised to set this option to NO.
430 +CASE_SENSE_NAMES = NO
432 +# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
433 +# will show members with their full class and namespace scopes in the
434 +# documentation. If set to YES the scope will be hidden.
436 +HIDE_SCOPE_NAMES = NO
438 +# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
439 +# will put a list of the files that are included by a file in the documentation
442 +SHOW_INCLUDE_FILES = YES
444 +# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
445 +# is inserted in the documentation for inline members.
449 +# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
450 +# will sort the (detailed) documentation of file and class members
451 +# alphabetically by member name. If set to NO the members will appear in
452 +# declaration order.
454 +SORT_MEMBER_DOCS = YES
456 +# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
457 +# brief documentation of file, namespace and class members alphabetically
458 +# by member name. If set to NO (the default) the members will appear in
459 +# declaration order.
461 +SORT_BRIEF_DOCS = NO
463 +# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the
464 +# hierarchy of group names into alphabetical order. If set to NO (the default)
465 +# the group names will appear in their defined order.
467 +SORT_GROUP_NAMES = NO
469 +# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
470 +# sorted by fully-qualified names, including namespaces. If set to
471 +# NO (the default), the class list will be sorted only by class name,
472 +# not including the namespace part.
473 +# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
474 +# Note: This option applies only to the class list, not to the
475 +# alphabetical list.
477 +SORT_BY_SCOPE_NAME = NO
479 +# The GENERATE_TODOLIST tag can be used to enable (YES) or
480 +# disable (NO) the todo list. This list is created by putting \todo
481 +# commands in the documentation.
483 +GENERATE_TODOLIST = YES
485 +# The GENERATE_TESTLIST tag can be used to enable (YES) or
486 +# disable (NO) the test list. This list is created by putting \test
487 +# commands in the documentation.
489 +GENERATE_TESTLIST = YES
491 +# The GENERATE_BUGLIST tag can be used to enable (YES) or
492 +# disable (NO) the bug list. This list is created by putting \bug
493 +# commands in the documentation.
495 +GENERATE_BUGLIST = YES
497 +# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
498 +# disable (NO) the deprecated list. This list is created by putting
499 +# \deprecated commands in the documentation.
501 +GENERATE_DEPRECATEDLIST= YES
503 +# The ENABLED_SECTIONS tag can be used to enable conditional
504 +# documentation sections, marked by \if sectionname ... \endif.
508 +# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
509 +# the initial value of a variable or define consists of for it to appear in
510 +# the documentation. If the initializer consists of more lines than specified
511 +# here it will be hidden. Use a value of 0 to hide initializers completely.
512 +# The appearance of the initializer of individual variables and defines in the
513 +# documentation can be controlled using \showinitializer or \hideinitializer
514 +# command in the documentation regardless of this setting.
516 +MAX_INITIALIZER_LINES = 30
518 +# Set the SHOW_USED_FILES tag to NO to disable the list of files generated
519 +# at the bottom of the documentation of classes and structs. If set to YES the
520 +# list will mention the files that were used to generate the documentation.
522 +SHOW_USED_FILES = YES
524 +# If the sources in your project are distributed over multiple directories
525 +# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
526 +# in the documentation. The default is NO.
528 +SHOW_DIRECTORIES = NO
530 +# Set the SHOW_FILES tag to NO to disable the generation of the Files page.
531 +# This will remove the Files entry from the Quick Index and from the
532 +# Folder Tree View (if specified). The default is YES.
536 +# Set the SHOW_NAMESPACES tag to NO to disable the generation of the
537 +# Namespaces page. This will remove the Namespaces entry from the Quick Index
538 +# and from the Folder Tree View (if specified). The default is YES.
540 +SHOW_NAMESPACES = YES
542 +# The FILE_VERSION_FILTER tag can be used to specify a program or script that
543 +# doxygen should invoke to get the current version for each file (typically from
544 +# the version control system). Doxygen will invoke the program by executing (via
545 +# popen()) the command <command> <input-file>, where <command> is the value of
546 +# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
547 +# provided by doxygen. Whatever the program writes to standard output
548 +# is used as the file version. See the manual for examples.
550 +FILE_VERSION_FILTER =
552 +# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed by
553 +# doxygen. The layout file controls the global structure of the generated output files
554 +# in an output format independent way. The create the layout file that represents
555 +# doxygen's defaults, run doxygen with the -l option. You can optionally specify a
556 +# file name after the option, if omitted DoxygenLayout.xml will be used as the name
557 +# of the layout file.
561 +#---------------------------------------------------------------------------
562 +# configuration options related to warning and progress messages
563 +#---------------------------------------------------------------------------
565 +# The QUIET tag can be used to turn on/off the messages that are generated
566 +# by doxygen. Possible values are YES and NO. If left blank NO is used.
570 +# The WARNINGS tag can be used to turn on/off the warning messages that are
571 +# generated by doxygen. Possible values are YES and NO. If left blank
576 +# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
577 +# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
578 +# automatically be disabled.
580 +WARN_IF_UNDOCUMENTED = YES
582 +# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
583 +# potential errors in the documentation, such as not documenting some
584 +# parameters in a documented function, or documenting parameters that
585 +# don't exist or using markup commands wrongly.
587 +WARN_IF_DOC_ERROR = YES
589 +# This WARN_NO_PARAMDOC option can be abled to get warnings for
590 +# functions that are documented, but have no documentation for their parameters
591 +# or return value. If set to NO (the default) doxygen will only warn about
592 +# wrong or incomplete parameter documentation, but not about the absence of
595 +WARN_NO_PARAMDOC = NO
597 +# The WARN_FORMAT tag determines the format of the warning messages that
598 +# doxygen can produce. The string should contain the $file, $line, and $text
599 +# tags, which will be replaced by the file and line number from which the
600 +# warning originated and the warning text. Optionally the format may contain
601 +# $version, which will be replaced by the version of the file (if it could
602 +# be obtained via FILE_VERSION_FILTER)
604 +WARN_FORMAT = "$file:$line: $text"
606 +# The WARN_LOGFILE tag can be used to specify a file to which warning
607 +# and error messages should be written. If left blank the output is written
612 +#---------------------------------------------------------------------------
613 +# configuration options related to the input files
614 +#---------------------------------------------------------------------------
616 +# The INPUT tag can be used to specify the files and/or directories that contain
617 +# documented source files. You may enter file names like "myfile.cpp" or
618 +# directories like "/usr/src/myproject". Separate the files or directories
621 +INPUT = src/ include/
623 +# This tag can be used to specify the character encoding of the source files
624 +# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is
625 +# also the default input encoding. Doxygen uses libiconv (or the iconv built
626 +# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for
627 +# the list of possible encodings.
629 +INPUT_ENCODING = UTF-8
631 +# If the value of the INPUT tag contains directories, you can use the
632 +# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
633 +# and *.h) to filter out the source-files in the directories. If left
634 +# blank the following patterns are tested:
635 +# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx
636 +# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90
638 +FILE_PATTERNS = *.c \
657 +# The RECURSIVE tag can be used to turn specify whether or not subdirectories
658 +# should be searched for input files as well. Possible values are YES and NO.
659 +# If left blank NO is used.
663 +# The EXCLUDE tag can be used to specify files and/or directories that should
664 +# excluded from the INPUT source files. This way you can easily exclude a
665 +# subdirectory from a directory tree whose root is specified with the INPUT tag.
671 +# The EXCLUDE_SYMLINKS tag can be used select whether or not files or
672 +# directories that are symbolic links (a Unix filesystem feature) are excluded
675 +EXCLUDE_SYMLINKS = NO
677 +# If the value of the INPUT tag contains directories, you can use the
678 +# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
679 +# certain files from those directories. Note that the wildcards are matched
680 +# against the file with absolute path, so to exclude all test directories
681 +# for example use the pattern */test/*
685 +# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
686 +# (namespaces, classes, functions, etc.) that should be excluded from the
687 +# output. The symbol name can be a fully qualified name, a word, or if the
688 +# wildcard * is used, a substring. Examples: ANamespace, AClass,
689 +# AClass::ANamespace, ANamespace::*Test
693 +# The EXAMPLE_PATH tag can be used to specify one or more files or
694 +# directories that contain example code fragments that are included (see
695 +# the \include command).
699 +# If the value of the EXAMPLE_PATH tag contains directories, you can use the
700 +# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
701 +# and *.h) to filter out the source-files in the directories. If left
702 +# blank all files are included.
704 +EXAMPLE_PATTERNS = *
706 +# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
707 +# searched for input files to be used with the \include or \dontinclude
708 +# commands irrespective of the value of the RECURSIVE tag.
709 +# Possible values are YES and NO. If left blank NO is used.
711 +EXAMPLE_RECURSIVE = NO
713 +# The IMAGE_PATH tag can be used to specify one or more files or
714 +# directories that contain image that are included in the documentation (see
715 +# the \image command).
719 +# The INPUT_FILTER tag can be used to specify a program that doxygen should
720 +# invoke to filter for each input file. Doxygen will invoke the filter program
721 +# by executing (via popen()) the command <filter> <input-file>, where <filter>
722 +# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
723 +# input file. Doxygen will then use the output that the filter program writes
724 +# to standard output. If FILTER_PATTERNS is specified, this tag will be
729 +# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
730 +# basis. Doxygen will compare the file name with each pattern and apply the
731 +# filter if there is a match. The filters are a list of the form:
732 +# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
733 +# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER
734 +# is applied to all files.
738 +# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
739 +# INPUT_FILTER) will be used to filter the input files when producing source
740 +# files to browse (i.e. when SOURCE_BROWSER is set to YES).
742 +FILTER_SOURCE_FILES = NO
744 +#---------------------------------------------------------------------------
745 +# configuration options related to source browsing
746 +#---------------------------------------------------------------------------
748 +# If the SOURCE_BROWSER tag is set to YES then a list of source files will
749 +# be generated. Documented entities will be cross-referenced with these sources.
750 +# Note: To get rid of all source code in the generated output, make sure also
751 +# VERBATIM_HEADERS is set to NO.
753 +SOURCE_BROWSER = YES
755 +# Setting the INLINE_SOURCES tag to YES will include the body
756 +# of functions and classes directly in the documentation.
760 +# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
761 +# doxygen to hide any special comment blocks from generated source code
762 +# fragments. Normal C and C++ comments will always remain visible.
764 +STRIP_CODE_COMMENTS = YES
766 +# If the REFERENCED_BY_RELATION tag is set to YES
767 +# then for each documented function all documented
768 +# functions referencing it will be listed.
770 +REFERENCED_BY_RELATION = YES
772 +# If the REFERENCES_RELATION tag is set to YES
773 +# then for each documented function all documented entities
774 +# called/used by that function will be listed.
776 +REFERENCES_RELATION = YES
778 +# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
779 +# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
780 +# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
781 +# link to the source code. Otherwise they will link to the documentation.
783 +REFERENCES_LINK_SOURCE = YES
785 +# If the USE_HTAGS tag is set to YES then the references to source code
786 +# will point to the HTML generated by the htags(1) tool instead of doxygen
787 +# built-in source browser. The htags tool is part of GNU's global source
788 +# tagging system (see http://www.gnu.org/software/global/global.html). You
789 +# will need version 4.8.6 or higher.
793 +# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
794 +# will generate a verbatim copy of the header file for each class for
795 +# which an include is specified. Set to NO to disable this.
797 +VERBATIM_HEADERS = NO
799 +#---------------------------------------------------------------------------
800 +# configuration options related to the alphabetical class index
801 +#---------------------------------------------------------------------------
803 +# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
804 +# of all compounds will be generated. Enable this if the project
805 +# contains a lot of classes, structs, unions or interfaces.
807 +ALPHABETICAL_INDEX = NO
809 +# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
810 +# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
811 +# in which this list will be split (can be a number in the range [1..20])
813 +COLS_IN_ALPHA_INDEX = 5
815 +# In case all classes in a project start with a common prefix, all
816 +# classes will be put under the same header in the alphabetical index.
817 +# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
818 +# should be ignored while generating the index headers.
822 +#---------------------------------------------------------------------------
823 +# configuration options related to the HTML output
824 +#---------------------------------------------------------------------------
826 +# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
827 +# generate HTML output.
831 +# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
832 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
833 +# put in front of it. If left blank `html' will be used as the default path.
837 +# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
838 +# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
839 +# doxygen will generate files with .html extension.
841 +HTML_FILE_EXTENSION = .html
843 +# The HTML_HEADER tag can be used to specify a personal HTML header for
844 +# each generated HTML page. If it is left blank doxygen will generate a
849 +# The HTML_FOOTER tag can be used to specify a personal HTML footer for
850 +# each generated HTML page. If it is left blank doxygen will generate a
855 +# The HTML_STYLESHEET tag can be used to specify a user-defined cascading
856 +# style sheet that is used by each HTML page. It can be used to
857 +# fine-tune the look of the HTML output. If the tag is left blank doxygen
858 +# will generate a default style sheet. Note that doxygen will try to copy
859 +# the style sheet file to the HTML output directory, so don't put your own
860 +# stylesheet in the HTML output directory as well, or it will be erased!
864 +# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
865 +# files or namespaces will be aligned in HTML using tables. If set to
866 +# NO a bullet list will be used.
868 +HTML_ALIGN_MEMBERS = YES
870 +# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
871 +# documentation will contain sections that can be hidden and shown after the
872 +# page has loaded. For this to work a browser that supports
873 +# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox
874 +# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).
876 +HTML_DYNAMIC_SECTIONS = NO
878 +# If the GENERATE_DOCSET tag is set to YES, additional index files
879 +# will be generated that can be used as input for Apple's Xcode 3
880 +# integrated development environment, introduced with OSX 10.5 (Leopard).
881 +# To create a documentation set, doxygen will generate a Makefile in the
882 +# HTML output directory. Running make will produce the docset in that
883 +# directory and running "make install" will install the docset in
884 +# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
886 +# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html for more information.
888 +GENERATE_DOCSET = NO
890 +# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the
891 +# feed. A documentation feed provides an umbrella under which multiple
892 +# documentation sets from a single provider (such as a company or product suite)
895 +DOCSET_FEEDNAME = "Doxygen generated docs"
897 +# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that
898 +# should uniquely identify the documentation set bundle. This should be a
899 +# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen
900 +# will append .docset to the name.
902 +DOCSET_BUNDLE_ID = org.doxygen.Project
904 +# If the GENERATE_HTMLHELP tag is set to YES, additional index files
905 +# will be generated that can be used as input for tools like the
906 +# Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
907 +# of the generated HTML documentation.
909 +GENERATE_HTMLHELP = NO
911 +# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
912 +# be used to specify the file name of the resulting .chm file. You
913 +# can add a path in front of the file if the result should not be
914 +# written to the html output directory.
918 +# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
919 +# be used to specify the location (absolute path including file name) of
920 +# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
921 +# the HTML help compiler on the generated index.hhp.
925 +# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
926 +# controls if a separate .chi index file is generated (YES) or that
927 +# it should be included in the master .chm file (NO).
931 +# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING
932 +# is used to encode HtmlHelp index (hhk), content (hhc) and project file
935 +CHM_INDEX_ENCODING =
937 +# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
938 +# controls whether a binary table of contents is generated (YES) or a
939 +# normal table of contents (NO) in the .chm file.
943 +# The TOC_EXPAND flag can be set to YES to add extra items for group members
944 +# to the contents of the HTML help documentation and to the tree view.
948 +# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and QHP_VIRTUAL_FOLDER
949 +# are set, an additional index file will be generated that can be used as input for
950 +# Qt's qhelpgenerator to generate a Qt Compressed Help (.qch) of the generated
951 +# HTML documentation.
955 +# If the QHG_LOCATION tag is specified, the QCH_FILE tag can
956 +# be used to specify the file name of the resulting .qch file.
957 +# The path specified is relative to the HTML output folder.
961 +# The QHP_NAMESPACE tag specifies the namespace to use when generating
962 +# Qt Help Project output. For more information please see
963 +# http://doc.trolltech.com/qthelpproject.html#namespace
967 +# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating
968 +# Qt Help Project output. For more information please see
969 +# http://doc.trolltech.com/qthelpproject.html#virtual-folders
971 +QHP_VIRTUAL_FOLDER = doc
973 +# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to add.
974 +# For more information please see
975 +# http://doc.trolltech.com/qthelpproject.html#custom-filters
977 +QHP_CUST_FILTER_NAME =
979 +# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the custom filter to add.For more information please see
980 +# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">Qt Help Project / Custom Filters</a>.
982 +QHP_CUST_FILTER_ATTRS =
984 +# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this project's
985 +# filter section matches.
986 +# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">Qt Help Project / Filter Attributes</a>.
988 +QHP_SECT_FILTER_ATTRS =
990 +# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can
991 +# be used to specify the location of Qt's qhelpgenerator.
992 +# If non-empty doxygen will try to run qhelpgenerator on the generated
997 +# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
998 +# top of each HTML page. The value NO (the default) enables the index and
999 +# the value YES disables it.
1003 +# This tag can be used to set the number of enum values (range [1..20])
1004 +# that doxygen will group on one line in the generated HTML documentation.
1006 +ENUM_VALUES_PER_LINE = 4
1008 +# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1009 +# structure should be generated to display hierarchical information.
1010 +# If the tag value is set to FRAME, a side panel will be generated
1011 +# containing a tree-like index structure (just like the one that
1012 +# is generated for HTML Help). For this to work a browser that supports
1013 +# JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+,
1014 +# Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are
1015 +# probably better off using the HTML help feature. Other possible values
1016 +# for this tag are: HIERARCHIES, which will generate the Groups, Directories,
1017 +# and Class Hierarchy pages using a tree view instead of an ordered list;
1018 +# ALL, which combines the behavior of FRAME and HIERARCHIES; and NONE, which
1019 +# disables this behavior completely. For backwards compatibility with previous
1020 +# releases of Doxygen, the values YES and NO are equivalent to FRAME and NONE
1023 +GENERATE_TREEVIEW = ALL
1025 +# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
1026 +# used to set the initial width (in pixels) of the frame in which the tree
1029 +TREEVIEW_WIDTH = 250
1031 +# Use this tag to change the font size of Latex formulas included
1032 +# as images in the HTML documentation. The default is 10. Note that
1033 +# when you change the font size after a successful doxygen run you need
1034 +# to manually remove any form_*.png images from the HTML output directory
1035 +# to force them to be regenerated.
1037 +FORMULA_FONTSIZE = 10
1039 +#---------------------------------------------------------------------------
1040 +# configuration options related to the LaTeX output
1041 +#---------------------------------------------------------------------------
1043 +# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
1044 +# generate Latex output.
1046 +GENERATE_LATEX = YES
1048 +# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
1049 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1050 +# put in front of it. If left blank `latex' will be used as the default path.
1052 +LATEX_OUTPUT = latex
1054 +# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
1055 +# invoked. If left blank `latex' will be used as the default command name.
1057 +LATEX_CMD_NAME = latex
1059 +# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
1060 +# generate index for LaTeX. If left blank `makeindex' will be used as the
1061 +# default command name.
1063 +MAKEINDEX_CMD_NAME = makeindex
1065 +# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
1066 +# LaTeX documents. This may be useful for small projects and may help to
1067 +# save some trees in general.
1071 +# The PAPER_TYPE tag can be used to set the paper type that is used
1072 +# by the printer. Possible values are: a4, a4wide, letter, legal and
1073 +# executive. If left blank a4wide will be used.
1075 +PAPER_TYPE = a4wide
1077 +# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
1078 +# packages that should be included in the LaTeX output.
1082 +# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
1083 +# the generated latex document. The header should contain everything until
1084 +# the first chapter. If it is left blank doxygen will generate a
1085 +# standard header. Notice: only use this tag if you know what you are doing!
1089 +# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
1090 +# is prepared for conversion to pdf (using ps2pdf). The pdf file will
1091 +# contain links (just like the HTML output) instead of page references
1092 +# This makes the output suitable for online browsing using a pdf viewer.
1094 +PDF_HYPERLINKS = YES
1096 +# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
1097 +# plain latex in the generated Makefile. Set this option to YES to get a
1098 +# higher quality PDF documentation.
1102 +# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
1103 +# command to the generated LaTeX files. This will instruct LaTeX to keep
1104 +# running if errors occur, instead of asking the user for help.
1105 +# This option is also used when generating formulas in HTML.
1107 +LATEX_BATCHMODE = NO
1109 +# If LATEX_HIDE_INDICES is set to YES then doxygen will not
1110 +# include the index chapters (such as File Index, Compound Index, etc.)
1113 +LATEX_HIDE_INDICES = NO
1115 +#---------------------------------------------------------------------------
1116 +# configuration options related to the RTF output
1117 +#---------------------------------------------------------------------------
1119 +# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
1120 +# The RTF output is optimized for Word 97 and may not look very pretty with
1121 +# other RTF readers or editors.
1125 +# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
1126 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1127 +# put in front of it. If left blank `rtf' will be used as the default path.
1131 +# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
1132 +# RTF documents. This may be useful for small projects and may help to
1133 +# save some trees in general.
1137 +# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
1138 +# will contain hyperlink fields. The RTF file will
1139 +# contain links (just like the HTML output) instead of page references.
1140 +# This makes the output suitable for online browsing using WORD or other
1141 +# programs which support those fields.
1142 +# Note: wordpad (write) and others do not support links.
1144 +RTF_HYPERLINKS = NO
1146 +# Load stylesheet definitions from file. Syntax is similar to doxygen's
1147 +# config file, i.e. a series of assignments. You only have to provide
1148 +# replacements, missing definitions are set to their default value.
1150 +RTF_STYLESHEET_FILE =
1152 +# Set optional variables used in the generation of an rtf document.
1153 +# Syntax is similar to doxygen's config file.
1155 +RTF_EXTENSIONS_FILE =
1157 +#---------------------------------------------------------------------------
1158 +# configuration options related to the man page output
1159 +#---------------------------------------------------------------------------
1161 +# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
1162 +# generate man pages
1166 +# The MAN_OUTPUT tag is used to specify where the man pages will be put.
1167 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1168 +# put in front of it. If left blank `man' will be used as the default path.
1172 +# The MAN_EXTENSION tag determines the extension that is added to
1173 +# the generated man pages (default is the subroutine's section .3)
1177 +# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
1178 +# then it will generate one additional man file for each entity
1179 +# documented in the real man page(s). These additional files
1180 +# only source the real man page, but without them the man command
1181 +# would be unable to find the correct page. The default is NO.
1185 +#---------------------------------------------------------------------------
1186 +# configuration options related to the XML output
1187 +#---------------------------------------------------------------------------
1189 +# If the GENERATE_XML tag is set to YES Doxygen will
1190 +# generate an XML file that captures the structure of
1191 +# the code including all documentation.
1195 +# The XML_OUTPUT tag is used to specify where the XML pages will be put.
1196 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1197 +# put in front of it. If left blank `xml' will be used as the default path.
1201 +# The XML_SCHEMA tag can be used to specify an XML schema,
1202 +# which can be used by a validating XML parser to check the
1203 +# syntax of the XML files.
1207 +# The XML_DTD tag can be used to specify an XML DTD,
1208 +# which can be used by a validating XML parser to check the
1209 +# syntax of the XML files.
1213 +# If the XML_PROGRAMLISTING tag is set to YES Doxygen will
1214 +# dump the program listings (including syntax highlighting
1215 +# and cross-referencing information) to the XML output. Note that
1216 +# enabling this will significantly increase the size of the XML output.
1218 +XML_PROGRAMLISTING = YES
1220 +#---------------------------------------------------------------------------
1221 +# configuration options for the AutoGen Definitions output
1222 +#---------------------------------------------------------------------------
1224 +# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
1225 +# generate an AutoGen Definitions (see autogen.sf.net) file
1226 +# that captures the structure of the code including all
1227 +# documentation. Note that this feature is still experimental
1228 +# and incomplete at the moment.
1230 +GENERATE_AUTOGEN_DEF = NO
1232 +#---------------------------------------------------------------------------
1233 +# configuration options related to the Perl module output
1234 +#---------------------------------------------------------------------------
1236 +# If the GENERATE_PERLMOD tag is set to YES Doxygen will
1237 +# generate a Perl module file that captures the structure of
1238 +# the code including all documentation. Note that this
1239 +# feature is still experimental and incomplete at the
1242 +GENERATE_PERLMOD = NO
1244 +# If the PERLMOD_LATEX tag is set to YES Doxygen will generate
1245 +# the necessary Makefile rules, Perl scripts and LaTeX code to be able
1246 +# to generate PDF and DVI output from the Perl module output.
1250 +# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
1251 +# nicely formatted so it can be parsed by a human reader. This is useful
1252 +# if you want to understand what is going on. On the other hand, if this
1253 +# tag is set to NO the size of the Perl module output will be much smaller
1254 +# and Perl will parse it just the same.
1256 +PERLMOD_PRETTY = YES
1258 +# The names of the make variables in the generated doxyrules.make file
1259 +# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
1260 +# This is useful so different doxyrules.make files included by the same
1261 +# Makefile don't overwrite each other's variables.
1263 +PERLMOD_MAKEVAR_PREFIX =
1265 +#---------------------------------------------------------------------------
1266 +# Configuration options related to the preprocessor
1267 +#---------------------------------------------------------------------------
1269 +# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
1270 +# evaluate all C-preprocessor directives found in the sources and include
1273 +ENABLE_PREPROCESSING = YES
1275 +# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
1276 +# names in the source code. If set to NO (the default) only conditional
1277 +# compilation will be performed. Macro expansion can be done in a controlled
1278 +# way by setting EXPAND_ONLY_PREDEF to YES.
1280 +MACRO_EXPANSION = NO
1282 +# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
1283 +# then the macro expansion is limited to the macros specified with the
1284 +# PREDEFINED and EXPAND_AS_DEFINED tags.
1286 +EXPAND_ONLY_PREDEF = NO
1288 +# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
1289 +# in the INCLUDE_PATH (see below) will be search if a #include is found.
1291 +SEARCH_INCLUDES = YES
1293 +# The INCLUDE_PATH tag can be used to specify one or more directories that
1294 +# contain include files that are not input files but should be processed by
1295 +# the preprocessor.
1299 +# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
1300 +# patterns (like *.h and *.hpp) to filter out the header-files in the
1301 +# directories. If left blank, the patterns specified with FILE_PATTERNS will
1304 +INCLUDE_FILE_PATTERNS =
1306 +# The PREDEFINED tag can be used to specify one or more macro names that
1307 +# are defined before the preprocessor is started (similar to the -D option of
1308 +# gcc). The argument of the tag is a list of macros of the form: name
1309 +# or name=definition (no spaces). If the definition and the = are
1310 +# omitted =1 is assumed. To prevent a macro definition from being
1311 +# undefined via #undef or recursively expanded use the := operator
1312 +# instead of the = operator.
1316 +# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
1317 +# this tag can be used to specify a list of macro names that should be expanded.
1318 +# The macro definition that is found in the sources will be used.
1319 +# Use the PREDEFINED tag if you want to use a different macro definition.
1321 +EXPAND_AS_DEFINED =
1323 +# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
1324 +# doxygen's preprocessor will remove all function-like macros that are alone
1325 +# on a line, have an all uppercase name, and do not end with a semicolon. Such
1326 +# function macros are typically used for boiler-plate code, and will confuse
1327 +# the parser if not removed.
1329 +SKIP_FUNCTION_MACROS = NO
1331 +#---------------------------------------------------------------------------
1332 +# Configuration::additions related to external references
1333 +#---------------------------------------------------------------------------
1335 +# The TAGFILES option can be used to specify one or more tagfiles.
1336 +# Optionally an initial location of the external documentation
1337 +# can be added for each tagfile. The format of a tag file without
1338 +# this location is as follows:
1339 +# TAGFILES = file1 file2 ...
1340 +# Adding location for the tag files is done as follows:
1341 +# TAGFILES = file1=loc1 "file2 = loc2" ...
1342 +# where "loc1" and "loc2" can be relative or absolute paths or
1343 +# URLs. If a location is present for each tag, the installdox tool
1344 +# does not have to be run to correct the links.
1345 +# Note that each tag file must have a unique name
1346 +# (where the name does NOT include the path)
1347 +# If a tag file is not located in the directory in which doxygen
1348 +# is run, you must also specify the path to the tagfile here.
1352 +# When a file name is specified after GENERATE_TAGFILE, doxygen will create
1353 +# a tag file that is based on the input files it reads.
1357 +# If the ALLEXTERNALS tag is set to YES all external classes will be listed
1358 +# in the class index. If set to NO only the inherited external classes
1363 +# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1364 +# in the modules index. If set to NO, only the current project's groups will
1367 +EXTERNAL_GROUPS = YES
1369 +# The PERL_PATH should be the absolute path and name of the perl script
1370 +# interpreter (i.e. the result of `which perl').
1372 +PERL_PATH = /usr/bin/perl
1374 +#---------------------------------------------------------------------------
1375 +# Configuration options related to the dot tool
1376 +#---------------------------------------------------------------------------
1378 +# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1379 +# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
1380 +# or super classes. Setting the tag to NO turns the diagrams off. Note that
1381 +# this option is superseded by the HAVE_DOT option below. This is only a
1382 +# fallback. It is recommended to install and use dot, since it yields more
1385 +CLASS_DIAGRAMS = NO
1387 +# You can define message sequence charts within doxygen comments using the \msc
1388 +# command. Doxygen will then run the mscgen tool (see
1389 +# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the
1390 +# documentation. The MSCGEN_PATH tag allows you to specify the directory where
1391 +# the mscgen tool resides. If left empty the tool is assumed to be found in the
1392 +# default search path.
1396 +# If set to YES, the inheritance and collaboration graphs will hide
1397 +# inheritance and usage relations if the target is undocumented
1398 +# or is not a class.
1400 +HIDE_UNDOC_RELATIONS = YES
1402 +# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1403 +# available from the path. This tool is part of Graphviz, a graph visualization
1404 +# toolkit from AT&T and Lucent Bell Labs. The other options in this section
1405 +# have no effect if this option is set to NO (the default)
1409 +# By default doxygen will write a font called FreeSans.ttf to the output
1410 +# directory and reference it in all dot files that doxygen generates. This
1411 +# font does not include all possible unicode characters however, so when you need
1412 +# these (or just want a differently looking font) you can specify the font name
1413 +# using DOT_FONTNAME. You need need to make sure dot is able to find the font,
1414 +# which can be done by putting it in a standard location or by setting the
1415 +# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory
1416 +# containing the font.
1418 +DOT_FONTNAME = FreeSans
1420 +# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs.
1421 +# The default size is 10pt.
1425 +# By default doxygen will tell dot to use the output directory to look for the
1426 +# FreeSans.ttf font (which doxygen will put there itself). If you specify a
1427 +# different font using DOT_FONTNAME you can set the path where dot
1428 +# can find it using this tag.
1432 +# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
1433 +# will generate a graph for each documented class showing the direct and
1434 +# indirect inheritance relations. Setting this tag to YES will force the
1435 +# the CLASS_DIAGRAMS tag to NO.
1439 +# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
1440 +# will generate a graph for each documented class showing the direct and
1441 +# indirect implementation dependencies (inheritance, containment, and
1442 +# class references variables) of the class with other documented classes.
1444 +COLLABORATION_GRAPH = YES
1446 +# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
1447 +# will generate a graph for groups, showing the direct groups dependencies
1451 +# If the UML_LOOK tag is set to YES doxygen will generate inheritance and
1452 +# collaboration diagrams in a style similar to the OMG's Unified Modeling
1457 +# If set to YES, the inheritance and collaboration graphs will show the
1458 +# relations between templates and their instances.
1460 +TEMPLATE_RELATIONS = NO
1462 +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
1463 +# tags are set to YES then doxygen will generate a graph for each documented
1464 +# file showing the direct and indirect include dependencies of the file with
1465 +# other documented files.
1467 +INCLUDE_GRAPH = YES
1469 +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
1470 +# HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1471 +# documented header file showing the documented files that directly or
1472 +# indirectly include this file.
1474 +INCLUDED_BY_GRAPH = YES
1476 +# If the CALL_GRAPH and HAVE_DOT options are set to YES then
1477 +# doxygen will generate a call dependency graph for every global function
1478 +# or class method. Note that enabling this option will significantly increase
1479 +# the time of a run. So in most cases it will be better to enable call graphs
1480 +# for selected functions only using the \callgraph command.
1484 +# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then
1485 +# doxygen will generate a caller dependency graph for every global function
1486 +# or class method. Note that enabling this option will significantly increase
1487 +# the time of a run. So in most cases it will be better to enable caller
1488 +# graphs for selected functions only using the \callergraph command.
1492 +# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
1493 +# will graphical hierarchy of all classes instead of a textual one.
1495 +GRAPHICAL_HIERARCHY = YES
1497 +# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
1498 +# then doxygen will show the dependencies a directory has on other directories
1499 +# in a graphical way. The dependency relations are determined by the #include
1500 +# relations between the files in the directories.
1502 +DIRECTORY_GRAPH = YES
1504 +# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1505 +# generated by dot. Possible values are png, jpg, or gif
1506 +# If left blank png will be used.
1508 +DOT_IMAGE_FORMAT = png
1510 +# The tag DOT_PATH can be used to specify the path where the dot tool can be
1511 +# found. If left blank, it is assumed the dot tool can be found in the path.
1515 +# The DOTFILE_DIRS tag can be used to specify one or more directories that
1516 +# contain dot files that are included in the documentation (see the
1517 +# \dotfile command).
1521 +# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of
1522 +# nodes that will be shown in the graph. If the number of nodes in a graph
1523 +# becomes larger than this value, doxygen will truncate the graph, which is
1524 +# visualized by representing a node as a red box. Note that doxygen if the
1525 +# number of direct children of the root node in a graph is already larger than
1526 +# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note
1527 +# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
1529 +DOT_GRAPH_MAX_NODES = 50
1531 +# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
1532 +# graphs generated by dot. A depth value of 3 means that only nodes reachable
1533 +# from the root by following a path via at most 3 edges will be shown. Nodes
1534 +# that lay further from the root node will be omitted. Note that setting this
1535 +# option to 1 or 2 may greatly reduce the computation time needed for large
1536 +# code bases. Also note that the size of a graph can be further restricted by
1537 +# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
1539 +MAX_DOT_GRAPH_DEPTH = 0
1541 +# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
1542 +# background. This is disabled by default, because dot on Windows does not
1543 +# seem to support this out of the box. Warning: Depending on the platform used,
1544 +# enabling this option may lead to badly anti-aliased labels on the edges of
1545 +# a graph (i.e. they become hard to read).
1547 +DOT_TRANSPARENT = NO
1549 +# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
1550 +# files in one run (i.e. multiple -o and -T options on the command line). This
1551 +# makes dot run faster, but since only newer versions of dot (>1.8.10)
1552 +# support this, this feature is disabled by default.
1554 +DOT_MULTI_TARGETS = NO
1556 +# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1557 +# generate a legend page explaining the meaning of the various boxes and
1558 +# arrows in the dot generated graphs.
1560 +GENERATE_LEGEND = YES
1562 +# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1563 +# remove the intermediate dot files that are used to generate
1564 +# the various graphs.
1568 +#---------------------------------------------------------------------------
1569 +# Options related to the search engine
1570 +#---------------------------------------------------------------------------
1572 +# The SEARCHENGINE tag specifies whether or not a search engine should be
1573 +# used. If set to NO the values of all tags below this one will be ignored.
1577 +++ dlt-daemon-2.2.0/config.h
1579 +#define HAVE_ARPAINET_H 1
1580 +#define HAVE_FCNTL_H 1
1581 +#define HAVE_FLOAT_H 1
1582 +#define HAVE_LIMITS_H 1
1583 +#define HAVE_NETDB_H 1
1584 +#define HAVE_NETINETIN_H 1
1585 +#define HAVE_STDDEF_H 1
1586 +#define HAVE_STDINT_H 1
1587 +#define HAVE_STDLIB_H 1
1588 +#define HAVE_STRING_H 1
1589 +#define HAVE_STRINGS_H 1
1590 +#define HAVE_SYSIOCTL_H 1
1591 +#define HAVE_SYSSOCKET_H 1
1592 +#define HAVE_SYSTIME_H 1
1593 +#define HAVE_UNISTD_H 1
1594 +#define HAVE_SYSIPC_H 1
1595 +#define HAVE_NETDB_H 1
1596 +#define HAVE_CTYPE_H 1
1597 +#define HAVE_SIGNAL_H 1
1598 +#define HAVE_SYSLOG_H 1
1599 +#define HAVE_SYSSTAT_H 1
1600 +#define HAVE_LINUXSTAT_H 1
1601 +#define HAVE_SYSUIO_H 1
1602 +#define HAVE_TERMIOS_H 1
1603 +#define HAVE_UNISTD_H 1
1605 +#define HAVE_FUNC_BZERO 1
1606 +#define HAVE_FUNC_CLOCKGETTIME 0
1607 +#define HAVE_FUNC_FLOOR 0
1608 +#define HAVE_FUNC_FORK 1
1609 +#define HAVE_FUNC_GETHOSTBYNAME 1
1610 +#define HAVE_FUNC_GETTIMEBYDAY 1
1611 +#define HAVE_FUNC_INETNTOA 1
1612 +#define HAVE_FUNC_MALLOC 1
1613 +#define HAVE_FUNC_MEMMOVE 1
1614 +#define HAVE_FUNC_MEMSET 1
1615 +#define HAVE_FUNC_MKFIFO 1
1616 +#define HAVE_FUNC_SELECT 1
1617 +#define HAVE_FUNC_SOCKET 1
1618 +#define HAVE_FUNC_STRCHR 1
1619 +#define HAVE_FUNC_STRERROR 1
1620 +#define HAVE_FUNC_STRSTR 1
1621 +#define HAVE_FUNC_STRTOL 1
1624 +++ dlt-daemon-2.2.0/svnversion.h
1626 +/* DO NOT EDIT! GENERATED AUTOMATICALLY! */
1627 +#define SVN_VERSION "1666"