aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/libraries/eet/doc
diff options
context:
space:
mode:
Diffstat (limited to 'libraries/eet/doc')
-rw-r--r--libraries/eet/doc/Doxyfile1694
-rw-r--r--libraries/eet/doc/Doxyfile.in1694
-rw-r--r--libraries/eet/doc/Makefile.am40
-rw-r--r--libraries/eet/doc/Makefile.in443
-rw-r--r--libraries/eet/doc/e.css436
-rw-r--r--libraries/eet/doc/eet.dox.in0
-rw-r--r--libraries/eet/doc/foot.html20
-rw-r--r--libraries/eet/doc/head.html65
-rwxr-xr-xlibraries/eet/doc/img/e.pngbin3825 -> 0 bytes
-rwxr-xr-xlibraries/eet/doc/img/e_big.pngbin30052 -> 0 bytes
-rwxr-xr-xlibraries/eet/doc/img/edoxy.css966
-rw-r--r--libraries/eet/doc/img/eet.pngbin74944 -> 0 bytes
-rwxr-xr-xlibraries/eet/doc/img/foot_bg.pngbin173 -> 0 bytes
-rwxr-xr-xlibraries/eet/doc/img/head_bg.pngbin214 -> 0 bytes
-rw-r--r--libraries/eet/doc/img/hilite.pngbin6127 -> 0 bytes
-rwxr-xr-xlibraries/eet/doc/img/menu_bg.pngbin192 -> 0 bytes
-rwxr-xr-xlibraries/eet/doc/img/menu_bg_current.pngbin1200 -> 0 bytes
-rwxr-xr-xlibraries/eet/doc/img/menu_bg_hover.pngbin3278 -> 0 bytes
-rwxr-xr-xlibraries/eet/doc/img/menu_bg_last.pngbin637 -> 0 bytes
-rwxr-xr-xlibraries/eet/doc/img/menu_bg_unsel.pngbin1596 -> 0 bytes
20 files changed, 0 insertions, 5358 deletions
diff --git a/libraries/eet/doc/Doxyfile b/libraries/eet/doc/Doxyfile
deleted file mode 100644
index 26a32a7..0000000
--- a/libraries/eet/doc/Doxyfile
+++ /dev/null
@@ -1,1694 +0,0 @@
1# Doxyfile 1.7.3
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#---------------------------------------------------------------------------
14# Project related configuration options
15#---------------------------------------------------------------------------
16
17# This tag specifies the encoding used for all characters in the config file
18# that follow. The default is UTF-8 which is also the encoding used for all
19# text before the first occurrence of this tag. Doxygen uses libiconv (or the
20# iconv built into libc) for the transcoding. See
21# http://www.gnu.org/software/libiconv for the list of possible encodings.
22
23DOXYFILE_ENCODING = UTF-8
24
25# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
26# by quotes) that should identify the project.
27
28PROJECT_NAME = Eet
29
30# The PROJECT_NUMBER tag can be used to enter a project or revision number.
31# This could be handy for archiving the generated documentation or
32# if some version control system is used.
33
34PROJECT_NUMBER = 1.6.0-alpha
35
36# Using the PROJECT_BRIEF tag one can provide an optional one line description for a project that appears at the top of each page and should give viewer a quick idea about the purpose of the project. Keep the description short.
37
38PROJECT_BRIEF =
39
40# With the PROJECT_LOGO tag one can specify an logo or icon that is
41# included in the documentation. The maximum height of the logo should not
42# exceed 55 pixels and the maximum width should not exceed 200 pixels.
43# Doxygen will copy the logo to the output directory.
44
45PROJECT_LOGO =
46
47# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
48# base path where the generated documentation will be put.
49# If a relative path is entered, it will be relative to the location
50# where doxygen was started. If left blank the current directory will be used.
51
52OUTPUT_DIRECTORY = .
53
54# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
55# 4096 sub-directories (in 2 levels) under the output directory of each output
56# format and will distribute the generated files over these directories.
57# Enabling this option can be useful when feeding doxygen a huge amount of
58# source files, where putting all generated files in the same directory would
59# otherwise cause performance problems for the file system.
60
61CREATE_SUBDIRS = NO
62
63# The OUTPUT_LANGUAGE tag is used to specify the language in which all
64# documentation generated by doxygen is written. Doxygen will use this
65# information to generate all constant output in the proper language.
66# The default language is English, other supported languages are:
67# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,
68# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German,
69# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English
70# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian,
71# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak,
72# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.
73
74OUTPUT_LANGUAGE = English
75
76# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
77# include brief member descriptions after the members that are listed in
78# the file and class documentation (similar to JavaDoc).
79# Set to NO to disable this.
80
81BRIEF_MEMBER_DESC = YES
82
83# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
84# the brief description of a member or function before the detailed description.
85# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
86# brief descriptions will be completely suppressed.
87
88REPEAT_BRIEF = YES
89
90# This tag implements a quasi-intelligent brief description abbreviator
91# that is used to form the text in various listings. Each string
92# in this list, if found as the leading text of the brief description, will be
93# stripped from the text and the result after processing the whole list, is
94# used as the annotated text. Otherwise, the brief description is used as-is.
95# If left blank, the following values are used ("$name" is automatically
96# replaced with the name of the entity): "The $name class" "The $name widget"
97# "The $name file" "is" "provides" "specifies" "contains"
98# "represents" "a" "an" "the"
99
100ABBREVIATE_BRIEF =
101
102# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
103# Doxygen will generate a detailed section even if there is only a brief
104# description.
105
106ALWAYS_DETAILED_SEC = NO
107
108# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
109# inherited members of a class in the documentation of that class as if those
110# members were ordinary class members. Constructors, destructors and assignment
111# operators of the base classes will not be shown.
112
113INLINE_INHERITED_MEMB = NO
114
115# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
116# path before files name in the file list and in the header files. If set
117# to NO the shortest path that makes the file name unique will be used.
118
119FULL_PATH_NAMES = NO
120
121# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
122# can be used to strip a user-defined part of the path. Stripping is
123# only done if one of the specified strings matches the left-hand part of
124# the path. The tag can be used to show relative paths in the file list.
125# If left blank the directory from which doxygen is run is used as the
126# path to strip.
127
128STRIP_FROM_PATH =
129
130# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
131# the path mentioned in the documentation of a class, which tells
132# the reader which header file to include in order to use a class.
133# If left blank only the name of the header file containing the class
134# definition is used. Otherwise one should specify the include paths that
135# are normally passed to the compiler using the -I flag.
136
137STRIP_FROM_INC_PATH =
138
139# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
140# (but less readable) file names. This can be useful if your file system
141# doesn't support long names like on DOS, Mac, or CD-ROM.
142
143SHORT_NAMES = NO
144
145# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
146# will interpret the first line (until the first dot) of a JavaDoc-style
147# comment as the brief description. If set to NO, the JavaDoc
148# comments will behave just like regular Qt-style comments
149# (thus requiring an explicit @brief command for a brief description.)
150
151JAVADOC_AUTOBRIEF = YES
152
153# If the QT_AUTOBRIEF tag is set to YES then Doxygen will
154# interpret the first line (until the first dot) of a Qt-style
155# comment as the brief description. If set to NO, the comments
156# will behave just like regular Qt-style comments (thus requiring
157# an explicit \brief command for a brief description.)
158
159QT_AUTOBRIEF = NO
160
161# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
162# treat a multi-line C++ special comment block (i.e. a block of //! or ///
163# comments) as a brief description. This used to be the default behaviour.
164# The new default is to treat a multi-line C++ comment block as a detailed
165# description. Set this tag to YES if you prefer the old behaviour instead.
166
167MULTILINE_CPP_IS_BRIEF = NO
168
169# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
170# member inherits the documentation from any documented member that it
171# re-implements.
172
173INHERIT_DOCS = YES
174
175# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
176# a new page for each member. If set to NO, the documentation of a member will
177# be part of the file/class/namespace that contains it.
178
179SEPARATE_MEMBER_PAGES = NO
180
181# The TAB_SIZE tag can be used to set the number of spaces in a tab.
182# Doxygen uses this value to replace tabs by spaces in code fragments.
183
184TAB_SIZE = 8
185
186# This tag can be used to specify a number of aliases that acts
187# as commands in the documentation. An alias has the form "name=value".
188# For example adding "sideeffect=\par Side Effects:\n" will allow you to
189# put the command \sideeffect (or @sideeffect) in the documentation, which
190# will result in a user-defined paragraph with heading "Side Effects:".
191# You can put \n's in the value part of an alias to insert newlines.
192
193ALIASES =
194
195# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
196# sources only. Doxygen will then generate output that is more tailored for C.
197# For instance, some of the names that are used will be different. The list
198# of all members will be omitted, etc.
199
200OPTIMIZE_OUTPUT_FOR_C = YES
201
202# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java
203# sources only. Doxygen will then generate output that is more tailored for
204# Java. For instance, namespaces will be presented as packages, qualified
205# scopes will look different, etc.
206
207OPTIMIZE_OUTPUT_JAVA = NO
208
209# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
210# sources only. Doxygen will then generate output that is more tailored for
211# Fortran.
212
213OPTIMIZE_FOR_FORTRAN = NO
214
215# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
216# sources. Doxygen will then generate output that is tailored for
217# VHDL.
218
219OPTIMIZE_OUTPUT_VHDL = NO
220
221# Doxygen selects the parser to use depending on the extension of the files it
222# parses. With this tag you can assign which parser to use for a given extension.
223# Doxygen has a built-in mapping, but you can override or extend it using this
224# tag. The format is ext=language, where ext is a file extension, and language
225# is one of the parsers supported by doxygen: IDL, Java, Javascript, CSharp, C,
226# C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. For instance to make
227# doxygen treat .inc files as Fortran files (default is PHP), and .f files as C
228# (default is Fortran), use: inc=Fortran f=C. Note that for custom extensions
229# you also need to set FILE_PATTERNS otherwise the files are not read by doxygen.
230
231EXTENSION_MAPPING =
232
233# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
234# to include (a tag file for) the STL sources as input, then you should
235# set this tag to YES in order to let doxygen match functions declarations and
236# definitions whose arguments contain STL classes (e.g. func(std::string); v.s.
237# func(std::string) {}). This also makes the inheritance and collaboration
238# diagrams that involve STL classes more complete and accurate.
239
240BUILTIN_STL_SUPPORT = NO
241
242# If you use Microsoft's C++/CLI language, you should set this option to YES to
243# enable parsing support.
244
245CPP_CLI_SUPPORT = NO
246
247# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only.
248# Doxygen will parse them like normal C++ but will assume all classes use public
249# instead of private inheritance when no explicit protection keyword is present.
250
251SIP_SUPPORT = NO
252
253# For Microsoft's IDL there are propget and propput attributes to indicate getter
254# and setter methods for a property. Setting this option to YES (the default)
255# will make doxygen replace the get and set methods by a property in the
256# documentation. This will only work if the methods are indeed getting or
257# setting a simple type. If this is not the case, or you want to show the
258# methods anyway, you should set this option to NO.
259
260IDL_PROPERTY_SUPPORT = YES
261
262# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
263# tag is set to YES, then doxygen will reuse the documentation of the first
264# member in the group (if any) for the other members of the group. By default
265# all members of a group must be documented explicitly.
266
267DISTRIBUTE_GROUP_DOC = NO
268
269# Set the SUBGROUPING tag to YES (the default) to allow class member groups of
270# the same type (for instance a group of public functions) to be put as a
271# subgroup of that type (e.g. under the Public Functions section). Set it to
272# NO to prevent subgrouping. Alternatively, this can be done per class using
273# the \nosubgrouping command.
274
275SUBGROUPING = YES
276
277# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum
278# is documented as struct, union, or enum with the name of the typedef. So
279# typedef struct TypeS {} TypeT, will appear in the documentation as a struct
280# with name TypeT. When disabled the typedef will appear as a member of a file,
281# namespace, or class. And the struct will be named TypeS. This can typically
282# be useful for C code in case the coding convention dictates that all compound
283# types are typedef'ed and only the typedef is referenced, never the tag name.
284
285TYPEDEF_HIDES_STRUCT = NO
286
287# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to
288# determine which symbols to keep in memory and which to flush to disk.
289# When the cache is full, less often used symbols will be written to disk.
290# For small to medium size projects (<1000 input files) the default value is
291# probably good enough. For larger projects a too small cache size can cause
292# doxygen to be busy swapping symbols to and from disk most of the time
293# causing a significant performance penalty.
294# If the system has enough physical memory increasing the cache will improve the
295# performance by keeping more symbols in memory. Note that the value works on
296# a logarithmic scale so increasing the size by one will roughly double the
297# memory usage. The cache size is given by this formula:
298# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,
299# corresponding to a cache size of 2^16 = 65536 symbols
300
301SYMBOL_CACHE_SIZE = 0
302
303#---------------------------------------------------------------------------
304# Build related configuration options
305#---------------------------------------------------------------------------
306
307# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
308# documentation are documented, even if no documentation was available.
309# Private class members and static file members will be hidden unless
310# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
311
312EXTRACT_ALL = NO
313
314# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
315# will be included in the documentation.
316
317EXTRACT_PRIVATE = NO
318
319# If the EXTRACT_STATIC tag is set to YES all static members of a file
320# will be included in the documentation.
321
322EXTRACT_STATIC = NO
323
324# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
325# defined locally in source files will be included in the documentation.
326# If set to NO only classes defined in header files are included.
327
328EXTRACT_LOCAL_CLASSES = NO
329
330# This flag is only useful for Objective-C code. When set to YES local
331# methods, which are defined in the implementation section but not in
332# the interface are included in the documentation.
333# If set to NO (the default) only methods in the interface are included.
334
335EXTRACT_LOCAL_METHODS = NO
336
337# If this flag is set to YES, the members of anonymous namespaces will be
338# extracted and appear in the documentation as a namespace called
339# 'anonymous_namespace{file}', where file will be replaced with the base
340# name of the file that contains the anonymous namespace. By default
341# anonymous namespaces are hidden.
342
343EXTRACT_ANON_NSPACES = NO
344
345# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
346# undocumented members of documented classes, files or namespaces.
347# If set to NO (the default) these members will be included in the
348# various overviews, but no documentation section is generated.
349# This option has no effect if EXTRACT_ALL is enabled.
350
351HIDE_UNDOC_MEMBERS = NO
352
353# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
354# undocumented classes that are normally visible in the class hierarchy.
355# If set to NO (the default) these classes will be included in the various
356# overviews. This option has no effect if EXTRACT_ALL is enabled.
357
358HIDE_UNDOC_CLASSES = NO
359
360# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
361# friend (class|struct|union) declarations.
362# If set to NO (the default) these declarations will be included in the
363# documentation.
364
365HIDE_FRIEND_COMPOUNDS = NO
366
367# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
368# documentation blocks found inside the body of a function.
369# If set to NO (the default) these blocks will be appended to the
370# function's detailed documentation block.
371
372HIDE_IN_BODY_DOCS = NO
373
374# The INTERNAL_DOCS tag determines if documentation
375# that is typed after a \internal command is included. If the tag is set
376# to NO (the default) then the documentation will be excluded.
377# Set it to YES to include the internal documentation.
378
379INTERNAL_DOCS = NO
380
381# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
382# file names in lower-case letters. If set to YES upper-case letters are also
383# allowed. This is useful if you have classes or files whose names only differ
384# in case and if your file system supports case sensitive file names. Windows
385# and Mac users are advised to set this option to NO.
386
387CASE_SENSE_NAMES = YES
388
389# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
390# will show members with their full class and namespace scopes in the
391# documentation. If set to YES the scope will be hidden.
392
393HIDE_SCOPE_NAMES = NO
394
395# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
396# will put a list of the files that are included by a file in the documentation
397# of that file.
398
399SHOW_INCLUDE_FILES = NO
400
401# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen
402# will list include files with double quotes in the documentation
403# rather than with sharp brackets.
404
405FORCE_LOCAL_INCLUDES = NO
406
407# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
408# is inserted in the documentation for inline members.
409
410INLINE_INFO = YES
411
412# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
413# will sort the (detailed) documentation of file and class members
414# alphabetically by member name. If set to NO the members will appear in
415# declaration order.
416
417SORT_MEMBER_DOCS = NO
418
419# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
420# brief documentation of file, namespace and class members alphabetically
421# by member name. If set to NO (the default) the members will appear in
422# declaration order.
423
424SORT_BRIEF_DOCS = NO
425
426# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen
427# will sort the (brief and detailed) documentation of class members so that
428# constructors and destructors are listed first. If set to NO (the default)
429# the constructors will appear in the respective orders defined by
430# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS.
431# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO
432# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.
433
434SORT_MEMBERS_CTORS_1ST = NO
435
436# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the
437# hierarchy of group names into alphabetical order. If set to NO (the default)
438# the group names will appear in their defined order.
439
440SORT_GROUP_NAMES = NO
441
442# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
443# sorted by fully-qualified names, including namespaces. If set to
444# NO (the default), the class list will be sorted only by class name,
445# not including the namespace part.
446# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
447# Note: This option applies only to the class list, not to the
448# alphabetical list.
449
450SORT_BY_SCOPE_NAME = NO
451
452# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper type resolution of all parameters of a function it will reject a
453# match between the prototype and the implementation of a member function even if there is only one candidate or it is obvious which candidate to choose by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen
454# will still accept a match between prototype and implementation in such cases.
455
456STRICT_PROTO_MATCHING = NO
457
458# The GENERATE_TODOLIST tag can be used to enable (YES) or
459# disable (NO) the todo list. This list is created by putting \todo
460# commands in the documentation.
461
462GENERATE_TODOLIST = YES
463
464# The GENERATE_TESTLIST tag can be used to enable (YES) or
465# disable (NO) the test list. This list is created by putting \test
466# commands in the documentation.
467
468GENERATE_TESTLIST = YES
469
470# The GENERATE_BUGLIST tag can be used to enable (YES) or
471# disable (NO) the bug list. This list is created by putting \bug
472# commands in the documentation.
473
474GENERATE_BUGLIST = YES
475
476# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
477# disable (NO) the deprecated list. This list is created by putting
478# \deprecated commands in the documentation.
479
480GENERATE_DEPRECATEDLIST= YES
481
482# The ENABLED_SECTIONS tag can be used to enable conditional
483# documentation sections, marked by \if sectionname ... \endif.
484
485ENABLED_SECTIONS =
486
487# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
488# the initial value of a variable or macro consists of for it to appear in
489# the documentation. If the initializer consists of more lines than specified
490# here it will be hidden. Use a value of 0 to hide initializers completely.
491# The appearance of the initializer of individual variables and macros in the
492# documentation can be controlled using \showinitializer or \hideinitializer
493# command in the documentation regardless of this setting.
494
495MAX_INITIALIZER_LINES = 30
496
497# Set the SHOW_USED_FILES tag to NO to disable the list of files generated
498# at the bottom of the documentation of classes and structs. If set to YES the
499# list will mention the files that were used to generate the documentation.
500
501SHOW_USED_FILES = NO
502
503# If the sources in your project are distributed over multiple directories
504# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
505# in the documentation. The default is NO.
506
507SHOW_DIRECTORIES = NO
508
509# Set the SHOW_FILES tag to NO to disable the generation of the Files page.
510# This will remove the Files entry from the Quick Index and from the
511# Folder Tree View (if specified). The default is YES.
512
513SHOW_FILES = YES
514
515# Set the SHOW_NAMESPACES tag to NO to disable the generation of the
516# Namespaces page.
517# This will remove the Namespaces entry from the Quick Index
518# and from the Folder Tree View (if specified). The default is YES.
519
520SHOW_NAMESPACES = YES
521
522# The FILE_VERSION_FILTER tag can be used to specify a program or script that
523# doxygen should invoke to get the current version for each file (typically from
524# the version control system). Doxygen will invoke the program by executing (via
525# popen()) the command <command> <input-file>, where <command> is the value of
526# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
527# provided by doxygen. Whatever the program writes to standard output
528# is used as the file version. See the manual for examples.
529
530FILE_VERSION_FILTER =
531
532# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
533# by doxygen. The layout file controls the global structure of the generated
534# output files in an output format independent way. The create the layout file
535# that represents doxygen's defaults, run doxygen with the -l option.
536# You can optionally specify a file name after the option, if omitted
537# DoxygenLayout.xml will be used as the name of the layout file.
538
539LAYOUT_FILE =
540
541#---------------------------------------------------------------------------
542# configuration options related to warning and progress messages
543#---------------------------------------------------------------------------
544
545# The QUIET tag can be used to turn on/off the messages that are generated
546# by doxygen. Possible values are YES and NO. If left blank NO is used.
547
548QUIET = NO
549
550# The WARNINGS tag can be used to turn on/off the warning messages that are
551# generated by doxygen. Possible values are YES and NO. If left blank
552# NO is used.
553
554WARNINGS = YES
555
556# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
557# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
558# automatically be disabled.
559
560WARN_IF_UNDOCUMENTED = YES
561
562# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
563# potential errors in the documentation, such as not documenting some
564# parameters in a documented function, or documenting parameters that
565# don't exist or using markup commands wrongly.
566
567WARN_IF_DOC_ERROR = YES
568
569# The WARN_NO_PARAMDOC option can be enabled to get warnings for
570# functions that are documented, but have no documentation for their parameters
571# or return value. If set to NO (the default) doxygen will only warn about
572# wrong or incomplete parameter documentation, but not about the absence of
573# documentation.
574
575WARN_NO_PARAMDOC = YES
576
577# The WARN_FORMAT tag determines the format of the warning messages that
578# doxygen can produce. The string should contain the $file, $line, and $text
579# tags, which will be replaced by the file and line number from which the
580# warning originated and the warning text. Optionally the format may contain
581# $version, which will be replaced by the version of the file (if it could
582# be obtained via FILE_VERSION_FILTER)
583
584WARN_FORMAT = "$file:$line: $text"
585
586# The WARN_LOGFILE tag can be used to specify a file to which warning
587# and error messages should be written. If left blank the output is written
588# to stderr.
589
590WARN_LOGFILE =
591
592#---------------------------------------------------------------------------
593# configuration options related to the input files
594#---------------------------------------------------------------------------
595
596# The INPUT tag can be used to specify the files and/or directories that contain
597# documented source files. You may enter file names like "myfile.cpp" or
598# directories like "/usr/src/myproject". Separate the files or directories
599# with spaces.
600
601INPUT = ./eet.dox \
602 ./examples.dox \
603 ../src/lib
604
605# This tag can be used to specify the character encoding of the source files
606# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is
607# also the default input encoding. Doxygen uses libiconv (or the iconv built
608# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for
609# the list of possible encodings.
610
611INPUT_ENCODING = UTF-8
612
613# If the value of the INPUT tag contains directories, you can use the
614# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
615# and *.h) to filter out the source-files in the directories. If left
616# blank the following patterns are tested:
617# *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh
618# *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py
619# *.f90 *.f *.for *.vhd *.vhdl
620
621FILE_PATTERNS = *.c \
622 *.h
623
624# The RECURSIVE tag can be used to turn specify whether or not subdirectories
625# should be searched for input files as well. Possible values are YES and NO.
626# If left blank NO is used.
627
628RECURSIVE = YES
629
630# The EXCLUDE tag can be used to specify files and/or directories that should
631# excluded from the INPUT source files. This way you can easily exclude a
632# subdirectory from a directory tree whose root is specified with the INPUT tag.
633
634EXCLUDE = ../src/lib/eet_amalgamation.c
635
636# The EXCLUDE_SYMLINKS tag can be used select whether or not files or
637# directories that are symbolic links (a Unix file system feature) are excluded
638# from the input.
639
640EXCLUDE_SYMLINKS = NO
641
642# If the value of the INPUT tag contains directories, you can use the
643# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
644# certain files from those directories. Note that the wildcards are matched
645# against the file with absolute path, so to exclude all test directories
646# for example use the pattern */test/*
647
648EXCLUDE_PATTERNS =
649
650# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
651# (namespaces, classes, functions, etc.) that should be excluded from the
652# output. The symbol name can be a fully qualified name, a word, or if the
653# wildcard * is used, a substring. Examples: ANamespace, AClass,
654# AClass::ANamespace, ANamespace::*Test
655
656EXCLUDE_SYMBOLS =
657
658# The EXAMPLE_PATH tag can be used to specify one or more files or
659# directories that contain example code fragments that are included (see
660# the \include command).
661
662EXAMPLE_PATH = ../src/examples
663
664# If the value of the EXAMPLE_PATH tag contains directories, you can use the
665# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
666# and *.h) to filter out the source-files in the directories. If left
667# blank all files are included.
668
669EXAMPLE_PATTERNS = *.c,*.h,*.x
670
671# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
672# searched for input files to be used with the \include or \dontinclude
673# commands irrespective of the value of the RECURSIVE tag.
674# Possible values are YES and NO. If left blank NO is used.
675
676EXAMPLE_RECURSIVE = NO
677
678# The IMAGE_PATH tag can be used to specify one or more files or
679# directories that contain image that are included in the documentation (see
680# the \image command).
681
682IMAGE_PATH = ../doc/img
683
684# The INPUT_FILTER tag can be used to specify a program that doxygen should
685# invoke to filter for each input file. Doxygen will invoke the filter program
686# by executing (via popen()) the command <filter> <input-file>, where <filter>
687# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
688# input file. Doxygen will then use the output that the filter program writes
689# to standard output.
690# If FILTER_PATTERNS is specified, this tag will be
691# ignored.
692
693INPUT_FILTER =
694
695# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
696# basis.
697# Doxygen will compare the file name with each pattern and apply the
698# filter if there is a match.
699# The filters are a list of the form:
700# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
701# info on how filters are used. If FILTER_PATTERNS is empty or if
702# non of the patterns match the file name, INPUT_FILTER is applied.
703
704FILTER_PATTERNS =
705
706# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
707# INPUT_FILTER) will be used to filter the input files when producing source
708# files to browse (i.e. when SOURCE_BROWSER is set to YES).
709
710FILTER_SOURCE_FILES = NO
711
712# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
713# pattern. A pattern will override the setting for FILTER_PATTERN (if any)
714# and it is also possible to disable source filtering for a specific pattern
715# using *.ext= (so without naming a filter). This option only has effect when
716# FILTER_SOURCE_FILES is enabled.
717
718FILTER_SOURCE_PATTERNS =
719
720#---------------------------------------------------------------------------
721# configuration options related to source browsing
722#---------------------------------------------------------------------------
723
724# If the SOURCE_BROWSER tag is set to YES then a list of source files will
725# be generated. Documented entities will be cross-referenced with these sources.
726# Note: To get rid of all source code in the generated output, make sure also
727# VERBATIM_HEADERS is set to NO.
728
729SOURCE_BROWSER = NO
730
731# Setting the INLINE_SOURCES tag to YES will include the body
732# of functions and classes directly in the documentation.
733
734INLINE_SOURCES = NO
735
736# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
737# doxygen to hide any special comment blocks from generated source code
738# fragments. Normal C and C++ comments will always remain visible.
739
740STRIP_CODE_COMMENTS = YES
741
742# If the REFERENCED_BY_RELATION tag is set to YES
743# then for each documented function all documented
744# functions referencing it will be listed.
745
746REFERENCED_BY_RELATION = YES
747
748# If the REFERENCES_RELATION tag is set to YES
749# then for each documented function all documented entities
750# called/used by that function will be listed.
751
752REFERENCES_RELATION = YES
753
754# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
755# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
756# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
757# link to the source code.
758# Otherwise they will link to the documentation.
759
760REFERENCES_LINK_SOURCE = YES
761
762# If the USE_HTAGS tag is set to YES then the references to source code
763# will point to the HTML generated by the htags(1) tool instead of doxygen
764# built-in source browser. The htags tool is part of GNU's global source
765# tagging system (see http://www.gnu.org/software/global/global.html). You
766# will need version 4.8.6 or higher.
767
768USE_HTAGS = NO
769
770# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
771# will generate a verbatim copy of the header file for each class for
772# which an include is specified. Set to NO to disable this.
773
774VERBATIM_HEADERS = NO
775
776#---------------------------------------------------------------------------
777# configuration options related to the alphabetical class index
778#---------------------------------------------------------------------------
779
780# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
781# of all compounds will be generated. Enable this if the project
782# contains a lot of classes, structs, unions or interfaces.
783
784ALPHABETICAL_INDEX = YES
785
786# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
787# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
788# in which this list will be split (can be a number in the range [1..20])
789
790COLS_IN_ALPHA_INDEX = 2
791
792# In case all classes in a project start with a common prefix, all
793# classes will be put under the same header in the alphabetical index.
794# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
795# should be ignored while generating the index headers.
796
797IGNORE_PREFIX = eet_ \
798 _eet_ \
799 Eet_ \
800 _Eet_ \
801 EET_ \
802 _EET_
803
804#---------------------------------------------------------------------------
805# configuration options related to the HTML output
806#---------------------------------------------------------------------------
807
808# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
809# generate HTML output.
810
811GENERATE_HTML = YES
812
813# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
814# If a relative path is entered the value of OUTPUT_DIRECTORY will be
815# put in front of it. If left blank `html' will be used as the default path.
816
817HTML_OUTPUT = html
818
819# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
820# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
821# doxygen will generate files with .html extension.
822
823HTML_FILE_EXTENSION = .html
824
825# The HTML_HEADER tag can be used to specify a personal HTML header for
826# each generated HTML page. If it is left blank doxygen will generate a
827# standard header.
828
829HTML_HEADER = ./head.html
830
831# The HTML_FOOTER tag can be used to specify a personal HTML footer for
832# each generated HTML page. If it is left blank doxygen will generate a
833# standard footer.
834
835HTML_FOOTER = ./foot.html
836
837# The HTML_STYLESHEET tag can be used to specify a user-defined cascading
838# style sheet that is used by each HTML page. It can be used to
839# fine-tune the look of the HTML output. If the tag is left blank doxygen
840# will generate a default style sheet. Note that doxygen will try to copy
841# the style sheet file to the HTML output directory, so don't put your own
842# stylesheet in the HTML output directory as well, or it will be erased!
843
844HTML_STYLESHEET = ./e.css
845
846# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output.
847# Doxygen will adjust the colors in the stylesheet and background images
848# according to this color. Hue is specified as an angle on a colorwheel,
849# see http://en.wikipedia.org/wiki/Hue for more information.
850# For instance the value 0 represents red, 60 is yellow, 120 is green,
851# 180 is cyan, 240 is blue, 300 purple, and 360 is red again.
852# The allowed range is 0 to 359.
853
854HTML_COLORSTYLE_HUE = 220
855
856# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of
857# the colors in the HTML output. For a value of 0 the output will use
858# grayscales only. A value of 255 will produce the most vivid colors.
859
860HTML_COLORSTYLE_SAT = 100
861
862# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to
863# the luminance component of the colors in the HTML output. Values below
864# 100 gradually make the output lighter, whereas values above 100 make
865# the output darker. The value divided by 100 is the actual gamma applied,
866# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2,
867# and 100 does not change the gamma.
868
869HTML_COLORSTYLE_GAMMA = 80
870
871# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
872# page will contain the date and time when the page was generated. Setting
873# this to NO can help when comparing the output of multiple runs.
874
875HTML_TIMESTAMP = YES
876
877# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
878# files or namespaces will be aligned in HTML using tables. If set to
879# NO a bullet list will be used.
880
881HTML_ALIGN_MEMBERS = YES
882
883# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
884# documentation will contain sections that can be hidden and shown after the
885# page has loaded. For this to work a browser that supports
886# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox
887# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).
888
889HTML_DYNAMIC_SECTIONS = YES
890
891# If the GENERATE_DOCSET tag is set to YES, additional index files
892# will be generated that can be used as input for Apple's Xcode 3
893# integrated development environment, introduced with OSX 10.5 (Leopard).
894# To create a documentation set, doxygen will generate a Makefile in the
895# HTML output directory. Running make will produce the docset in that
896# directory and running "make install" will install the docset in
897# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
898# it at startup.
899# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
900# for more information.
901
902GENERATE_DOCSET = YES
903
904# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the
905# feed. A documentation feed provides an umbrella under which multiple
906# documentation sets from a single provider (such as a company or product suite)
907# can be grouped.
908
909DOCSET_FEEDNAME = "Doxygen generated docs"
910
911# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that
912# should uniquely identify the documentation set bundle. This should be a
913# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen
914# will append .docset to the name.
915
916DOCSET_BUNDLE_ID = org.enlightenment.Eet
917
918# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify
919# the documentation publisher. This should be a reverse domain-name style
920# string, e.g. com.mycompany.MyDocSet.documentation.
921
922DOCSET_PUBLISHER_ID = org.enlightenment.Eet
923
924# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.
925
926DOCSET_PUBLISHER_NAME = Enlightenment
927
928# If the GENERATE_HTMLHELP tag is set to YES, additional index files
929# will be generated that can be used as input for tools like the
930# Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
931# of the generated HTML documentation.
932
933GENERATE_HTMLHELP = YES
934
935# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
936# be used to specify the file name of the resulting .chm file. You
937# can add a path in front of the file if the result should not be
938# written to the html output directory.
939
940CHM_FILE =
941
942# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
943# be used to specify the location (absolute path including file name) of
944# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
945# the HTML help compiler on the generated index.hhp.
946
947HHC_LOCATION =
948
949# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
950# controls if a separate .chi index file is generated (YES) or that
951# it should be included in the master .chm file (NO).
952
953GENERATE_CHI = NO
954
955# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING
956# is used to encode HtmlHelp index (hhk), content (hhc) and project file
957# content.
958
959CHM_INDEX_ENCODING =
960
961# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
962# controls whether a binary table of contents is generated (YES) or a
963# normal table of contents (NO) in the .chm file.
964
965BINARY_TOC = NO
966
967# The TOC_EXPAND flag can be set to YES to add extra items for group members
968# to the contents of the HTML help documentation and to the tree view.
969
970TOC_EXPAND = NO
971
972# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
973# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated
974# that can be used as input for Qt's qhelpgenerator to generate a
975# Qt Compressed Help (.qch) of the generated HTML documentation.
976
977GENERATE_QHP = NO
978
979# If the QHG_LOCATION tag is specified, the QCH_FILE tag can
980# be used to specify the file name of the resulting .qch file.
981# The path specified is relative to the HTML output folder.
982
983QCH_FILE =
984
985# The QHP_NAMESPACE tag specifies the namespace to use when generating
986# Qt Help Project output. For more information please see
987# http://doc.trolltech.com/qthelpproject.html#namespace
988
989QHP_NAMESPACE = org.enlightenment.Eet
990
991# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating
992# Qt Help Project output. For more information please see
993# http://doc.trolltech.com/qthelpproject.html#virtual-folders
994
995QHP_VIRTUAL_FOLDER = doc
996
997# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to
998# add. For more information please see
999# http://doc.trolltech.com/qthelpproject.html#custom-filters
1000
1001QHP_CUST_FILTER_NAME =
1002
1003# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the
1004# custom filter to add. For more information please see
1005# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">
1006# Qt Help Project / Custom Filters</a>.
1007
1008QHP_CUST_FILTER_ATTRS =
1009
1010# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
1011# project's
1012# filter section matches.
1013# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">
1014# Qt Help Project / Filter Attributes</a>.
1015
1016QHP_SECT_FILTER_ATTRS =
1017
1018# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can
1019# be used to specify the location of Qt's qhelpgenerator.
1020# If non-empty doxygen will try to run qhelpgenerator on the generated
1021# .qhp file.
1022
1023QHG_LOCATION =
1024
1025# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files
1026# will be generated, which together with the HTML files, form an Eclipse help
1027# plugin. To install this plugin and make it available under the help contents
1028# menu in Eclipse, the contents of the directory containing the HTML and XML
1029# files needs to be copied into the plugins directory of eclipse. The name of
1030# the directory within the plugins directory should be the same as
1031# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before
1032# the help appears.
1033
1034GENERATE_ECLIPSEHELP = NO
1035
1036# A unique identifier for the eclipse help plugin. When installing the plugin
1037# the directory name containing the HTML and XML files should also have
1038# this name.
1039
1040ECLIPSE_DOC_ID = org.enlightenment.Eet
1041
1042# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
1043# top of each HTML page. The value NO (the default) enables the index and
1044# the value YES disables it.
1045
1046DISABLE_INDEX = YES
1047
1048# This tag can be used to set the number of enum values (range [0,1..20])
1049# that doxygen will group on one line in the generated HTML documentation.
1050# Note that a value of 0 will completely suppress the enum values from appearing in the overview section.
1051
1052ENUM_VALUES_PER_LINE = 1
1053
1054# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1055# structure should be generated to display hierarchical information.
1056# If the tag value is set to YES, a side panel will be generated
1057# containing a tree-like index structure (just like the one that
1058# is generated for HTML Help). For this to work a browser that supports
1059# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).
1060# Windows users are probably better off using the HTML help feature.
1061
1062GENERATE_TREEVIEW = NO
1063
1064# By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories,
1065# and Class Hierarchy pages using a tree view instead of an ordered list.
1066
1067USE_INLINE_TREES = NO
1068
1069# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
1070# used to set the initial width (in pixels) of the frame in which the tree
1071# is shown.
1072
1073TREEVIEW_WIDTH = 250
1074
1075# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open
1076# links to external symbols imported via tag files in a separate window.
1077
1078EXT_LINKS_IN_WINDOW = NO
1079
1080# Use this tag to change the font size of Latex formulas included
1081# as images in the HTML documentation. The default is 10. Note that
1082# when you change the font size after a successful doxygen run you need
1083# to manually remove any form_*.png images from the HTML output directory
1084# to force them to be regenerated.
1085
1086FORMULA_FONTSIZE = 10
1087
1088# Use the FORMULA_TRANPARENT tag to determine whether or not the images
1089# generated for formulas are transparent PNGs. Transparent PNGs are
1090# not supported properly for IE 6.0, but are supported on all modern browsers.
1091# Note that when changing this option you need to delete any form_*.png files
1092# in the HTML output before the changes have effect.
1093
1094FORMULA_TRANSPARENT = YES
1095
1096# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax
1097# (see http://www.mathjax.org) which uses client side Javascript for the
1098# rendering instead of using prerendered bitmaps. Use this if you do not
1099# have LaTeX installed or if you want to formulas look prettier in the HTML
1100# output. When enabled you also need to install MathJax separately and
1101# configure the path to it using the MATHJAX_RELPATH option.
1102
1103USE_MATHJAX = NO
1104
1105# When MathJax is enabled you need to specify the location relative to the
1106# HTML output directory using the MATHJAX_RELPATH option. The destination
1107# directory should contain the MathJax.js script. For instance, if the mathjax
1108# directory is located at the same level as the HTML output directory, then
1109# MATHJAX_RELPATH should be ../mathjax. The default value points to the mathjax.org site, so you can quickly see the result without installing
1110# MathJax, but it is strongly recommended to install a local copy of MathJax
1111# before deployment.
1112
1113MATHJAX_RELPATH = http://www.mathjax.org/mathjax
1114
1115# When the SEARCHENGINE tag is enabled doxygen will generate a search box
1116# for the HTML output. The underlying search engine uses javascript
1117# and DHTML and should work on any modern browser. Note that when using
1118# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets
1119# (GENERATE_DOCSET) there is already a search function so this one should
1120# typically be disabled. For large projects the javascript based search engine
1121# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.
1122
1123SEARCHENGINE = NO
1124
1125# When the SERVER_BASED_SEARCH tag is enabled the search engine will be
1126# implemented using a PHP enabled web server instead of at the web client
1127# using Javascript. Doxygen will generate the search PHP script and index
1128# file to put on the web server. The advantage of the server
1129# based approach is that it scales better to large projects and allows
1130# full text search. The disadvantages are that it is more difficult to setup
1131# and does not have live searching capabilities.
1132
1133SERVER_BASED_SEARCH = NO
1134
1135#---------------------------------------------------------------------------
1136# configuration options related to the LaTeX output
1137#---------------------------------------------------------------------------
1138
1139# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
1140# generate Latex output.
1141
1142GENERATE_LATEX = YES
1143
1144# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
1145# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1146# put in front of it. If left blank `latex' will be used as the default path.
1147
1148LATEX_OUTPUT = latex
1149
1150# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
1151# invoked. If left blank `latex' will be used as the default command name.
1152# Note that when enabling USE_PDFLATEX this option is only used for
1153# generating bitmaps for formulas in the HTML output, but not in the
1154# Makefile that is written to the output directory.
1155
1156LATEX_CMD_NAME = latex
1157
1158# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
1159# generate index for LaTeX. If left blank `makeindex' will be used as the
1160# default command name.
1161
1162MAKEINDEX_CMD_NAME = makeindex
1163
1164# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
1165# LaTeX documents. This may be useful for small projects and may help to
1166# save some trees in general.
1167
1168COMPACT_LATEX = NO
1169
1170# The PAPER_TYPE tag can be used to set the paper type that is used
1171# by the printer. Possible values are: a4, letter, legal and
1172# executive. If left blank a4wide will be used.
1173
1174PAPER_TYPE = a4wide
1175
1176# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
1177# packages that should be included in the LaTeX output.
1178
1179EXTRA_PACKAGES =
1180
1181# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
1182# the generated latex document. The header should contain everything until
1183# the first chapter. If it is left blank doxygen will generate a
1184# standard header. Notice: only use this tag if you know what you are doing!
1185
1186LATEX_HEADER =
1187
1188# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
1189# is prepared for conversion to pdf (using ps2pdf). The pdf file will
1190# contain links (just like the HTML output) instead of page references
1191# This makes the output suitable for online browsing using a pdf viewer.
1192
1193PDF_HYPERLINKS = YES
1194
1195# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
1196# plain latex in the generated Makefile. Set this option to YES to get a
1197# higher quality PDF documentation.
1198
1199USE_PDFLATEX = YES
1200
1201# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
1202# command to the generated LaTeX files. This will instruct LaTeX to keep
1203# running if errors occur, instead of asking the user for help.
1204# This option is also used when generating formulas in HTML.
1205
1206LATEX_BATCHMODE = NO
1207
1208# If LATEX_HIDE_INDICES is set to YES then doxygen will not
1209# include the index chapters (such as File Index, Compound Index, etc.)
1210# in the output.
1211
1212LATEX_HIDE_INDICES = NO
1213
1214# If LATEX_SOURCE_CODE is set to YES then doxygen will include
1215# source code with syntax highlighting in the LaTeX output.
1216# Note that which sources are shown also depends on other settings
1217# such as SOURCE_BROWSER.
1218
1219LATEX_SOURCE_CODE = NO
1220
1221#---------------------------------------------------------------------------
1222# configuration options related to the RTF output
1223#---------------------------------------------------------------------------
1224
1225# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
1226# The RTF output is optimized for Word 97 and may not look very pretty with
1227# other RTF readers or editors.
1228
1229GENERATE_RTF = NO
1230
1231# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
1232# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1233# put in front of it. If left blank `rtf' will be used as the default path.
1234
1235RTF_OUTPUT = rtf
1236
1237# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
1238# RTF documents. This may be useful for small projects and may help to
1239# save some trees in general.
1240
1241COMPACT_RTF = NO
1242
1243# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
1244# will contain hyperlink fields. The RTF file will
1245# contain links (just like the HTML output) instead of page references.
1246# This makes the output suitable for online browsing using WORD or other
1247# programs which support those fields.
1248# Note: wordpad (write) and others do not support links.
1249
1250RTF_HYPERLINKS = NO
1251
1252# Load stylesheet definitions from file. Syntax is similar to doxygen's
1253# config file, i.e. a series of assignments. You only have to provide
1254# replacements, missing definitions are set to their default value.
1255
1256RTF_STYLESHEET_FILE =
1257
1258# Set optional variables used in the generation of an rtf document.
1259# Syntax is similar to doxygen's config file.
1260
1261RTF_EXTENSIONS_FILE =
1262
1263#---------------------------------------------------------------------------
1264# configuration options related to the man page output
1265#---------------------------------------------------------------------------
1266
1267# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
1268# generate man pages
1269
1270GENERATE_MAN = NO
1271
1272# The MAN_OUTPUT tag is used to specify where the man pages will be put.
1273# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1274# put in front of it. If left blank `man' will be used as the default path.
1275
1276MAN_OUTPUT = man
1277
1278# The MAN_EXTENSION tag determines the extension that is added to
1279# the generated man pages (default is the subroutine's section .3)
1280
1281MAN_EXTENSION = .3
1282
1283# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
1284# then it will generate one additional man file for each entity
1285# documented in the real man page(s). These additional files
1286# only source the real man page, but without them the man command
1287# would be unable to find the correct page. The default is NO.
1288
1289MAN_LINKS = YES
1290
1291#---------------------------------------------------------------------------
1292# configuration options related to the XML output
1293#---------------------------------------------------------------------------
1294
1295# If the GENERATE_XML tag is set to YES Doxygen will
1296# generate an XML file that captures the structure of
1297# the code including all documentation.
1298
1299GENERATE_XML = NO
1300
1301# The XML_OUTPUT tag is used to specify where the XML pages will be put.
1302# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1303# put in front of it. If left blank `xml' will be used as the default path.
1304
1305XML_OUTPUT = xml
1306
1307# The XML_SCHEMA tag can be used to specify an XML schema,
1308# which can be used by a validating XML parser to check the
1309# syntax of the XML files.
1310
1311XML_SCHEMA =
1312
1313# The XML_DTD tag can be used to specify an XML DTD,
1314# which can be used by a validating XML parser to check the
1315# syntax of the XML files.
1316
1317XML_DTD =
1318
1319# If the XML_PROGRAMLISTING tag is set to YES Doxygen will
1320# dump the program listings (including syntax highlighting
1321# and cross-referencing information) to the XML output. Note that
1322# enabling this will significantly increase the size of the XML output.
1323
1324XML_PROGRAMLISTING = YES
1325
1326#---------------------------------------------------------------------------
1327# configuration options for the AutoGen Definitions output
1328#---------------------------------------------------------------------------
1329
1330# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
1331# generate an AutoGen Definitions (see autogen.sf.net) file
1332# that captures the structure of the code including all
1333# documentation. Note that this feature is still experimental
1334# and incomplete at the moment.
1335
1336GENERATE_AUTOGEN_DEF = NO
1337
1338#---------------------------------------------------------------------------
1339# configuration options related to the Perl module output
1340#---------------------------------------------------------------------------
1341
1342# If the GENERATE_PERLMOD tag is set to YES Doxygen will
1343# generate a Perl module file that captures the structure of
1344# the code including all documentation. Note that this
1345# feature is still experimental and incomplete at the
1346# moment.
1347
1348GENERATE_PERLMOD = NO
1349
1350# If the PERLMOD_LATEX tag is set to YES Doxygen will generate
1351# the necessary Makefile rules, Perl scripts and LaTeX code to be able
1352# to generate PDF and DVI output from the Perl module output.
1353
1354PERLMOD_LATEX = NO
1355
1356# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
1357# nicely formatted so it can be parsed by a human reader.
1358# This is useful
1359# if you want to understand what is going on.
1360# On the other hand, if this
1361# tag is set to NO the size of the Perl module output will be much smaller
1362# and Perl will parse it just the same.
1363
1364PERLMOD_PRETTY = YES
1365
1366# The names of the make variables in the generated doxyrules.make file
1367# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
1368# This is useful so different doxyrules.make files included by the same
1369# Makefile don't overwrite each other's variables.
1370
1371PERLMOD_MAKEVAR_PREFIX =
1372
1373#---------------------------------------------------------------------------
1374# Configuration options related to the preprocessor
1375#---------------------------------------------------------------------------
1376
1377# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
1378# evaluate all C-preprocessor directives found in the sources and include
1379# files.
1380
1381ENABLE_PREPROCESSING = YES
1382
1383# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
1384# names in the source code. If set to NO (the default) only conditional
1385# compilation will be performed. Macro expansion can be done in a controlled
1386# way by setting EXPAND_ONLY_PREDEF to YES.
1387
1388MACRO_EXPANSION = YES
1389
1390# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
1391# then the macro expansion is limited to the macros specified with the
1392# PREDEFINED and EXPAND_AS_DEFINED tags.
1393
1394EXPAND_ONLY_PREDEF = YES
1395
1396# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
1397# in the INCLUDE_PATH (see below) will be search if a #include is found.
1398
1399SEARCH_INCLUDES = NO
1400
1401# The INCLUDE_PATH tag can be used to specify one or more directories that
1402# contain include files that are not input files but should be processed by
1403# the preprocessor.
1404
1405INCLUDE_PATH =
1406
1407# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
1408# patterns (like *.h and *.hpp) to filter out the header-files in the
1409# directories. If left blank, the patterns specified with FILE_PATTERNS will
1410# be used.
1411
1412INCLUDE_FILE_PATTERNS =
1413
1414# The PREDEFINED tag can be used to specify one or more macro names that
1415# are defined before the preprocessor is started (similar to the -D option of
1416# gcc). The argument of the tag is a list of macros of the form: name
1417# or name=definition (no spaces). If the definition and the = are
1418# omitted =1 is assumed. To prevent a macro definition from being
1419# undefined via #undef or recursively expanded use the := operator
1420# instead of the = operator.
1421
1422PREDEFINED = EINA_MAGIC_DEBUG \
1423 __UNUSED__= \
1424 EINA_ARG_NONNULL()= \
1425 EINA_MALLOC= \
1426 EINA_WARN_UNUSED_RESULT= \
1427 EAPI= \
1428 EINA_PURE= \
1429 EINA_CONST=
1430
1431# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
1432# this tag can be used to specify a list of macro names that should be expanded.
1433# The macro definition that is found in the sources will be used.
1434# Use the PREDEFINED tag if you want to use a different macro definition that overrules the definition found in the source code.
1435
1436EXPAND_AS_DEFINED =
1437
1438# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
1439# doxygen's preprocessor will remove all references to function-like macros
1440# that are alone on a line, have an all uppercase name, and do not end with a
1441# semicolon, because these will confuse the parser if not removed.
1442
1443SKIP_FUNCTION_MACROS = YES
1444
1445#---------------------------------------------------------------------------
1446# Configuration::additions related to external references
1447#---------------------------------------------------------------------------
1448
1449# The TAGFILES option can be used to specify one or more tagfiles.
1450# Optionally an initial location of the external documentation
1451# can be added for each tagfile. The format of a tag file without
1452# this location is as follows:
1453#
1454# TAGFILES = file1 file2 ...
1455# Adding location for the tag files is done as follows:
1456#
1457# TAGFILES = file1=loc1 "file2 = loc2" ...
1458# where "loc1" and "loc2" can be relative or absolute paths or
1459# URLs. If a location is present for each tag, the installdox tool
1460# does not have to be run to correct the links.
1461# Note that each tag file must have a unique name
1462# (where the name does NOT include the path)
1463# If a tag file is not located in the directory in which doxygen
1464# is run, you must also specify the path to the tagfile here.
1465
1466TAGFILES =
1467
1468# When a file name is specified after GENERATE_TAGFILE, doxygen will create
1469# a tag file that is based on the input files it reads.
1470
1471GENERATE_TAGFILE =
1472
1473# If the ALLEXTERNALS tag is set to YES all external classes will be listed
1474# in the class index. If set to NO only the inherited external classes
1475# will be listed.
1476
1477ALLEXTERNALS = NO
1478
1479# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1480# in the modules index. If set to NO, only the current project's groups will
1481# be listed.
1482
1483EXTERNAL_GROUPS = YES
1484
1485# The PERL_PATH should be the absolute path and name of the perl script
1486# interpreter (i.e. the result of `which perl').
1487
1488PERL_PATH = /usr/bin/perl
1489
1490#---------------------------------------------------------------------------
1491# Configuration options related to the dot tool
1492#---------------------------------------------------------------------------
1493
1494# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1495# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
1496# or super classes. Setting the tag to NO turns the diagrams off. Note that
1497# this option also works with HAVE_DOT disabled, but it is recommended to
1498# install and use dot, since it yields more powerful graphs.
1499
1500CLASS_DIAGRAMS = NO
1501
1502# You can define message sequence charts within doxygen comments using the \msc
1503# command. Doxygen will then run the mscgen tool (see
1504# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the
1505# documentation. The MSCGEN_PATH tag allows you to specify the directory where
1506# the mscgen tool resides. If left empty the tool is assumed to be found in the
1507# default search path.
1508
1509MSCGEN_PATH =
1510
1511# If set to YES, the inheritance and collaboration graphs will hide
1512# inheritance and usage relations if the target is undocumented
1513# or is not a class.
1514
1515HIDE_UNDOC_RELATIONS = YES
1516
1517# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1518# available from the path. This tool is part of Graphviz, a graph visualization
1519# toolkit from AT&T and Lucent Bell Labs. The other options in this section
1520# have no effect if this option is set to NO (the default)
1521
1522HAVE_DOT = NO
1523
1524# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is
1525# allowed to run in parallel. When set to 0 (the default) doxygen will
1526# base this on the number of processors available in the system. You can set it
1527# explicitly to a value larger than 0 to get control over the balance
1528# between CPU load and processing speed.
1529
1530DOT_NUM_THREADS = 0
1531
1532# By default doxygen will write a font called Helvetica to the output
1533# directory and reference it in all dot files that doxygen generates.
1534# When you want a differently looking font you can specify the font name
1535# using DOT_FONTNAME. You need to make sure dot is able to find the font,
1536# which can be done by putting it in a standard location or by setting the
1537# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory
1538# containing the font.
1539
1540DOT_FONTNAME = Helvetica
1541
1542# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs.
1543# The default size is 10pt.
1544
1545DOT_FONTSIZE = 10
1546
1547# By default doxygen will tell dot to use the output directory to look for the
1548# FreeSans.ttf font (which doxygen will put there itself). If you specify a
1549# different font using DOT_FONTNAME you can set the path where dot
1550# can find it using this tag.
1551
1552DOT_FONTPATH =
1553
1554# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
1555# will generate a graph for each documented class showing the direct and
1556# indirect inheritance relations. Setting this tag to YES will force the
1557# the CLASS_DIAGRAMS tag to NO.
1558
1559CLASS_GRAPH = NO
1560
1561# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
1562# will generate a graph for each documented class showing the direct and
1563# indirect implementation dependencies (inheritance, containment, and
1564# class references variables) of the class with other documented classes.
1565
1566COLLABORATION_GRAPH = NO
1567
1568# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
1569# will generate a graph for groups, showing the direct groups dependencies
1570
1571GROUP_GRAPHS = YES
1572
1573# If the UML_LOOK tag is set to YES doxygen will generate inheritance and
1574# collaboration diagrams in a style similar to the OMG's Unified Modeling
1575# Language.
1576
1577UML_LOOK = NO
1578
1579# If set to YES, the inheritance and collaboration graphs will show the
1580# relations between templates and their instances.
1581
1582TEMPLATE_RELATIONS = NO
1583
1584# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
1585# tags are set to YES then doxygen will generate a graph for each documented
1586# file showing the direct and indirect include dependencies of the file with
1587# other documented files.
1588
1589INCLUDE_GRAPH = NO
1590
1591# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
1592# HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1593# documented header file showing the documented files that directly or
1594# indirectly include this file.
1595
1596INCLUDED_BY_GRAPH = NO
1597
1598# If the CALL_GRAPH and HAVE_DOT options are set to YES then
1599# doxygen will generate a call dependency graph for every global function
1600# or class method. Note that enabling this option will significantly increase
1601# the time of a run. So in most cases it will be better to enable call graphs
1602# for selected functions only using the \callgraph command.
1603
1604CALL_GRAPH = NO
1605
1606# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then
1607# doxygen will generate a caller dependency graph for every global function
1608# or class method. Note that enabling this option will significantly increase
1609# the time of a run. So in most cases it will be better to enable caller
1610# graphs for selected functions only using the \callergraph command.
1611
1612CALLER_GRAPH = NO
1613
1614# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
1615# will generate a graphical hierarchy of all classes instead of a textual one.
1616
1617GRAPHICAL_HIERARCHY = NO
1618
1619# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
1620# then doxygen will show the dependencies a directory has on other directories
1621# in a graphical way. The dependency relations are determined by the #include
1622# relations between the files in the directories.
1623
1624DIRECTORY_GRAPH = YES
1625
1626# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1627# generated by dot. Possible values are png, svg, gif or svg.
1628# If left blank png will be used.
1629
1630DOT_IMAGE_FORMAT = png
1631
1632# The tag DOT_PATH can be used to specify the path where the dot tool can be
1633# found. If left blank, it is assumed the dot tool can be found in the path.
1634
1635DOT_PATH =
1636
1637# The DOTFILE_DIRS tag can be used to specify one or more directories that
1638# contain dot files that are included in the documentation (see the
1639# \dotfile command).
1640
1641DOTFILE_DIRS =
1642
1643# The MSCFILE_DIRS tag can be used to specify one or more directories that
1644# contain msc files that are included in the documentation (see the
1645# \mscfile command).
1646
1647MSCFILE_DIRS =
1648
1649# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of
1650# nodes that will be shown in the graph. If the number of nodes in a graph
1651# becomes larger than this value, doxygen will truncate the graph, which is
1652# visualized by representing a node as a red box. Note that doxygen if the
1653# number of direct children of the root node in a graph is already larger than
1654# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note
1655# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
1656
1657DOT_GRAPH_MAX_NODES = 50
1658
1659# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
1660# graphs generated by dot. A depth value of 3 means that only nodes reachable
1661# from the root by following a path via at most 3 edges will be shown. Nodes
1662# that lay further from the root node will be omitted. Note that setting this
1663# option to 1 or 2 may greatly reduce the computation time needed for large
1664# code bases. Also note that the size of a graph can be further restricted by
1665# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
1666
1667MAX_DOT_GRAPH_DEPTH = 0
1668
1669# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
1670# background. This is disabled by default, because dot on Windows does not
1671# seem to support this out of the box. Warning: Depending on the platform used,
1672# enabling this option may lead to badly anti-aliased labels on the edges of
1673# a graph (i.e. they become hard to read).
1674
1675DOT_TRANSPARENT = YES
1676
1677# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
1678# files in one run (i.e. multiple -o and -T options on the command line). This
1679# makes dot run faster, but since only newer versions of dot (>1.8.10)
1680# support this, this feature is disabled by default.
1681
1682DOT_MULTI_TARGETS = NO
1683
1684# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1685# generate a legend page explaining the meaning of the various boxes and
1686# arrows in the dot generated graphs.
1687
1688GENERATE_LEGEND = YES
1689
1690# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1691# remove the intermediate dot files that are used to generate
1692# the various graphs.
1693
1694DOT_CLEANUP = YES
diff --git a/libraries/eet/doc/Doxyfile.in b/libraries/eet/doc/Doxyfile.in
deleted file mode 100644
index 8c427f8..0000000
--- a/libraries/eet/doc/Doxyfile.in
+++ /dev/null
@@ -1,1694 +0,0 @@
1# Doxyfile 1.7.3
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#---------------------------------------------------------------------------
14# Project related configuration options
15#---------------------------------------------------------------------------
16
17# This tag specifies the encoding used for all characters in the config file
18# that follow. The default is UTF-8 which is also the encoding used for all
19# text before the first occurrence of this tag. Doxygen uses libiconv (or the
20# iconv built into libc) for the transcoding. See
21# http://www.gnu.org/software/libiconv for the list of possible encodings.
22
23DOXYFILE_ENCODING = UTF-8
24
25# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
26# by quotes) that should identify the project.
27
28PROJECT_NAME = Eet
29
30# The PROJECT_NUMBER tag can be used to enter a project or revision number.
31# This could be handy for archiving the generated documentation or
32# if some version control system is used.
33
34PROJECT_NUMBER = @PACKAGE_VERSION@
35
36# Using the PROJECT_BRIEF tag one can provide an optional one line description for a project that appears at the top of each page and should give viewer a quick idea about the purpose of the project. Keep the description short.
37
38PROJECT_BRIEF =
39
40# With the PROJECT_LOGO tag one can specify an logo or icon that is
41# included in the documentation. The maximum height of the logo should not
42# exceed 55 pixels and the maximum width should not exceed 200 pixels.
43# Doxygen will copy the logo to the output directory.
44
45PROJECT_LOGO =
46
47# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
48# base path where the generated documentation will be put.
49# If a relative path is entered, it will be relative to the location
50# where doxygen was started. If left blank the current directory will be used.
51
52OUTPUT_DIRECTORY = .
53
54# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
55# 4096 sub-directories (in 2 levels) under the output directory of each output
56# format and will distribute the generated files over these directories.
57# Enabling this option can be useful when feeding doxygen a huge amount of
58# source files, where putting all generated files in the same directory would
59# otherwise cause performance problems for the file system.
60
61CREATE_SUBDIRS = NO
62
63# The OUTPUT_LANGUAGE tag is used to specify the language in which all
64# documentation generated by doxygen is written. Doxygen will use this
65# information to generate all constant output in the proper language.
66# The default language is English, other supported languages are:
67# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,
68# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German,
69# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English
70# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian,
71# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak,
72# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.
73
74OUTPUT_LANGUAGE = English
75
76# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
77# include brief member descriptions after the members that are listed in
78# the file and class documentation (similar to JavaDoc).
79# Set to NO to disable this.
80
81BRIEF_MEMBER_DESC = YES
82
83# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
84# the brief description of a member or function before the detailed description.
85# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
86# brief descriptions will be completely suppressed.
87
88REPEAT_BRIEF = YES
89
90# This tag implements a quasi-intelligent brief description abbreviator
91# that is used to form the text in various listings. Each string
92# in this list, if found as the leading text of the brief description, will be
93# stripped from the text and the result after processing the whole list, is
94# used as the annotated text. Otherwise, the brief description is used as-is.
95# If left blank, the following values are used ("$name" is automatically
96# replaced with the name of the entity): "The $name class" "The $name widget"
97# "The $name file" "is" "provides" "specifies" "contains"
98# "represents" "a" "an" "the"
99
100ABBREVIATE_BRIEF =
101
102# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
103# Doxygen will generate a detailed section even if there is only a brief
104# description.
105
106ALWAYS_DETAILED_SEC = NO
107
108# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
109# inherited members of a class in the documentation of that class as if those
110# members were ordinary class members. Constructors, destructors and assignment
111# operators of the base classes will not be shown.
112
113INLINE_INHERITED_MEMB = NO
114
115# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
116# path before files name in the file list and in the header files. If set
117# to NO the shortest path that makes the file name unique will be used.
118
119FULL_PATH_NAMES = NO
120
121# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
122# can be used to strip a user-defined part of the path. Stripping is
123# only done if one of the specified strings matches the left-hand part of
124# the path. The tag can be used to show relative paths in the file list.
125# If left blank the directory from which doxygen is run is used as the
126# path to strip.
127
128STRIP_FROM_PATH =
129
130# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
131# the path mentioned in the documentation of a class, which tells
132# the reader which header file to include in order to use a class.
133# If left blank only the name of the header file containing the class
134# definition is used. Otherwise one should specify the include paths that
135# are normally passed to the compiler using the -I flag.
136
137STRIP_FROM_INC_PATH =
138
139# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
140# (but less readable) file names. This can be useful if your file system
141# doesn't support long names like on DOS, Mac, or CD-ROM.
142
143SHORT_NAMES = NO
144
145# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
146# will interpret the first line (until the first dot) of a JavaDoc-style
147# comment as the brief description. If set to NO, the JavaDoc
148# comments will behave just like regular Qt-style comments
149# (thus requiring an explicit @brief command for a brief description.)
150
151JAVADOC_AUTOBRIEF = YES
152
153# If the QT_AUTOBRIEF tag is set to YES then Doxygen will
154# interpret the first line (until the first dot) of a Qt-style
155# comment as the brief description. If set to NO, the comments
156# will behave just like regular Qt-style comments (thus requiring
157# an explicit \brief command for a brief description.)
158
159QT_AUTOBRIEF = NO
160
161# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
162# treat a multi-line C++ special comment block (i.e. a block of //! or ///
163# comments) as a brief description. This used to be the default behaviour.
164# The new default is to treat a multi-line C++ comment block as a detailed
165# description. Set this tag to YES if you prefer the old behaviour instead.
166
167MULTILINE_CPP_IS_BRIEF = NO
168
169# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
170# member inherits the documentation from any documented member that it
171# re-implements.
172
173INHERIT_DOCS = YES
174
175# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
176# a new page for each member. If set to NO, the documentation of a member will
177# be part of the file/class/namespace that contains it.
178
179SEPARATE_MEMBER_PAGES = NO
180
181# The TAB_SIZE tag can be used to set the number of spaces in a tab.
182# Doxygen uses this value to replace tabs by spaces in code fragments.
183
184TAB_SIZE = 8
185
186# This tag can be used to specify a number of aliases that acts
187# as commands in the documentation. An alias has the form "name=value".
188# For example adding "sideeffect=\par Side Effects:\n" will allow you to
189# put the command \sideeffect (or @sideeffect) in the documentation, which
190# will result in a user-defined paragraph with heading "Side Effects:".
191# You can put \n's in the value part of an alias to insert newlines.
192
193ALIASES =
194
195# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
196# sources only. Doxygen will then generate output that is more tailored for C.
197# For instance, some of the names that are used will be different. The list
198# of all members will be omitted, etc.
199
200OPTIMIZE_OUTPUT_FOR_C = YES
201
202# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java
203# sources only. Doxygen will then generate output that is more tailored for
204# Java. For instance, namespaces will be presented as packages, qualified
205# scopes will look different, etc.
206
207OPTIMIZE_OUTPUT_JAVA = NO
208
209# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
210# sources only. Doxygen will then generate output that is more tailored for
211# Fortran.
212
213OPTIMIZE_FOR_FORTRAN = NO
214
215# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
216# sources. Doxygen will then generate output that is tailored for
217# VHDL.
218
219OPTIMIZE_OUTPUT_VHDL = NO
220
221# Doxygen selects the parser to use depending on the extension of the files it
222# parses. With this tag you can assign which parser to use for a given extension.
223# Doxygen has a built-in mapping, but you can override or extend it using this
224# tag. The format is ext=language, where ext is a file extension, and language
225# is one of the parsers supported by doxygen: IDL, Java, Javascript, CSharp, C,
226# C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. For instance to make
227# doxygen treat .inc files as Fortran files (default is PHP), and .f files as C
228# (default is Fortran), use: inc=Fortran f=C. Note that for custom extensions
229# you also need to set FILE_PATTERNS otherwise the files are not read by doxygen.
230
231EXTENSION_MAPPING =
232
233# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
234# to include (a tag file for) the STL sources as input, then you should
235# set this tag to YES in order to let doxygen match functions declarations and
236# definitions whose arguments contain STL classes (e.g. func(std::string); v.s.
237# func(std::string) {}). This also makes the inheritance and collaboration
238# diagrams that involve STL classes more complete and accurate.
239
240BUILTIN_STL_SUPPORT = NO
241
242# If you use Microsoft's C++/CLI language, you should set this option to YES to
243# enable parsing support.
244
245CPP_CLI_SUPPORT = NO
246
247# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only.
248# Doxygen will parse them like normal C++ but will assume all classes use public
249# instead of private inheritance when no explicit protection keyword is present.
250
251SIP_SUPPORT = NO
252
253# For Microsoft's IDL there are propget and propput attributes to indicate getter
254# and setter methods for a property. Setting this option to YES (the default)
255# will make doxygen replace the get and set methods by a property in the
256# documentation. This will only work if the methods are indeed getting or
257# setting a simple type. If this is not the case, or you want to show the
258# methods anyway, you should set this option to NO.
259
260IDL_PROPERTY_SUPPORT = YES
261
262# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
263# tag is set to YES, then doxygen will reuse the documentation of the first
264# member in the group (if any) for the other members of the group. By default
265# all members of a group must be documented explicitly.
266
267DISTRIBUTE_GROUP_DOC = NO
268
269# Set the SUBGROUPING tag to YES (the default) to allow class member groups of
270# the same type (for instance a group of public functions) to be put as a
271# subgroup of that type (e.g. under the Public Functions section). Set it to
272# NO to prevent subgrouping. Alternatively, this can be done per class using
273# the \nosubgrouping command.
274
275SUBGROUPING = YES
276
277# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum
278# is documented as struct, union, or enum with the name of the typedef. So
279# typedef struct TypeS {} TypeT, will appear in the documentation as a struct
280# with name TypeT. When disabled the typedef will appear as a member of a file,
281# namespace, or class. And the struct will be named TypeS. This can typically
282# be useful for C code in case the coding convention dictates that all compound
283# types are typedef'ed and only the typedef is referenced, never the tag name.
284
285TYPEDEF_HIDES_STRUCT = NO
286
287# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to
288# determine which symbols to keep in memory and which to flush to disk.
289# When the cache is full, less often used symbols will be written to disk.
290# For small to medium size projects (<1000 input files) the default value is
291# probably good enough. For larger projects a too small cache size can cause
292# doxygen to be busy swapping symbols to and from disk most of the time
293# causing a significant performance penalty.
294# If the system has enough physical memory increasing the cache will improve the
295# performance by keeping more symbols in memory. Note that the value works on
296# a logarithmic scale so increasing the size by one will roughly double the
297# memory usage. The cache size is given by this formula:
298# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,
299# corresponding to a cache size of 2^16 = 65536 symbols
300
301SYMBOL_CACHE_SIZE = 0
302
303#---------------------------------------------------------------------------
304# Build related configuration options
305#---------------------------------------------------------------------------
306
307# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
308# documentation are documented, even if no documentation was available.
309# Private class members and static file members will be hidden unless
310# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
311
312EXTRACT_ALL = NO
313
314# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
315# will be included in the documentation.
316
317EXTRACT_PRIVATE = NO
318
319# If the EXTRACT_STATIC tag is set to YES all static members of a file
320# will be included in the documentation.
321
322EXTRACT_STATIC = NO
323
324# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
325# defined locally in source files will be included in the documentation.
326# If set to NO only classes defined in header files are included.
327
328EXTRACT_LOCAL_CLASSES = NO
329
330# This flag is only useful for Objective-C code. When set to YES local
331# methods, which are defined in the implementation section but not in
332# the interface are included in the documentation.
333# If set to NO (the default) only methods in the interface are included.
334
335EXTRACT_LOCAL_METHODS = NO
336
337# If this flag is set to YES, the members of anonymous namespaces will be
338# extracted and appear in the documentation as a namespace called
339# 'anonymous_namespace{file}', where file will be replaced with the base
340# name of the file that contains the anonymous namespace. By default
341# anonymous namespaces are hidden.
342
343EXTRACT_ANON_NSPACES = NO
344
345# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
346# undocumented members of documented classes, files or namespaces.
347# If set to NO (the default) these members will be included in the
348# various overviews, but no documentation section is generated.
349# This option has no effect if EXTRACT_ALL is enabled.
350
351HIDE_UNDOC_MEMBERS = NO
352
353# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
354# undocumented classes that are normally visible in the class hierarchy.
355# If set to NO (the default) these classes will be included in the various
356# overviews. This option has no effect if EXTRACT_ALL is enabled.
357
358HIDE_UNDOC_CLASSES = NO
359
360# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
361# friend (class|struct|union) declarations.
362# If set to NO (the default) these declarations will be included in the
363# documentation.
364
365HIDE_FRIEND_COMPOUNDS = NO
366
367# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
368# documentation blocks found inside the body of a function.
369# If set to NO (the default) these blocks will be appended to the
370# function's detailed documentation block.
371
372HIDE_IN_BODY_DOCS = NO
373
374# The INTERNAL_DOCS tag determines if documentation
375# that is typed after a \internal command is included. If the tag is set
376# to NO (the default) then the documentation will be excluded.
377# Set it to YES to include the internal documentation.
378
379INTERNAL_DOCS = NO
380
381# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
382# file names in lower-case letters. If set to YES upper-case letters are also
383# allowed. This is useful if you have classes or files whose names only differ
384# in case and if your file system supports case sensitive file names. Windows
385# and Mac users are advised to set this option to NO.
386
387CASE_SENSE_NAMES = YES
388
389# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
390# will show members with their full class and namespace scopes in the
391# documentation. If set to YES the scope will be hidden.
392
393HIDE_SCOPE_NAMES = NO
394
395# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
396# will put a list of the files that are included by a file in the documentation
397# of that file.
398
399SHOW_INCLUDE_FILES = NO
400
401# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen
402# will list include files with double quotes in the documentation
403# rather than with sharp brackets.
404
405FORCE_LOCAL_INCLUDES = NO
406
407# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
408# is inserted in the documentation for inline members.
409
410INLINE_INFO = YES
411
412# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
413# will sort the (detailed) documentation of file and class members
414# alphabetically by member name. If set to NO the members will appear in
415# declaration order.
416
417SORT_MEMBER_DOCS = NO
418
419# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
420# brief documentation of file, namespace and class members alphabetically
421# by member name. If set to NO (the default) the members will appear in
422# declaration order.
423
424SORT_BRIEF_DOCS = NO
425
426# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen
427# will sort the (brief and detailed) documentation of class members so that
428# constructors and destructors are listed first. If set to NO (the default)
429# the constructors will appear in the respective orders defined by
430# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS.
431# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO
432# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.
433
434SORT_MEMBERS_CTORS_1ST = NO
435
436# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the
437# hierarchy of group names into alphabetical order. If set to NO (the default)
438# the group names will appear in their defined order.
439
440SORT_GROUP_NAMES = NO
441
442# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
443# sorted by fully-qualified names, including namespaces. If set to
444# NO (the default), the class list will be sorted only by class name,
445# not including the namespace part.
446# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
447# Note: This option applies only to the class list, not to the
448# alphabetical list.
449
450SORT_BY_SCOPE_NAME = NO
451
452# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper type resolution of all parameters of a function it will reject a
453# match between the prototype and the implementation of a member function even if there is only one candidate or it is obvious which candidate to choose by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen
454# will still accept a match between prototype and implementation in such cases.
455
456STRICT_PROTO_MATCHING = NO
457
458# The GENERATE_TODOLIST tag can be used to enable (YES) or
459# disable (NO) the todo list. This list is created by putting \todo
460# commands in the documentation.
461
462GENERATE_TODOLIST = YES
463
464# The GENERATE_TESTLIST tag can be used to enable (YES) or
465# disable (NO) the test list. This list is created by putting \test
466# commands in the documentation.
467
468GENERATE_TESTLIST = YES
469
470# The GENERATE_BUGLIST tag can be used to enable (YES) or
471# disable (NO) the bug list. This list is created by putting \bug
472# commands in the documentation.
473
474GENERATE_BUGLIST = YES
475
476# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
477# disable (NO) the deprecated list. This list is created by putting
478# \deprecated commands in the documentation.
479
480GENERATE_DEPRECATEDLIST= YES
481
482# The ENABLED_SECTIONS tag can be used to enable conditional
483# documentation sections, marked by \if sectionname ... \endif.
484
485ENABLED_SECTIONS =
486
487# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
488# the initial value of a variable or macro consists of for it to appear in
489# the documentation. If the initializer consists of more lines than specified
490# here it will be hidden. Use a value of 0 to hide initializers completely.
491# The appearance of the initializer of individual variables and macros in the
492# documentation can be controlled using \showinitializer or \hideinitializer
493# command in the documentation regardless of this setting.
494
495MAX_INITIALIZER_LINES = 30
496
497# Set the SHOW_USED_FILES tag to NO to disable the list of files generated
498# at the bottom of the documentation of classes and structs. If set to YES the
499# list will mention the files that were used to generate the documentation.
500
501SHOW_USED_FILES = NO
502
503# If the sources in your project are distributed over multiple directories
504# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
505# in the documentation. The default is NO.
506
507SHOW_DIRECTORIES = NO
508
509# Set the SHOW_FILES tag to NO to disable the generation of the Files page.
510# This will remove the Files entry from the Quick Index and from the
511# Folder Tree View (if specified). The default is YES.
512
513SHOW_FILES = YES
514
515# Set the SHOW_NAMESPACES tag to NO to disable the generation of the
516# Namespaces page.
517# This will remove the Namespaces entry from the Quick Index
518# and from the Folder Tree View (if specified). The default is YES.
519
520SHOW_NAMESPACES = YES
521
522# The FILE_VERSION_FILTER tag can be used to specify a program or script that
523# doxygen should invoke to get the current version for each file (typically from
524# the version control system). Doxygen will invoke the program by executing (via
525# popen()) the command <command> <input-file>, where <command> is the value of
526# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
527# provided by doxygen. Whatever the program writes to standard output
528# is used as the file version. See the manual for examples.
529
530FILE_VERSION_FILTER =
531
532# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
533# by doxygen. The layout file controls the global structure of the generated
534# output files in an output format independent way. The create the layout file
535# that represents doxygen's defaults, run doxygen with the -l option.
536# You can optionally specify a file name after the option, if omitted
537# DoxygenLayout.xml will be used as the name of the layout file.
538
539LAYOUT_FILE =
540
541#---------------------------------------------------------------------------
542# configuration options related to warning and progress messages
543#---------------------------------------------------------------------------
544
545# The QUIET tag can be used to turn on/off the messages that are generated
546# by doxygen. Possible values are YES and NO. If left blank NO is used.
547
548QUIET = NO
549
550# The WARNINGS tag can be used to turn on/off the warning messages that are
551# generated by doxygen. Possible values are YES and NO. If left blank
552# NO is used.
553
554WARNINGS = YES
555
556# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
557# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
558# automatically be disabled.
559
560WARN_IF_UNDOCUMENTED = YES
561
562# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
563# potential errors in the documentation, such as not documenting some
564# parameters in a documented function, or documenting parameters that
565# don't exist or using markup commands wrongly.
566
567WARN_IF_DOC_ERROR = YES
568
569# The WARN_NO_PARAMDOC option can be enabled to get warnings for
570# functions that are documented, but have no documentation for their parameters
571# or return value. If set to NO (the default) doxygen will only warn about
572# wrong or incomplete parameter documentation, but not about the absence of
573# documentation.
574
575WARN_NO_PARAMDOC = YES
576
577# The WARN_FORMAT tag determines the format of the warning messages that
578# doxygen can produce. The string should contain the $file, $line, and $text
579# tags, which will be replaced by the file and line number from which the
580# warning originated and the warning text. Optionally the format may contain
581# $version, which will be replaced by the version of the file (if it could
582# be obtained via FILE_VERSION_FILTER)
583
584WARN_FORMAT = "$file:$line: $text"
585
586# The WARN_LOGFILE tag can be used to specify a file to which warning
587# and error messages should be written. If left blank the output is written
588# to stderr.
589
590WARN_LOGFILE =
591
592#---------------------------------------------------------------------------
593# configuration options related to the input files
594#---------------------------------------------------------------------------
595
596# The INPUT tag can be used to specify the files and/or directories that contain
597# documented source files. You may enter file names like "myfile.cpp" or
598# directories like "/usr/src/myproject". Separate the files or directories
599# with spaces.
600
601INPUT = @builddir@/eet.dox \
602 @srcdir@/examples.dox \
603 @top_srcdir@/src/lib
604
605# This tag can be used to specify the character encoding of the source files
606# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is
607# also the default input encoding. Doxygen uses libiconv (or the iconv built
608# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for
609# the list of possible encodings.
610
611INPUT_ENCODING = UTF-8
612
613# If the value of the INPUT tag contains directories, you can use the
614# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
615# and *.h) to filter out the source-files in the directories. If left
616# blank the following patterns are tested:
617# *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh
618# *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py
619# *.f90 *.f *.for *.vhd *.vhdl
620
621FILE_PATTERNS = *.c \
622 *.h
623
624# The RECURSIVE tag can be used to turn specify whether or not subdirectories
625# should be searched for input files as well. Possible values are YES and NO.
626# If left blank NO is used.
627
628RECURSIVE = YES
629
630# The EXCLUDE tag can be used to specify files and/or directories that should
631# excluded from the INPUT source files. This way you can easily exclude a
632# subdirectory from a directory tree whose root is specified with the INPUT tag.
633
634EXCLUDE = @top_builddir@/src/lib/eet_amalgamation.c
635
636# The EXCLUDE_SYMLINKS tag can be used select whether or not files or
637# directories that are symbolic links (a Unix file system feature) are excluded
638# from the input.
639
640EXCLUDE_SYMLINKS = NO
641
642# If the value of the INPUT tag contains directories, you can use the
643# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
644# certain files from those directories. Note that the wildcards are matched
645# against the file with absolute path, so to exclude all test directories
646# for example use the pattern */test/*
647
648EXCLUDE_PATTERNS =
649
650# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
651# (namespaces, classes, functions, etc.) that should be excluded from the
652# output. The symbol name can be a fully qualified name, a word, or if the
653# wildcard * is used, a substring. Examples: ANamespace, AClass,
654# AClass::ANamespace, ANamespace::*Test
655
656EXCLUDE_SYMBOLS =
657
658# The EXAMPLE_PATH tag can be used to specify one or more files or
659# directories that contain example code fragments that are included (see
660# the \include command).
661
662EXAMPLE_PATH = @top_srcdir@/src/examples
663
664# If the value of the EXAMPLE_PATH tag contains directories, you can use the
665# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
666# and *.h) to filter out the source-files in the directories. If left
667# blank all files are included.
668
669EXAMPLE_PATTERNS = *.c,*.h,*.x
670
671# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
672# searched for input files to be used with the \include or \dontinclude
673# commands irrespective of the value of the RECURSIVE tag.
674# Possible values are YES and NO. If left blank NO is used.
675
676EXAMPLE_RECURSIVE = NO
677
678# The IMAGE_PATH tag can be used to specify one or more files or
679# directories that contain image that are included in the documentation (see
680# the \image command).
681
682IMAGE_PATH = @top_srcdir@/doc/img
683
684# The INPUT_FILTER tag can be used to specify a program that doxygen should
685# invoke to filter for each input file. Doxygen will invoke the filter program
686# by executing (via popen()) the command <filter> <input-file>, where <filter>
687# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
688# input file. Doxygen will then use the output that the filter program writes
689# to standard output.
690# If FILTER_PATTERNS is specified, this tag will be
691# ignored.
692
693INPUT_FILTER =
694
695# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
696# basis.
697# Doxygen will compare the file name with each pattern and apply the
698# filter if there is a match.
699# The filters are a list of the form:
700# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
701# info on how filters are used. If FILTER_PATTERNS is empty or if
702# non of the patterns match the file name, INPUT_FILTER is applied.
703
704FILTER_PATTERNS =
705
706# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
707# INPUT_FILTER) will be used to filter the input files when producing source
708# files to browse (i.e. when SOURCE_BROWSER is set to YES).
709
710FILTER_SOURCE_FILES = NO
711
712# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
713# pattern. A pattern will override the setting for FILTER_PATTERN (if any)
714# and it is also possible to disable source filtering for a specific pattern
715# using *.ext= (so without naming a filter). This option only has effect when
716# FILTER_SOURCE_FILES is enabled.
717
718FILTER_SOURCE_PATTERNS =
719
720#---------------------------------------------------------------------------
721# configuration options related to source browsing
722#---------------------------------------------------------------------------
723
724# If the SOURCE_BROWSER tag is set to YES then a list of source files will
725# be generated. Documented entities will be cross-referenced with these sources.
726# Note: To get rid of all source code in the generated output, make sure also
727# VERBATIM_HEADERS is set to NO.
728
729SOURCE_BROWSER = NO
730
731# Setting the INLINE_SOURCES tag to YES will include the body
732# of functions and classes directly in the documentation.
733
734INLINE_SOURCES = NO
735
736# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
737# doxygen to hide any special comment blocks from generated source code
738# fragments. Normal C and C++ comments will always remain visible.
739
740STRIP_CODE_COMMENTS = YES
741
742# If the REFERENCED_BY_RELATION tag is set to YES
743# then for each documented function all documented
744# functions referencing it will be listed.
745
746REFERENCED_BY_RELATION = YES
747
748# If the REFERENCES_RELATION tag is set to YES
749# then for each documented function all documented entities
750# called/used by that function will be listed.
751
752REFERENCES_RELATION = YES
753
754# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
755# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
756# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
757# link to the source code.
758# Otherwise they will link to the documentation.
759
760REFERENCES_LINK_SOURCE = YES
761
762# If the USE_HTAGS tag is set to YES then the references to source code
763# will point to the HTML generated by the htags(1) tool instead of doxygen
764# built-in source browser. The htags tool is part of GNU's global source
765# tagging system (see http://www.gnu.org/software/global/global.html). You
766# will need version 4.8.6 or higher.
767
768USE_HTAGS = NO
769
770# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
771# will generate a verbatim copy of the header file for each class for
772# which an include is specified. Set to NO to disable this.
773
774VERBATIM_HEADERS = NO
775
776#---------------------------------------------------------------------------
777# configuration options related to the alphabetical class index
778#---------------------------------------------------------------------------
779
780# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
781# of all compounds will be generated. Enable this if the project
782# contains a lot of classes, structs, unions or interfaces.
783
784ALPHABETICAL_INDEX = YES
785
786# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
787# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
788# in which this list will be split (can be a number in the range [1..20])
789
790COLS_IN_ALPHA_INDEX = 2
791
792# In case all classes in a project start with a common prefix, all
793# classes will be put under the same header in the alphabetical index.
794# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
795# should be ignored while generating the index headers.
796
797IGNORE_PREFIX = eet_ \
798 _eet_ \
799 Eet_ \
800 _Eet_ \
801 EET_ \
802 _EET_
803
804#---------------------------------------------------------------------------
805# configuration options related to the HTML output
806#---------------------------------------------------------------------------
807
808# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
809# generate HTML output.
810
811GENERATE_HTML = YES
812
813# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
814# If a relative path is entered the value of OUTPUT_DIRECTORY will be
815# put in front of it. If left blank `html' will be used as the default path.
816
817HTML_OUTPUT = html
818
819# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
820# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
821# doxygen will generate files with .html extension.
822
823HTML_FILE_EXTENSION = .html
824
825# The HTML_HEADER tag can be used to specify a personal HTML header for
826# each generated HTML page. If it is left blank doxygen will generate a
827# standard header.
828
829HTML_HEADER = @srcdir@/head.html
830
831# The HTML_FOOTER tag can be used to specify a personal HTML footer for
832# each generated HTML page. If it is left blank doxygen will generate a
833# standard footer.
834
835HTML_FOOTER = @srcdir@/foot.html
836
837# The HTML_STYLESHEET tag can be used to specify a user-defined cascading
838# style sheet that is used by each HTML page. It can be used to
839# fine-tune the look of the HTML output. If the tag is left blank doxygen
840# will generate a default style sheet. Note that doxygen will try to copy
841# the style sheet file to the HTML output directory, so don't put your own
842# stylesheet in the HTML output directory as well, or it will be erased!
843
844HTML_STYLESHEET = @srcdir@/e.css
845
846# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output.
847# Doxygen will adjust the colors in the stylesheet and background images
848# according to this color. Hue is specified as an angle on a colorwheel,
849# see http://en.wikipedia.org/wiki/Hue for more information.
850# For instance the value 0 represents red, 60 is yellow, 120 is green,
851# 180 is cyan, 240 is blue, 300 purple, and 360 is red again.
852# The allowed range is 0 to 359.
853
854HTML_COLORSTYLE_HUE = 220
855
856# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of
857# the colors in the HTML output. For a value of 0 the output will use
858# grayscales only. A value of 255 will produce the most vivid colors.
859
860HTML_COLORSTYLE_SAT = 100
861
862# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to
863# the luminance component of the colors in the HTML output. Values below
864# 100 gradually make the output lighter, whereas values above 100 make
865# the output darker. The value divided by 100 is the actual gamma applied,
866# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2,
867# and 100 does not change the gamma.
868
869HTML_COLORSTYLE_GAMMA = 80
870
871# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
872# page will contain the date and time when the page was generated. Setting
873# this to NO can help when comparing the output of multiple runs.
874
875HTML_TIMESTAMP = YES
876
877# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
878# files or namespaces will be aligned in HTML using tables. If set to
879# NO a bullet list will be used.
880
881HTML_ALIGN_MEMBERS = YES
882
883# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
884# documentation will contain sections that can be hidden and shown after the
885# page has loaded. For this to work a browser that supports
886# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox
887# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).
888
889HTML_DYNAMIC_SECTIONS = YES
890
891# If the GENERATE_DOCSET tag is set to YES, additional index files
892# will be generated that can be used as input for Apple's Xcode 3
893# integrated development environment, introduced with OSX 10.5 (Leopard).
894# To create a documentation set, doxygen will generate a Makefile in the
895# HTML output directory. Running make will produce the docset in that
896# directory and running "make install" will install the docset in
897# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
898# it at startup.
899# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
900# for more information.
901
902GENERATE_DOCSET = YES
903
904# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the
905# feed. A documentation feed provides an umbrella under which multiple
906# documentation sets from a single provider (such as a company or product suite)
907# can be grouped.
908
909DOCSET_FEEDNAME = "Doxygen generated docs"
910
911# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that
912# should uniquely identify the documentation set bundle. This should be a
913# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen
914# will append .docset to the name.
915
916DOCSET_BUNDLE_ID = org.enlightenment.Eet
917
918# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify
919# the documentation publisher. This should be a reverse domain-name style
920# string, e.g. com.mycompany.MyDocSet.documentation.
921
922DOCSET_PUBLISHER_ID = org.enlightenment.Eet
923
924# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.
925
926DOCSET_PUBLISHER_NAME = Enlightenment
927
928# If the GENERATE_HTMLHELP tag is set to YES, additional index files
929# will be generated that can be used as input for tools like the
930# Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
931# of the generated HTML documentation.
932
933GENERATE_HTMLHELP = YES
934
935# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
936# be used to specify the file name of the resulting .chm file. You
937# can add a path in front of the file if the result should not be
938# written to the html output directory.
939
940CHM_FILE =
941
942# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
943# be used to specify the location (absolute path including file name) of
944# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
945# the HTML help compiler on the generated index.hhp.
946
947HHC_LOCATION =
948
949# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
950# controls if a separate .chi index file is generated (YES) or that
951# it should be included in the master .chm file (NO).
952
953GENERATE_CHI = NO
954
955# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING
956# is used to encode HtmlHelp index (hhk), content (hhc) and project file
957# content.
958
959CHM_INDEX_ENCODING =
960
961# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
962# controls whether a binary table of contents is generated (YES) or a
963# normal table of contents (NO) in the .chm file.
964
965BINARY_TOC = NO
966
967# The TOC_EXPAND flag can be set to YES to add extra items for group members
968# to the contents of the HTML help documentation and to the tree view.
969
970TOC_EXPAND = NO
971
972# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
973# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated
974# that can be used as input for Qt's qhelpgenerator to generate a
975# Qt Compressed Help (.qch) of the generated HTML documentation.
976
977GENERATE_QHP = NO
978
979# If the QHG_LOCATION tag is specified, the QCH_FILE tag can
980# be used to specify the file name of the resulting .qch file.
981# The path specified is relative to the HTML output folder.
982
983QCH_FILE =
984
985# The QHP_NAMESPACE tag specifies the namespace to use when generating
986# Qt Help Project output. For more information please see
987# http://doc.trolltech.com/qthelpproject.html#namespace
988
989QHP_NAMESPACE = org.enlightenment.Eet
990
991# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating
992# Qt Help Project output. For more information please see
993# http://doc.trolltech.com/qthelpproject.html#virtual-folders
994
995QHP_VIRTUAL_FOLDER = doc
996
997# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to
998# add. For more information please see
999# http://doc.trolltech.com/qthelpproject.html#custom-filters
1000
1001QHP_CUST_FILTER_NAME =
1002
1003# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the
1004# custom filter to add. For more information please see
1005# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">
1006# Qt Help Project / Custom Filters</a>.
1007
1008QHP_CUST_FILTER_ATTRS =
1009
1010# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
1011# project's
1012# filter section matches.
1013# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">
1014# Qt Help Project / Filter Attributes</a>.
1015
1016QHP_SECT_FILTER_ATTRS =
1017
1018# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can
1019# be used to specify the location of Qt's qhelpgenerator.
1020# If non-empty doxygen will try to run qhelpgenerator on the generated
1021# .qhp file.
1022
1023QHG_LOCATION =
1024
1025# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files
1026# will be generated, which together with the HTML files, form an Eclipse help
1027# plugin. To install this plugin and make it available under the help contents
1028# menu in Eclipse, the contents of the directory containing the HTML and XML
1029# files needs to be copied into the plugins directory of eclipse. The name of
1030# the directory within the plugins directory should be the same as
1031# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before
1032# the help appears.
1033
1034GENERATE_ECLIPSEHELP = NO
1035
1036# A unique identifier for the eclipse help plugin. When installing the plugin
1037# the directory name containing the HTML and XML files should also have
1038# this name.
1039
1040ECLIPSE_DOC_ID = org.enlightenment.Eet
1041
1042# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
1043# top of each HTML page. The value NO (the default) enables the index and
1044# the value YES disables it.
1045
1046DISABLE_INDEX = YES
1047
1048# This tag can be used to set the number of enum values (range [0,1..20])
1049# that doxygen will group on one line in the generated HTML documentation.
1050# Note that a value of 0 will completely suppress the enum values from appearing in the overview section.
1051
1052ENUM_VALUES_PER_LINE = 1
1053
1054# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1055# structure should be generated to display hierarchical information.
1056# If the tag value is set to YES, a side panel will be generated
1057# containing a tree-like index structure (just like the one that
1058# is generated for HTML Help). For this to work a browser that supports
1059# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).
1060# Windows users are probably better off using the HTML help feature.
1061
1062GENERATE_TREEVIEW = NO
1063
1064# By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories,
1065# and Class Hierarchy pages using a tree view instead of an ordered list.
1066
1067USE_INLINE_TREES = NO
1068
1069# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
1070# used to set the initial width (in pixels) of the frame in which the tree
1071# is shown.
1072
1073TREEVIEW_WIDTH = 250
1074
1075# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open
1076# links to external symbols imported via tag files in a separate window.
1077
1078EXT_LINKS_IN_WINDOW = NO
1079
1080# Use this tag to change the font size of Latex formulas included
1081# as images in the HTML documentation. The default is 10. Note that
1082# when you change the font size after a successful doxygen run you need
1083# to manually remove any form_*.png images from the HTML output directory
1084# to force them to be regenerated.
1085
1086FORMULA_FONTSIZE = 10
1087
1088# Use the FORMULA_TRANPARENT tag to determine whether or not the images
1089# generated for formulas are transparent PNGs. Transparent PNGs are
1090# not supported properly for IE 6.0, but are supported on all modern browsers.
1091# Note that when changing this option you need to delete any form_*.png files
1092# in the HTML output before the changes have effect.
1093
1094FORMULA_TRANSPARENT = YES
1095
1096# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax
1097# (see http://www.mathjax.org) which uses client side Javascript for the
1098# rendering instead of using prerendered bitmaps. Use this if you do not
1099# have LaTeX installed or if you want to formulas look prettier in the HTML
1100# output. When enabled you also need to install MathJax separately and
1101# configure the path to it using the MATHJAX_RELPATH option.
1102
1103USE_MATHJAX = NO
1104
1105# When MathJax is enabled you need to specify the location relative to the
1106# HTML output directory using the MATHJAX_RELPATH option. The destination
1107# directory should contain the MathJax.js script. For instance, if the mathjax
1108# directory is located at the same level as the HTML output directory, then
1109# MATHJAX_RELPATH should be ../mathjax. The default value points to the mathjax.org site, so you can quickly see the result without installing
1110# MathJax, but it is strongly recommended to install a local copy of MathJax
1111# before deployment.
1112
1113MATHJAX_RELPATH = http://www.mathjax.org/mathjax
1114
1115# When the SEARCHENGINE tag is enabled doxygen will generate a search box
1116# for the HTML output. The underlying search engine uses javascript
1117# and DHTML and should work on any modern browser. Note that when using
1118# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets
1119# (GENERATE_DOCSET) there is already a search function so this one should
1120# typically be disabled. For large projects the javascript based search engine
1121# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.
1122
1123SEARCHENGINE = NO
1124
1125# When the SERVER_BASED_SEARCH tag is enabled the search engine will be
1126# implemented using a PHP enabled web server instead of at the web client
1127# using Javascript. Doxygen will generate the search PHP script and index
1128# file to put on the web server. The advantage of the server
1129# based approach is that it scales better to large projects and allows
1130# full text search. The disadvantages are that it is more difficult to setup
1131# and does not have live searching capabilities.
1132
1133SERVER_BASED_SEARCH = NO
1134
1135#---------------------------------------------------------------------------
1136# configuration options related to the LaTeX output
1137#---------------------------------------------------------------------------
1138
1139# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
1140# generate Latex output.
1141
1142GENERATE_LATEX = YES
1143
1144# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
1145# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1146# put in front of it. If left blank `latex' will be used as the default path.
1147
1148LATEX_OUTPUT = latex
1149
1150# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
1151# invoked. If left blank `latex' will be used as the default command name.
1152# Note that when enabling USE_PDFLATEX this option is only used for
1153# generating bitmaps for formulas in the HTML output, but not in the
1154# Makefile that is written to the output directory.
1155
1156LATEX_CMD_NAME = latex
1157
1158# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
1159# generate index for LaTeX. If left blank `makeindex' will be used as the
1160# default command name.
1161
1162MAKEINDEX_CMD_NAME = makeindex
1163
1164# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
1165# LaTeX documents. This may be useful for small projects and may help to
1166# save some trees in general.
1167
1168COMPACT_LATEX = NO
1169
1170# The PAPER_TYPE tag can be used to set the paper type that is used
1171# by the printer. Possible values are: a4, letter, legal and
1172# executive. If left blank a4wide will be used.
1173
1174PAPER_TYPE = a4wide
1175
1176# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
1177# packages that should be included in the LaTeX output.
1178
1179EXTRA_PACKAGES =
1180
1181# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
1182# the generated latex document. The header should contain everything until
1183# the first chapter. If it is left blank doxygen will generate a
1184# standard header. Notice: only use this tag if you know what you are doing!
1185
1186LATEX_HEADER =
1187
1188# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
1189# is prepared for conversion to pdf (using ps2pdf). The pdf file will
1190# contain links (just like the HTML output) instead of page references
1191# This makes the output suitable for online browsing using a pdf viewer.
1192
1193PDF_HYPERLINKS = YES
1194
1195# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
1196# plain latex in the generated Makefile. Set this option to YES to get a
1197# higher quality PDF documentation.
1198
1199USE_PDFLATEX = YES
1200
1201# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
1202# command to the generated LaTeX files. This will instruct LaTeX to keep
1203# running if errors occur, instead of asking the user for help.
1204# This option is also used when generating formulas in HTML.
1205
1206LATEX_BATCHMODE = NO
1207
1208# If LATEX_HIDE_INDICES is set to YES then doxygen will not
1209# include the index chapters (such as File Index, Compound Index, etc.)
1210# in the output.
1211
1212LATEX_HIDE_INDICES = NO
1213
1214# If LATEX_SOURCE_CODE is set to YES then doxygen will include
1215# source code with syntax highlighting in the LaTeX output.
1216# Note that which sources are shown also depends on other settings
1217# such as SOURCE_BROWSER.
1218
1219LATEX_SOURCE_CODE = NO
1220
1221#---------------------------------------------------------------------------
1222# configuration options related to the RTF output
1223#---------------------------------------------------------------------------
1224
1225# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
1226# The RTF output is optimized for Word 97 and may not look very pretty with
1227# other RTF readers or editors.
1228
1229GENERATE_RTF = NO
1230
1231# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
1232# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1233# put in front of it. If left blank `rtf' will be used as the default path.
1234
1235RTF_OUTPUT = rtf
1236
1237# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
1238# RTF documents. This may be useful for small projects and may help to
1239# save some trees in general.
1240
1241COMPACT_RTF = NO
1242
1243# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
1244# will contain hyperlink fields. The RTF file will
1245# contain links (just like the HTML output) instead of page references.
1246# This makes the output suitable for online browsing using WORD or other
1247# programs which support those fields.
1248# Note: wordpad (write) and others do not support links.
1249
1250RTF_HYPERLINKS = NO
1251
1252# Load stylesheet definitions from file. Syntax is similar to doxygen's
1253# config file, i.e. a series of assignments. You only have to provide
1254# replacements, missing definitions are set to their default value.
1255
1256RTF_STYLESHEET_FILE =
1257
1258# Set optional variables used in the generation of an rtf document.
1259# Syntax is similar to doxygen's config file.
1260
1261RTF_EXTENSIONS_FILE =
1262
1263#---------------------------------------------------------------------------
1264# configuration options related to the man page output
1265#---------------------------------------------------------------------------
1266
1267# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
1268# generate man pages
1269
1270GENERATE_MAN = NO
1271
1272# The MAN_OUTPUT tag is used to specify where the man pages will be put.
1273# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1274# put in front of it. If left blank `man' will be used as the default path.
1275
1276MAN_OUTPUT = man
1277
1278# The MAN_EXTENSION tag determines the extension that is added to
1279# the generated man pages (default is the subroutine's section .3)
1280
1281MAN_EXTENSION = .3
1282
1283# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
1284# then it will generate one additional man file for each entity
1285# documented in the real man page(s). These additional files
1286# only source the real man page, but without them the man command
1287# would be unable to find the correct page. The default is NO.
1288
1289MAN_LINKS = YES
1290
1291#---------------------------------------------------------------------------
1292# configuration options related to the XML output
1293#---------------------------------------------------------------------------
1294
1295# If the GENERATE_XML tag is set to YES Doxygen will
1296# generate an XML file that captures the structure of
1297# the code including all documentation.
1298
1299GENERATE_XML = NO
1300
1301# The XML_OUTPUT tag is used to specify where the XML pages will be put.
1302# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1303# put in front of it. If left blank `xml' will be used as the default path.
1304
1305XML_OUTPUT = xml
1306
1307# The XML_SCHEMA tag can be used to specify an XML schema,
1308# which can be used by a validating XML parser to check the
1309# syntax of the XML files.
1310
1311XML_SCHEMA =
1312
1313# The XML_DTD tag can be used to specify an XML DTD,
1314# which can be used by a validating XML parser to check the
1315# syntax of the XML files.
1316
1317XML_DTD =
1318
1319# If the XML_PROGRAMLISTING tag is set to YES Doxygen will
1320# dump the program listings (including syntax highlighting
1321# and cross-referencing information) to the XML output. Note that
1322# enabling this will significantly increase the size of the XML output.
1323
1324XML_PROGRAMLISTING = YES
1325
1326#---------------------------------------------------------------------------
1327# configuration options for the AutoGen Definitions output
1328#---------------------------------------------------------------------------
1329
1330# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
1331# generate an AutoGen Definitions (see autogen.sf.net) file
1332# that captures the structure of the code including all
1333# documentation. Note that this feature is still experimental
1334# and incomplete at the moment.
1335
1336GENERATE_AUTOGEN_DEF = NO
1337
1338#---------------------------------------------------------------------------
1339# configuration options related to the Perl module output
1340#---------------------------------------------------------------------------
1341
1342# If the GENERATE_PERLMOD tag is set to YES Doxygen will
1343# generate a Perl module file that captures the structure of
1344# the code including all documentation. Note that this
1345# feature is still experimental and incomplete at the
1346# moment.
1347
1348GENERATE_PERLMOD = NO
1349
1350# If the PERLMOD_LATEX tag is set to YES Doxygen will generate
1351# the necessary Makefile rules, Perl scripts and LaTeX code to be able
1352# to generate PDF and DVI output from the Perl module output.
1353
1354PERLMOD_LATEX = NO
1355
1356# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
1357# nicely formatted so it can be parsed by a human reader.
1358# This is useful
1359# if you want to understand what is going on.
1360# On the other hand, if this
1361# tag is set to NO the size of the Perl module output will be much smaller
1362# and Perl will parse it just the same.
1363
1364PERLMOD_PRETTY = YES
1365
1366# The names of the make variables in the generated doxyrules.make file
1367# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
1368# This is useful so different doxyrules.make files included by the same
1369# Makefile don't overwrite each other's variables.
1370
1371PERLMOD_MAKEVAR_PREFIX =
1372
1373#---------------------------------------------------------------------------
1374# Configuration options related to the preprocessor
1375#---------------------------------------------------------------------------
1376
1377# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
1378# evaluate all C-preprocessor directives found in the sources and include
1379# files.
1380
1381ENABLE_PREPROCESSING = YES
1382
1383# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
1384# names in the source code. If set to NO (the default) only conditional
1385# compilation will be performed. Macro expansion can be done in a controlled
1386# way by setting EXPAND_ONLY_PREDEF to YES.
1387
1388MACRO_EXPANSION = YES
1389
1390# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
1391# then the macro expansion is limited to the macros specified with the
1392# PREDEFINED and EXPAND_AS_DEFINED tags.
1393
1394EXPAND_ONLY_PREDEF = YES
1395
1396# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
1397# in the INCLUDE_PATH (see below) will be search if a #include is found.
1398
1399SEARCH_INCLUDES = NO
1400
1401# The INCLUDE_PATH tag can be used to specify one or more directories that
1402# contain include files that are not input files but should be processed by
1403# the preprocessor.
1404
1405INCLUDE_PATH =
1406
1407# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
1408# patterns (like *.h and *.hpp) to filter out the header-files in the
1409# directories. If left blank, the patterns specified with FILE_PATTERNS will
1410# be used.
1411
1412INCLUDE_FILE_PATTERNS =
1413
1414# The PREDEFINED tag can be used to specify one or more macro names that
1415# are defined before the preprocessor is started (similar to the -D option of
1416# gcc). The argument of the tag is a list of macros of the form: name
1417# or name=definition (no spaces). If the definition and the = are
1418# omitted =1 is assumed. To prevent a macro definition from being
1419# undefined via #undef or recursively expanded use the := operator
1420# instead of the = operator.
1421
1422PREDEFINED = EINA_MAGIC_DEBUG \
1423 __UNUSED__= \
1424 EINA_ARG_NONNULL()= \
1425 EINA_MALLOC= \
1426 EINA_WARN_UNUSED_RESULT= \
1427 EAPI= \
1428 EINA_PURE= \
1429 EINA_CONST=
1430
1431# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
1432# this tag can be used to specify a list of macro names that should be expanded.
1433# The macro definition that is found in the sources will be used.
1434# Use the PREDEFINED tag if you want to use a different macro definition that overrules the definition found in the source code.
1435
1436EXPAND_AS_DEFINED =
1437
1438# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
1439# doxygen's preprocessor will remove all references to function-like macros
1440# that are alone on a line, have an all uppercase name, and do not end with a
1441# semicolon, because these will confuse the parser if not removed.
1442
1443SKIP_FUNCTION_MACROS = YES
1444
1445#---------------------------------------------------------------------------
1446# Configuration::additions related to external references
1447#---------------------------------------------------------------------------
1448
1449# The TAGFILES option can be used to specify one or more tagfiles.
1450# Optionally an initial location of the external documentation
1451# can be added for each tagfile. The format of a tag file without
1452# this location is as follows:
1453#
1454# TAGFILES = file1 file2 ...
1455# Adding location for the tag files is done as follows:
1456#
1457# TAGFILES = file1=loc1 "file2 = loc2" ...
1458# where "loc1" and "loc2" can be relative or absolute paths or
1459# URLs. If a location is present for each tag, the installdox tool
1460# does not have to be run to correct the links.
1461# Note that each tag file must have a unique name
1462# (where the name does NOT include the path)
1463# If a tag file is not located in the directory in which doxygen
1464# is run, you must also specify the path to the tagfile here.
1465
1466TAGFILES =
1467
1468# When a file name is specified after GENERATE_TAGFILE, doxygen will create
1469# a tag file that is based on the input files it reads.
1470
1471GENERATE_TAGFILE =
1472
1473# If the ALLEXTERNALS tag is set to YES all external classes will be listed
1474# in the class index. If set to NO only the inherited external classes
1475# will be listed.
1476
1477ALLEXTERNALS = NO
1478
1479# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1480# in the modules index. If set to NO, only the current project's groups will
1481# be listed.
1482
1483EXTERNAL_GROUPS = YES
1484
1485# The PERL_PATH should be the absolute path and name of the perl script
1486# interpreter (i.e. the result of `which perl').
1487
1488PERL_PATH = /usr/bin/perl
1489
1490#---------------------------------------------------------------------------
1491# Configuration options related to the dot tool
1492#---------------------------------------------------------------------------
1493
1494# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1495# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
1496# or super classes. Setting the tag to NO turns the diagrams off. Note that
1497# this option also works with HAVE_DOT disabled, but it is recommended to
1498# install and use dot, since it yields more powerful graphs.
1499
1500CLASS_DIAGRAMS = NO
1501
1502# You can define message sequence charts within doxygen comments using the \msc
1503# command. Doxygen will then run the mscgen tool (see
1504# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the
1505# documentation. The MSCGEN_PATH tag allows you to specify the directory where
1506# the mscgen tool resides. If left empty the tool is assumed to be found in the
1507# default search path.
1508
1509MSCGEN_PATH =
1510
1511# If set to YES, the inheritance and collaboration graphs will hide
1512# inheritance and usage relations if the target is undocumented
1513# or is not a class.
1514
1515HIDE_UNDOC_RELATIONS = YES
1516
1517# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1518# available from the path. This tool is part of Graphviz, a graph visualization
1519# toolkit from AT&T and Lucent Bell Labs. The other options in this section
1520# have no effect if this option is set to NO (the default)
1521
1522HAVE_DOT = NO
1523
1524# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is
1525# allowed to run in parallel. When set to 0 (the default) doxygen will
1526# base this on the number of processors available in the system. You can set it
1527# explicitly to a value larger than 0 to get control over the balance
1528# between CPU load and processing speed.
1529
1530DOT_NUM_THREADS = 0
1531
1532# By default doxygen will write a font called Helvetica to the output
1533# directory and reference it in all dot files that doxygen generates.
1534# When you want a differently looking font you can specify the font name
1535# using DOT_FONTNAME. You need to make sure dot is able to find the font,
1536# which can be done by putting it in a standard location or by setting the
1537# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory
1538# containing the font.
1539
1540DOT_FONTNAME = Helvetica
1541
1542# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs.
1543# The default size is 10pt.
1544
1545DOT_FONTSIZE = 10
1546
1547# By default doxygen will tell dot to use the output directory to look for the
1548# FreeSans.ttf font (which doxygen will put there itself). If you specify a
1549# different font using DOT_FONTNAME you can set the path where dot
1550# can find it using this tag.
1551
1552DOT_FONTPATH =
1553
1554# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
1555# will generate a graph for each documented class showing the direct and
1556# indirect inheritance relations. Setting this tag to YES will force the
1557# the CLASS_DIAGRAMS tag to NO.
1558
1559CLASS_GRAPH = NO
1560
1561# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
1562# will generate a graph for each documented class showing the direct and
1563# indirect implementation dependencies (inheritance, containment, and
1564# class references variables) of the class with other documented classes.
1565
1566COLLABORATION_GRAPH = NO
1567
1568# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
1569# will generate a graph for groups, showing the direct groups dependencies
1570
1571GROUP_GRAPHS = YES
1572
1573# If the UML_LOOK tag is set to YES doxygen will generate inheritance and
1574# collaboration diagrams in a style similar to the OMG's Unified Modeling
1575# Language.
1576
1577UML_LOOK = NO
1578
1579# If set to YES, the inheritance and collaboration graphs will show the
1580# relations between templates and their instances.
1581
1582TEMPLATE_RELATIONS = NO
1583
1584# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
1585# tags are set to YES then doxygen will generate a graph for each documented
1586# file showing the direct and indirect include dependencies of the file with
1587# other documented files.
1588
1589INCLUDE_GRAPH = NO
1590
1591# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
1592# HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1593# documented header file showing the documented files that directly or
1594# indirectly include this file.
1595
1596INCLUDED_BY_GRAPH = NO
1597
1598# If the CALL_GRAPH and HAVE_DOT options are set to YES then
1599# doxygen will generate a call dependency graph for every global function
1600# or class method. Note that enabling this option will significantly increase
1601# the time of a run. So in most cases it will be better to enable call graphs
1602# for selected functions only using the \callgraph command.
1603
1604CALL_GRAPH = NO
1605
1606# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then
1607# doxygen will generate a caller dependency graph for every global function
1608# or class method. Note that enabling this option will significantly increase
1609# the time of a run. So in most cases it will be better to enable caller
1610# graphs for selected functions only using the \callergraph command.
1611
1612CALLER_GRAPH = NO
1613
1614# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
1615# will generate a graphical hierarchy of all classes instead of a textual one.
1616
1617GRAPHICAL_HIERARCHY = NO
1618
1619# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
1620# then doxygen will show the dependencies a directory has on other directories
1621# in a graphical way. The dependency relations are determined by the #include
1622# relations between the files in the directories.
1623
1624DIRECTORY_GRAPH = YES
1625
1626# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1627# generated by dot. Possible values are png, svg, gif or svg.
1628# If left blank png will be used.
1629
1630DOT_IMAGE_FORMAT = png
1631
1632# The tag DOT_PATH can be used to specify the path where the dot tool can be
1633# found. If left blank, it is assumed the dot tool can be found in the path.
1634
1635DOT_PATH =
1636
1637# The DOTFILE_DIRS tag can be used to specify one or more directories that
1638# contain dot files that are included in the documentation (see the
1639# \dotfile command).
1640
1641DOTFILE_DIRS =
1642
1643# The MSCFILE_DIRS tag can be used to specify one or more directories that
1644# contain msc files that are included in the documentation (see the
1645# \mscfile command).
1646
1647MSCFILE_DIRS =
1648
1649# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of
1650# nodes that will be shown in the graph. If the number of nodes in a graph
1651# becomes larger than this value, doxygen will truncate the graph, which is
1652# visualized by representing a node as a red box. Note that doxygen if the
1653# number of direct children of the root node in a graph is already larger than
1654# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note
1655# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
1656
1657DOT_GRAPH_MAX_NODES = 50
1658
1659# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
1660# graphs generated by dot. A depth value of 3 means that only nodes reachable
1661# from the root by following a path via at most 3 edges will be shown. Nodes
1662# that lay further from the root node will be omitted. Note that setting this
1663# option to 1 or 2 may greatly reduce the computation time needed for large
1664# code bases. Also note that the size of a graph can be further restricted by
1665# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
1666
1667MAX_DOT_GRAPH_DEPTH = 0
1668
1669# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
1670# background. This is disabled by default, because dot on Windows does not
1671# seem to support this out of the box. Warning: Depending on the platform used,
1672# enabling this option may lead to badly anti-aliased labels on the edges of
1673# a graph (i.e. they become hard to read).
1674
1675DOT_TRANSPARENT = YES
1676
1677# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
1678# files in one run (i.e. multiple -o and -T options on the command line). This
1679# makes dot run faster, but since only newer versions of dot (>1.8.10)
1680# support this, this feature is disabled by default.
1681
1682DOT_MULTI_TARGETS = NO
1683
1684# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1685# generate a legend page explaining the meaning of the various boxes and
1686# arrows in the dot generated graphs.
1687
1688GENERATE_LEGEND = YES
1689
1690# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1691# remove the intermediate dot files that are used to generate
1692# the various graphs.
1693
1694DOT_CLEANUP = YES
diff --git a/libraries/eet/doc/Makefile.am b/libraries/eet/doc/Makefile.am
deleted file mode 100644
index 4eeb438..0000000
--- a/libraries/eet/doc/Makefile.am
+++ /dev/null
@@ -1,40 +0,0 @@
1
2MAINTAINERCLEANFILES = Makefile.in eet.dox
3
4.PHONY: doc
5
6PACKAGE_DOCNAME = $(PACKAGE_TARNAME)-$(PACKAGE_VERSION)-doc
7
8if EFL_BUILD_DOC
9
10doc-clean:
11 rm -rf html/ latex/ xml/ $(PACKAGE_DOCNAME).tar*
12
13doc: doc-clean
14 $(efl_doxygen)
15 cp $(srcdir)/img/* html/
16 rm -rf $(PACKAGE_DOCNAME).tar*
17 mkdir -p $(PACKAGE_DOCNAME)/doc
18 cp -R html/ latex/ $(PACKAGE_DOCNAME)/doc
19 tar cf $(PACKAGE_DOCNAME).tar $(PACKAGE_DOCNAME)/
20 bzip2 -9 $(PACKAGE_DOCNAME).tar
21 rm -rf $(PACKAGE_DOCNAME)/
22 mv $(PACKAGE_DOCNAME).tar.bz2 $(top_builddir)
23 @echo "Documentation Package: $(PACKAGE_DOCNAME).tar.bz2"
24 @echo "Documentation HTML: doc/html"
25
26clean-local: doc-clean
27
28else
29
30doc:
31 @echo "Documentation not built. Run ./configure --help"
32
33endif
34
35EXTRA_DIST = $(builddir)/Doxyfile \
36 $(srcdir)/e.css \
37 $(srcdir)/foot.html \
38 $(srcdir)/head.html \
39 $(wildcard $(srcdir)/img/*.*) \
40 $(srcdir)/eet.dox.in
diff --git a/libraries/eet/doc/Makefile.in b/libraries/eet/doc/Makefile.in
deleted file mode 100644
index 25de7ec..0000000
--- a/libraries/eet/doc/Makefile.in
+++ /dev/null
@@ -1,443 +0,0 @@
1# Makefile.in generated by automake 1.11.1 from Makefile.am.
2# @configure_input@
3
4# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
5# 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation,
6# Inc.
7# This Makefile.in is free software; the Free Software Foundation
8# gives unlimited permission to copy and/or distribute it,
9# with or without modifications, as long as this notice is preserved.
10
11# This program is distributed in the hope that it will be useful,
12# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
13# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
14# PARTICULAR PURPOSE.
15
16@SET_MAKE@
17VPATH = @srcdir@
18pkgdatadir = $(datadir)/@PACKAGE@
19pkgincludedir = $(includedir)/@PACKAGE@
20pkglibdir = $(libdir)/@PACKAGE@
21pkglibexecdir = $(libexecdir)/@PACKAGE@
22am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
23install_sh_DATA = $(install_sh) -c -m 644
24install_sh_PROGRAM = $(install_sh) -c
25install_sh_SCRIPT = $(install_sh) -c
26INSTALL_HEADER = $(INSTALL_DATA)
27transform = $(program_transform_name)
28NORMAL_INSTALL = :
29PRE_INSTALL = :
30POST_INSTALL = :
31NORMAL_UNINSTALL = :
32PRE_UNINSTALL = :
33POST_UNINSTALL = :
34build_triplet = @build@
35host_triplet = @host@
36subdir = doc
37DIST_COMMON = $(srcdir)/Doxyfile.in $(srcdir)/Makefile.am \
38 $(srcdir)/Makefile.in $(srcdir)/eet.dox.in
39ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
40am__aclocal_m4_deps = $(top_srcdir)/m4/ac_attribute.m4 \
41 $(top_srcdir)/m4/ac_path_generic.m4 \
42 $(top_srcdir)/m4/efl_binary.m4 \
43 $(top_srcdir)/m4/efl_compiler_flag.m4 \
44 $(top_srcdir)/m4/efl_coverage.m4 \
45 $(top_srcdir)/m4/efl_doxygen.m4 \
46 $(top_srcdir)/m4/efl_fnmatch.m4 \
47 $(top_srcdir)/m4/efl_path_max.m4 $(top_srcdir)/m4/efl_tests.m4 \
48 $(top_srcdir)/m4/libtool.m4 $(top_srcdir)/m4/ltoptions.m4 \
49 $(top_srcdir)/m4/ltsugar.m4 $(top_srcdir)/m4/ltversion.m4 \
50 $(top_srcdir)/m4/lt~obsolete.m4 $(top_srcdir)/configure.ac
51am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
52 $(ACLOCAL_M4)
53mkinstalldirs = $(install_sh) -d
54CONFIG_HEADER = $(top_builddir)/config.h
55CONFIG_CLEAN_FILES = Doxyfile eet.dox
56CONFIG_CLEAN_VPATH_FILES =
57AM_V_GEN = $(am__v_GEN_$(V))
58am__v_GEN_ = $(am__v_GEN_$(AM_DEFAULT_VERBOSITY))
59am__v_GEN_0 = @echo " GEN " $@;
60AM_V_at = $(am__v_at_$(V))
61am__v_at_ = $(am__v_at_$(AM_DEFAULT_VERBOSITY))
62am__v_at_0 = @
63SOURCES =
64DIST_SOURCES =
65DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
66ACLOCAL = @ACLOCAL@
67ALLOCA = @ALLOCA@
68AMTAR = @AMTAR@
69AM_DEFAULT_VERBOSITY = @AM_DEFAULT_VERBOSITY@
70AR = @AR@
71AS = @AS@
72AUTOCONF = @AUTOCONF@
73AUTOHEADER = @AUTOHEADER@
74AUTOMAKE = @AUTOMAKE@
75AWK = @AWK@
76CC = @CC@
77CCDEPMODE = @CCDEPMODE@
78CFLAGS = @CFLAGS@
79CHECK_CFLAGS = @CHECK_CFLAGS@
80CHECK_LIBS = @CHECK_LIBS@
81CPP = @CPP@
82CPPFLAGS = @CPPFLAGS@
83CYGPATH_W = @CYGPATH_W@
84DEBUG_CFLAGS = @DEBUG_CFLAGS@
85DEFS = @DEFS@
86DEPDIR = @DEPDIR@
87DLLTOOL = @DLLTOOL@
88DSYMUTIL = @DSYMUTIL@
89DUMPBIN = @DUMPBIN@
90ECHO_C = @ECHO_C@
91ECHO_N = @ECHO_N@
92ECHO_T = @ECHO_T@
93EET_CFLAGS = @EET_CFLAGS@
94EET_CPPFLAGS = @EET_CPPFLAGS@
95EET_LIBS = @EET_LIBS@
96EET_PRG = @EET_PRG@
97EFL_COVERAGE_CFLAGS = @EFL_COVERAGE_CFLAGS@
98EFL_COVERAGE_LIBS = @EFL_COVERAGE_LIBS@
99EFL_EET_BUILD = @EFL_EET_BUILD@
100EFL_FNMATCH_LIBS = @EFL_FNMATCH_LIBS@
101EGREP = @EGREP@
102EINA_CFLAGS = @EINA_CFLAGS@
103EINA_LIBS = @EINA_LIBS@
104EVIL_CFLAGS = @EVIL_CFLAGS@
105EVIL_LIBS = @EVIL_LIBS@
106EXEEXT = @EXEEXT@
107EXOTIC_CFLAGS = @EXOTIC_CFLAGS@
108EXOTIC_LIBS = @EXOTIC_LIBS@
109FGREP = @FGREP@
110GNUTLS_CFLAGS = @GNUTLS_CFLAGS@
111GNUTLS_LIBS = @GNUTLS_LIBS@
112GREP = @GREP@
113INSTALL = @INSTALL@
114INSTALL_DATA = @INSTALL_DATA@
115INSTALL_PROGRAM = @INSTALL_PROGRAM@
116INSTALL_SCRIPT = @INSTALL_SCRIPT@
117INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@
118LD = @LD@
119LDFLAGS = @LDFLAGS@
120LIBGCRYPT_CFLAGS = @LIBGCRYPT_CFLAGS@
121LIBGCRYPT_CONFIG = @LIBGCRYPT_CONFIG@
122LIBGCRYPT_LIBS = @LIBGCRYPT_LIBS@
123LIBOBJS = @LIBOBJS@
124LIBS = @LIBS@
125LIBTOOL = @LIBTOOL@
126LIPO = @LIPO@
127LN_S = @LN_S@
128LTLIBOBJS = @LTLIBOBJS@
129MAKEINFO = @MAKEINFO@
130MKDIR_P = @MKDIR_P@
131NM = @NM@
132NMEDIT = @NMEDIT@
133OBJDUMP = @OBJDUMP@
134OBJEXT = @OBJEXT@
135OPENSSL_CFLAGS = @OPENSSL_CFLAGS@
136OPENSSL_LIBS = @OPENSSL_LIBS@
137OTOOL = @OTOOL@
138OTOOL64 = @OTOOL64@
139PACKAGE = @PACKAGE@
140PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@
141PACKAGE_NAME = @PACKAGE_NAME@
142PACKAGE_STRING = @PACKAGE_STRING@
143PACKAGE_TARNAME = @PACKAGE_TARNAME@
144PACKAGE_URL = @PACKAGE_URL@
145PACKAGE_VERSION = @PACKAGE_VERSION@
146PATH_SEPARATOR = @PATH_SEPARATOR@
147PKG_CONFIG = @PKG_CONFIG@
148PKG_CONFIG_LIBDIR = @PKG_CONFIG_LIBDIR@
149PKG_CONFIG_PATH = @PKG_CONFIG_PATH@
150RANLIB = @RANLIB@
151SED = @SED@
152SET_MAKE = @SET_MAKE@
153SHELL = @SHELL@
154STRIP = @STRIP@
155VERSION = @VERSION@
156VMAJ = @VMAJ@
157abs_builddir = @abs_builddir@
158abs_srcdir = @abs_srcdir@
159abs_top_builddir = @abs_top_builddir@
160abs_top_srcdir = @abs_top_srcdir@
161ac_ct_CC = @ac_ct_CC@
162ac_ct_DUMPBIN = @ac_ct_DUMPBIN@
163am__include = @am__include@
164am__leading_dot = @am__leading_dot@
165am__quote = @am__quote@
166am__tar = @am__tar@
167am__untar = @am__untar@
168bindir = @bindir@
169build = @build@
170build_alias = @build_alias@
171build_cpu = @build_cpu@
172build_os = @build_os@
173build_vendor = @build_vendor@
174builddir = @builddir@
175datadir = @datadir@
176datarootdir = @datarootdir@
177docdir = @docdir@
178dvidir = @dvidir@
179efl_doxygen = @efl_doxygen@
180efl_have_doxygen = @efl_have_doxygen@
181exec_prefix = @exec_prefix@
182have_lcov = @have_lcov@
183host = @host@
184host_alias = @host_alias@
185host_cpu = @host_cpu@
186host_os = @host_os@
187host_vendor = @host_vendor@
188htmldir = @htmldir@
189includedir = @includedir@
190infodir = @infodir@
191install_sh = @install_sh@
192libdir = @libdir@
193libexecdir = @libexecdir@
194localedir = @localedir@
195localstatedir = @localstatedir@
196lt_ECHO = @lt_ECHO@
197lt_enable_auto_import = @lt_enable_auto_import@
198mandir = @mandir@
199mkdir_p = @mkdir_p@
200oldincludedir = @oldincludedir@
201pdfdir = @pdfdir@
202pkgconfig_requires_private = @pkgconfig_requires_private@
203prefix = @prefix@
204program_transform_name = @program_transform_name@
205psdir = @psdir@
206release_info = @release_info@
207requirement_eet = @requirement_eet@
208sbindir = @sbindir@
209sharedstatedir = @sharedstatedir@
210srcdir = @srcdir@
211sysconfdir = @sysconfdir@
212target_alias = @target_alias@
213top_build_prefix = @top_build_prefix@
214top_builddir = @top_builddir@
215top_srcdir = @top_srcdir@
216version_info = @version_info@
217MAINTAINERCLEANFILES = Makefile.in eet.dox
218PACKAGE_DOCNAME = $(PACKAGE_TARNAME)-$(PACKAGE_VERSION)-doc
219EXTRA_DIST = $(builddir)/Doxyfile \
220 $(srcdir)/e.css \
221 $(srcdir)/foot.html \
222 $(srcdir)/head.html \
223 $(wildcard $(srcdir)/img/*.*) \
224 $(srcdir)/eet.dox.in
225
226all: all-am
227
228.SUFFIXES:
229$(srcdir)/Makefile.in: $(srcdir)/Makefile.am $(am__configure_deps)
230 @for dep in $?; do \
231 case '$(am__configure_deps)' in \
232 *$$dep*) \
233 ( cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh ) \
234 && { if test -f $@; then exit 0; else break; fi; }; \
235 exit 1;; \
236 esac; \
237 done; \
238 echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu doc/Makefile'; \
239 $(am__cd) $(top_srcdir) && \
240 $(AUTOMAKE) --gnu doc/Makefile
241.PRECIOUS: Makefile
242Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
243 @case '$?' in \
244 *config.status*) \
245 cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \
246 *) \
247 echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \
248 cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \
249 esac;
250
251$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
252 cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
253
254$(top_srcdir)/configure: $(am__configure_deps)
255 cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
256$(ACLOCAL_M4): $(am__aclocal_m4_deps)
257 cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
258$(am__aclocal_m4_deps):
259Doxyfile: $(top_builddir)/config.status $(srcdir)/Doxyfile.in
260 cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@
261eet.dox: $(top_builddir)/config.status $(srcdir)/eet.dox.in
262 cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@
263
264mostlyclean-libtool:
265 -rm -f *.lo
266
267clean-libtool:
268 -rm -rf .libs _libs
269tags: TAGS
270TAGS:
271
272ctags: CTAGS
273CTAGS:
274
275
276distdir: $(DISTFILES)
277 @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
278 topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
279 list='$(DISTFILES)'; \
280 dist_files=`for file in $$list; do echo $$file; done | \
281 sed -e "s|^$$srcdirstrip/||;t" \
282 -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
283 case $$dist_files in \
284 */*) $(MKDIR_P) `echo "$$dist_files" | \
285 sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
286 sort -u` ;; \
287 esac; \
288 for file in $$dist_files; do \
289 if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
290 if test -d $$d/$$file; then \
291 dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
292 if test -d "$(distdir)/$$file"; then \
293 find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \
294 fi; \
295 if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
296 cp -fpR $(srcdir)/$$file "$(distdir)$$dir" || exit 1; \
297 find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \
298 fi; \
299 cp -fpR $$d/$$file "$(distdir)$$dir" || exit 1; \
300 else \
301 test -f "$(distdir)/$$file" \
302 || cp -p $$d/$$file "$(distdir)/$$file" \
303 || exit 1; \
304 fi; \
305 done
306check-am: all-am
307check: check-am
308all-am: Makefile
309installdirs:
310install: install-am
311install-exec: install-exec-am
312install-data: install-data-am
313uninstall: uninstall-am
314
315install-am: all-am
316 @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
317
318installcheck: installcheck-am
319install-strip:
320 $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
321 install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
322 `test -z '$(STRIP)' || \
323 echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install
324mostlyclean-generic:
325
326clean-generic:
327
328distclean-generic:
329 -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
330 -test . = "$(srcdir)" || test -z "$(CONFIG_CLEAN_VPATH_FILES)" || rm -f $(CONFIG_CLEAN_VPATH_FILES)
331
332maintainer-clean-generic:
333 @echo "This command is intended for maintainers to use"
334 @echo "it deletes files that may require special tools to rebuild."
335 -test -z "$(MAINTAINERCLEANFILES)" || rm -f $(MAINTAINERCLEANFILES)
336@EFL_BUILD_DOC_FALSE@clean-local:
337clean: clean-am
338
339clean-am: clean-generic clean-libtool clean-local mostlyclean-am
340
341distclean: distclean-am
342 -rm -f Makefile
343distclean-am: clean-am distclean-generic
344
345dvi: dvi-am
346
347dvi-am:
348
349html: html-am
350
351html-am:
352
353info: info-am
354
355info-am:
356
357install-data-am:
358
359install-dvi: install-dvi-am
360
361install-dvi-am:
362
363install-exec-am:
364
365install-html: install-html-am
366
367install-html-am:
368
369install-info: install-info-am
370
371install-info-am:
372
373install-man:
374
375install-pdf: install-pdf-am
376
377install-pdf-am:
378
379install-ps: install-ps-am
380
381install-ps-am:
382
383installcheck-am:
384
385maintainer-clean: maintainer-clean-am
386 -rm -f Makefile
387maintainer-clean-am: distclean-am maintainer-clean-generic
388
389mostlyclean: mostlyclean-am
390
391mostlyclean-am: mostlyclean-generic mostlyclean-libtool
392
393pdf: pdf-am
394
395pdf-am:
396
397ps: ps-am
398
399ps-am:
400
401uninstall-am:
402
403.MAKE: install-am install-strip
404
405.PHONY: all all-am check check-am clean clean-generic clean-libtool \
406 clean-local distclean distclean-generic distclean-libtool \
407 distdir dvi dvi-am html html-am info info-am install \
408 install-am install-data install-data-am install-dvi \
409 install-dvi-am install-exec install-exec-am install-html \
410 install-html-am install-info install-info-am install-man \
411 install-pdf install-pdf-am install-ps install-ps-am \
412 install-strip installcheck installcheck-am installdirs \
413 maintainer-clean maintainer-clean-generic mostlyclean \
414 mostlyclean-generic mostlyclean-libtool pdf pdf-am ps ps-am \
415 uninstall uninstall-am
416
417
418.PHONY: doc
419
420@EFL_BUILD_DOC_TRUE@doc-clean:
421@EFL_BUILD_DOC_TRUE@ rm -rf html/ latex/ xml/ $(PACKAGE_DOCNAME).tar*
422
423@EFL_BUILD_DOC_TRUE@doc: doc-clean
424@EFL_BUILD_DOC_TRUE@ $(efl_doxygen)
425@EFL_BUILD_DOC_TRUE@ cp $(srcdir)/img/* html/
426@EFL_BUILD_DOC_TRUE@ rm -rf $(PACKAGE_DOCNAME).tar*
427@EFL_BUILD_DOC_TRUE@ mkdir -p $(PACKAGE_DOCNAME)/doc
428@EFL_BUILD_DOC_TRUE@ cp -R html/ latex/ $(PACKAGE_DOCNAME)/doc
429@EFL_BUILD_DOC_TRUE@ tar cf $(PACKAGE_DOCNAME).tar $(PACKAGE_DOCNAME)/
430@EFL_BUILD_DOC_TRUE@ bzip2 -9 $(PACKAGE_DOCNAME).tar
431@EFL_BUILD_DOC_TRUE@ rm -rf $(PACKAGE_DOCNAME)/
432@EFL_BUILD_DOC_TRUE@ mv $(PACKAGE_DOCNAME).tar.bz2 $(top_builddir)
433@EFL_BUILD_DOC_TRUE@ @echo "Documentation Package: $(PACKAGE_DOCNAME).tar.bz2"
434@EFL_BUILD_DOC_TRUE@ @echo "Documentation HTML: doc/html"
435
436@EFL_BUILD_DOC_TRUE@clean-local: doc-clean
437
438@EFL_BUILD_DOC_FALSE@doc:
439@EFL_BUILD_DOC_FALSE@ @echo "Documentation not built. Run ./configure --help"
440
441# Tell versions [3.59,3.63) of GNU make to not export all variables.
442# Otherwise a system limit (for SysV at least) may be exceeded.
443.NOEXPORT:
diff --git a/libraries/eet/doc/e.css b/libraries/eet/doc/e.css
deleted file mode 100644
index 07ebd1e..0000000
--- a/libraries/eet/doc/e.css
+++ /dev/null
@@ -1,436 +0,0 @@
1/*
2 Author:
3 Andres Blanc <andresblanc@gmail.com>
4 DaveMDS Andreoli <dave@gurumeditation.it>
5
6 Supported Browsers:
7 ie7, opera9, konqueror4 and firefox3
8
9 Please use a different file for ie6, ie5, etc. hacks.
10*/
11
12
13/* Necessary to place the footer at the bottom of the page */
14html, body {
15 height: 100%;
16 margin: 0px;
17 padding: 0px;
18}
19
20#container {
21 min-height: 100%;
22 height: auto !important;
23 height: 100%;
24 margin: 0 auto -53px;
25}
26
27#footer, #push {
28 height: 53px;
29}
30
31
32* html #container {
33 height: 100%;
34}
35
36/* Prevent floating elements overflowing containers */
37.clear {
38 clear: both;
39 width: 0px;
40 height: 0px;
41}
42
43/* Flexible & centered layout from 750 to 960 pixels */
44.layout {
45 max-width: 960px;
46 min-width: 760px;
47 margin-left: auto;
48 margin-right: auto;
49}
50
51body {
52 /*font-family: Lucida Grande, Helvetica, sans-serif;*/
53 font-family: "Bitstream Vera","Vera","Trebuchet MS",Trebuchet,Tahoma,sans-serif
54}
55
56/* Prevent design overflowing the viewport in small resolutions */
57#container {
58 padding-right: 17px;
59 padding-left: 17px;
60 background-image: url(head_bg.png);
61 background-repeat: repeat-x;
62}
63
64#header {
65 width: 100%;
66 height: 102px;
67}
68
69#header h1 {
70 width: 63px;
71 height: 63px;
72 background-image: url(e.png);
73 background-repeat: no-repeat;
74 position: absolute;
75 margin: 0px;
76}
77
78#header h1 span {
79 display: none;
80}
81
82#header h2 {
83 display: none;
84}
85
86/* .menu-container is used to set properties common to .menu and .submenu */
87#header .menu-container {
88}
89
90#header .menu-container ul {
91 list-style-type: none;
92 list-style-position: inside;
93 margin: 0;
94}
95
96#header .menu-container li {
97 display: block;
98 float: right;
99}
100
101#header .menu {
102 height: 63px;
103 display: block;
104 background-image: url(menu_bg.png);
105 background-repeat: repeat-x;
106}
107
108#header .menu ul {
109 height: 100%;
110 display: block;
111 background-image: url(menu_bg_last.png);
112 background-repeat: no-repeat;
113 background-position: top right;
114 padding-right: 17px;
115}
116
117#header .menu li {
118 height: 100%;
119 text-align: center;
120 background-image: url(menu_bg_unsel.png);
121 background-repeat: no-repeat;
122}
123
124#header .menu a {
125 height: 100%;
126 display: block;
127 color: #cdcdcd;
128 text-decoration: none;
129 font-size: 10pt;
130 line-height: 59px;
131 text-align: center;
132 padding: 0px 15px 0px 15px;
133}
134
135#header .menu li:hover {
136 background-image: url(menu_bg_hover.png);
137 background-repeat: no-repeat;
138}
139
140#header .menu li:hover a {
141 color: #FFFFFF;
142}
143
144#header .menu li.current {
145 background-image: url(menu_bg_current.png);
146 background-repeat: no-repeat;
147}
148
149#header .menu li.current a {
150 color: #646464;
151}
152
153
154/* Hide all the submenus but the current */
155#header .submenu ul {
156 display: none;
157}
158
159#header .submenu .current {
160 display: block;
161}
162
163#header .submenu {
164 font: bold 10px verdana,'Bitstream Vera Sans',helvetica,arial,sans-serif;
165 margin-top: 10px;
166}
167
168#header .submenu a {
169 color: #888888;
170 text-decoration: none;
171 font-size: 0.9em;
172 line-height: 15px;
173 padding:0px 5px 0px 5px;
174}
175
176#header .submenu a:hover {
177 color: #444444;
178}
179
180#header .submenu li {
181 border-left: 1px solid #DDDDDD;
182}
183
184#header .submenu li:last-child {
185 border-left: 0;
186}
187
188#header .doxytitle {
189 position: absolute;
190 font-size: 1.8em;
191 font-weight: bold;
192 color: #444444;
193 line-height: 35px;
194}
195
196#header small {
197 font-size: 0.4em;
198}
199
200#footer {
201 background-image: url(foot_bg.png);
202 width: 100%;
203}
204
205#footer table {
206 width: 100%;
207 text-align: center;
208 white-space: nowrap;
209 padding: 5px 30px 5px 30px;
210 font-size: 0.8em;
211 font-family: "Bitstream Vera","Vera","Trebuchet MS",Trebuchet,Tahoma,sans-serif;
212 color: #888888;
213}
214
215#footer td.copyright {
216 width: 100%;
217}
218
219/*
220 Author:
221 Andres Blanc <andresblanc@gmail.com>
222 DaveMDS Andreoli <dave@gurumeditation.it>
223
224 Supported Browsers:
225 ie7, opera9, konqueror4 and firefox3
226
227 Please use a different file for ie6, ie5, etc. hacks.
228*/
229
230
231/* Necessary to place the footer at the bottom of the page */
232html, body {
233 height: 100%;
234 margin: 0px;
235 padding: 0px;
236}
237
238#container {
239 min-height: 100%;
240 height: auto !important;
241 height: 100%;
242 margin: 0 auto -53px;
243}
244
245#footer, #push {
246 height: 53px;
247}
248
249
250* html #container {
251 height: 100%;
252}
253
254/* Prevent floating elements overflowing containers */
255.clear {
256 clear: both;
257 width: 0px;
258 height: 0px;
259}
260
261/* Flexible & centered layout from 750 to 960 pixels */
262.layout {
263 max-width: 960px;
264 min-width: 760px;
265 margin-left: auto;
266 margin-right: auto;
267}
268
269body {
270 /*font-family: Lucida Grande, Helvetica, sans-serif;*/
271 font-family: "Bitstream Vera","Vera","Trebuchet MS",Trebuchet,Tahoma,sans-serif
272}
273
274/* Prevent design overflowing the viewport in small resolutions */
275#container {
276 padding-right: 17px;
277 padding-left: 17px;
278 background-image: url(head_bg.png);
279 background-repeat: repeat-x;
280}
281
282#header {
283 width: 100%;
284 height: 102px;
285}
286
287#header h1 {
288 width: 63px;
289 height: 63px;
290 background-image: url(e.png);
291 background-repeat: no-repeat;
292 position: absolute;
293 margin: 0px;
294}
295
296#header h1 span {
297 display: none;
298}
299
300#header h2 {
301 display: none;
302}
303
304/* .menu-container is used to set properties common to .menu and .submenu */
305#header .menu-container {
306}
307
308#header .menu-container ul {
309 list-style-type: none;
310 list-style-position: inside;
311 margin: 0;
312}
313
314#header .menu-container li {
315 display: block;
316 float: right;
317}
318
319#header .menu {
320 height: 63px;
321 display: block;
322 background-image: url(menu_bg.png);
323 background-repeat: repeat-x;
324}
325
326#header .menu ul {
327 height: 100%;
328 display: block;
329 background-image: url(menu_bg_last.png);
330 background-repeat: no-repeat;
331 background-position: top right;
332 padding-right: 17px;
333}
334
335#header .menu li {
336 height: 100%;
337 text-align: center;
338 background-image: url(menu_bg_unsel.png);
339 background-repeat: no-repeat;
340}
341
342#header .menu a {
343 height: 100%;
344 display: block;
345 color: #cdcdcd;
346 text-decoration: none;
347 font-size: 10pt;
348 line-height: 59px;
349 text-align: center;
350 padding: 0px 15px 0px 15px;
351}
352
353#header .menu li:hover {
354 background-image: url(menu_bg_hover.png);
355 background-repeat: no-repeat;
356}
357
358#header .menu li:hover a {
359 color: #FFFFFF;
360}
361
362#header .menu li.current {
363 background-image: url(menu_bg_current.png);
364 background-repeat: no-repeat;
365}
366
367#header .menu li.current a {
368 color: #646464;
369}
370
371
372/* Hide all the submenus but the current */
373#header .submenu ul {
374 display: none;
375}
376
377#header .submenu .current {
378 display: block;
379}
380
381#header .submenu {
382 font: bold 10px verdana,'Bitstream Vera Sans',helvetica,arial,sans-serif;
383 margin-top: 10px;
384}
385
386#header .submenu a {
387 color: #888888;
388 text-decoration: none;
389 font-size: 0.9em;
390 line-height: 15px;
391 padding:0px 5px 0px 5px;
392}
393
394#header .submenu a:hover {
395 color: #444444;
396}
397
398#header .submenu li {
399 border-left: 1px solid #DDDDDD;
400}
401
402#header .submenu li:last-child {
403 border-left: 0;
404}
405
406#header .doxytitle {
407 position: absolute;
408 font-size: 1.8em;
409 font-weight: bold;
410 color: #444444;
411 line-height: 35px;
412}
413
414#header small {
415 font-size: 0.4em;
416}
417
418#footer {
419 background-image: url(foot_bg.png);
420 width: 100%;
421}
422
423#footer table {
424 width: 100%;
425 text-align: center;
426 white-space: nowrap;
427 padding: 5px 30px 5px 30px;
428 font-size: 0.8em;
429 font-family: "Bitstream Vera","Vera","Trebuchet MS",Trebuchet,Tahoma,sans-serif;
430 color: #888888;
431}
432
433#footer td.copyright {
434 width: 100%;
435}
436
diff --git a/libraries/eet/doc/eet.dox.in b/libraries/eet/doc/eet.dox.in
deleted file mode 100644
index e69de29..0000000
--- a/libraries/eet/doc/eet.dox.in
+++ /dev/null
diff --git a/libraries/eet/doc/foot.html b/libraries/eet/doc/foot.html
deleted file mode 100644
index 3a96978..0000000
--- a/libraries/eet/doc/foot.html
+++ /dev/null
@@ -1,20 +0,0 @@
1
2 <div id="push"></div>
3 </div> <!-- #content -->
4 </div> <!-- .layout -->
5
6 </div> <!-- #container -->
7
8
9 <div id="footer">
10 <table><tr>
11 <td class="poweredby"><img src="doxygen.png"></td>
12 <td>Samsung Electronics is supporting the EFL Documentation Project</td>
13 <td class="copyright">Copyright &copy;$year Enlightenment</td>
14 <td class="generated">Docs generated $datetime</td>
15 </tr></table>
16 </div>
17
18
19</body>
20</html>
diff --git a/libraries/eet/doc/head.html b/libraries/eet/doc/head.html
deleted file mode 100644
index 519631b..0000000
--- a/libraries/eet/doc/head.html
+++ /dev/null
@@ -1,65 +0,0 @@
1<html>
2<head>
3 <title>$title</title>
4 <meta http-equiv="content-type" content="text/html;charset=UTF-8">
5 <meta name="author" content="Andres Blanc" >
6
7 <link rel="icon" href="img/favicon.png" type="image/x-icon">
8 <link rel="shortcut icon" href="img/favicon.png" type="image/x-icon">
9 <link rel="icon" href="img/favicon.png" type="image/ico">
10 <link rel="shortcut icon" href="img/favicon.png" type="image/ico">
11
12 <link rel="stylesheet" type="text/css" media="screen" href="e.css">
13 <link rel="stylesheet" type="text/css" media="screen" href="edoxy.css">
14</head>
15
16<body>
17
18<div id="container">
19
20<div id="header">
21<div class="layout">
22
23 <h1><span>Enlightenment</span></h1>
24 <h2><span>Beauty at your fingertips</span></h2>
25
26 <div class="menu-container">
27 <div class="menu">
28 <ul>
29 <li class="current"><a href="http://web.enlightenment.org/p.php?p=docs">Docs</a></li>
30 <li><a href="http://trac.enlightenment.org/e">Tracker</a></li>
31 <li><a href="http://www.enlightenment.org/p.php?p=contact">Contact</a></li>
32 <li><a href="http://www.enlightenment.org/p.php?p=contribute">Contribute</a></li>
33 <li><a href="http://www.enlightenment.org/p.php?p=support">Support</a></li>
34 <li><a href="http://www.enlightenment.org/p.php?p=download">Download</a></li>
35 <li><a href="http://www.enlightenment.org/p.php?p=about">About</a></li>
36 <li><a href="http://www.enlightenment.org/p.php?p=news">News</a></li>
37 <li><a href="http://www.enlightenment.org/">Home</a></li>
38 </ul>
39 </div>
40 </div>
41
42 <div class="doxytitle">
43 $projectname Documentation <small>at $date</small>
44 </div>
45
46 <div class="menu-container">
47 <div class="submenu">
48 <ul class="current">
49 <li><a href="Examples.html">Examples</a></li>
50 <li><a href="files.html">Files</a></li>
51 <li><a href="modules.html">Modules</a></li>
52 <li><a href="globals.html">Globals</a></li>
53 <li><a href="pages.html">Related Pages</a></li>
54 <li class="current"><a href="index.html">Main Page</a></li>
55 </ul>
56 </div>
57 </div>
58
59
60 <div class="clear"></div>
61</div>
62</div>
63
64<div id="content">
65<div class="layout">
diff --git a/libraries/eet/doc/img/e.png b/libraries/eet/doc/img/e.png
deleted file mode 100755
index b3884a5..0000000
--- a/libraries/eet/doc/img/e.png
+++ /dev/null
Binary files differ
diff --git a/libraries/eet/doc/img/e_big.png b/libraries/eet/doc/img/e_big.png
deleted file mode 100755
index d42aeb4..0000000
--- a/libraries/eet/doc/img/e_big.png
+++ /dev/null
Binary files differ
diff --git a/libraries/eet/doc/img/edoxy.css b/libraries/eet/doc/img/edoxy.css
deleted file mode 100755
index 616a0c5..0000000
--- a/libraries/eet/doc/img/edoxy.css
+++ /dev/null
@@ -1,966 +0,0 @@
1/*
2 * This file contain a custom doxygen style to match e.org graphics
3 */
4
5
6
7/* BODY,H1,H2,H3,H4,H5,H6,P,CENTER,TD,TH,UL,DL,DIV {
8 font-family: Geneva, Arial, Helvetica, sans-serif;
9}*/
10BODY, TD {
11 font-size: 12px;
12}
13H1 {
14 text-align: center;
15 font-size: 160%;
16}
17H2 {
18 font-size: 120%;
19}
20H3 {
21 font-size: 100%;
22}
23CAPTION {
24 font-weight: bold
25}
26DIV.qindex {
27 width: 100%;
28 background-color: #e8eef2;
29 border: 1px solid #84b0c7;
30 text-align: center;
31 margin: 2px;
32 padding: 2px;
33 line-height: 140%;
34}
35DIV.navpath {
36 width: 100%;
37 background-color: #e8eef2;
38 border: 1px solid #84b0c7;
39 text-align: center;
40 margin: 2px;
41 padding: 2px;
42 line-height: 140%;
43}
44DIV.navtab {
45 background-color: #e8eef2;
46 border: 1px solid #84b0c7;
47 text-align: center;
48 margin: 2px;
49 margin-right: 15px;
50 padding: 2px;
51}
52TD.navtab {
53 font-size: 70%;
54}
55A.qindex {
56 text-decoration: none;
57 font-weight: bold;
58 color: #1A419D;
59}
60A.qindex:visited {
61 text-decoration: none;
62 font-weight: bold;
63 color: #1A419D
64}
65A.qindex:hover {
66 text-decoration: none;
67 background-color: #ddddff;
68}
69A.qindexHL {
70 text-decoration: none;
71 font-weight: bold;
72 background-color: #6666cc;
73 color: #ffffff;
74 border: 1px double #9295C2;
75}
76A.qindexHL:hover {
77 text-decoration: none;
78 background-color: #6666cc;
79 color: #ffffff;
80}
81A.qindexHL:visited {
82 text-decoration: none;
83 background-color: #6666cc;
84 color: #ffffff
85}
86A.el {
87 text-decoration: none;
88 font-weight: bold
89}
90A.elRef {
91 font-weight: bold
92}
93A.code:link {
94 text-decoration: none;
95 font-weight: normal;
96 color: #0000FF
97}
98A.code:visited {
99 text-decoration: none;
100 font-weight: normal;
101 color: #0000FF
102}
103A.codeRef:link {
104 font-weight: normal;
105 color: #0000FF
106}
107A.codeRef:visited {
108 font-weight: normal;
109 color: #0000FF
110}
111A:hover, A:visited:hover {
112 text-decoration: none;
113 /* background-color: #f2f2ff; */
114 color: #000055;
115}
116A.anchor {
117 color: #000;
118}
119DL.el {
120 margin-left: -1cm
121}
122.fragment {
123 font-family: monospace, fixed;
124 font-size: 95%;
125}
126PRE.fragment {
127 border: 1px solid #CCCCCC;
128 background-color: #f5f5f5;
129 margin-top: 4px;
130 margin-bottom: 4px;
131 margin-left: 2px;
132 margin-right: 8px;
133 padding-left: 6px;
134 padding-right: 6px;
135 padding-top: 4px;
136 padding-bottom: 4px;
137}
138DIV.ah {
139 background-color: black;
140 font-weight: bold;
141 color: #ffffff;
142 margin-bottom: 3px;
143 margin-top: 3px
144}
145
146DIV.groupHeader {
147 margin-left: 16px;
148 margin-top: 12px;
149 margin-bottom: 6px;
150 font-weight: bold;
151}
152DIV.groupText {
153 margin-left: 16px;
154 font-style: italic;
155 font-size: 90%
156}
157/*BODY {
158 background: white;
159 color: black;
160 margin-right: 20px;
161 margin-left: 20px;
162}*/
163TD.indexkey {
164 background-color: #e8eef2;
165 font-weight: bold;
166 padding-right : 10px;
167 padding-top : 2px;
168 padding-left : 10px;
169 padding-bottom : 2px;
170 margin-left : 0px;
171 margin-right : 0px;
172 margin-top : 2px;
173 margin-bottom : 2px;
174 border: 1px solid #CCCCCC;
175}
176TD.indexvalue {
177 background-color: #e8eef2;
178 font-style: italic;
179 padding-right : 10px;
180 padding-top : 2px;
181 padding-left : 10px;
182 padding-bottom : 2px;
183 margin-left : 0px;
184 margin-right : 0px;
185 margin-top : 2px;
186 margin-bottom : 2px;
187 border: 1px solid #CCCCCC;
188}
189TR.memlist {
190 background-color: #f0f0f0;
191}
192P.formulaDsp {
193 text-align: center;
194}
195IMG.formulaDsp {
196}
197IMG.formulaInl {
198 vertical-align: middle;
199}
200SPAN.keyword { color: #008000 }
201SPAN.keywordtype { color: #604020 }
202SPAN.keywordflow { color: #e08000 }
203SPAN.comment { color: #800000 }
204SPAN.preprocessor { color: #806020 }
205SPAN.stringliteral { color: #002080 }
206SPAN.charliteral { color: #008080 }
207SPAN.vhdldigit { color: #ff00ff }
208SPAN.vhdlchar { color: #000000 }
209SPAN.vhdlkeyword { color: #700070 }
210SPAN.vhdllogic { color: #ff0000 }
211
212.mdescLeft {
213 padding: 0px 8px 4px 8px;
214 font-size: 80%;
215 font-style: italic;
216 background-color: #FAFAFA;
217 border-top: 1px none #E0E0E0;
218 border-right: 1px none #E0E0E0;
219 border-bottom: 1px none #E0E0E0;
220 border-left: 1px none #E0E0E0;
221 margin: 0px;
222}
223.mdescRight {
224 padding: 0px 8px 4px 8px;
225 font-size: 80%;
226 font-style: italic;
227 background-color: #FAFAFA;
228 border-top: 1px none #E0E0E0;
229 border-right: 1px none #E0E0E0;
230 border-bottom: 1px none #E0E0E0;
231 border-left: 1px none #E0E0E0;
232 margin: 0px;
233}
234.memItemLeft {
235 padding: 1px 0px 0px 8px;
236 margin: 4px;
237 border-top-width: 1px;
238 border-right-width: 1px;
239 border-bottom-width: 1px;
240 border-left-width: 1px;
241 border-top-color: #E0E0E0;
242 border-right-color: #E0E0E0;
243 border-bottom-color: #E0E0E0;
244 border-left-color: #E0E0E0;
245 border-top-style: solid;
246 border-right-style: none;
247 border-bottom-style: none;
248 border-left-style: none;
249 background-color: #FAFAFA;
250 font-size: 80%;
251}
252.memItemRight {
253 padding: 1px 8px 0px 8px;
254 margin: 4px;
255 border-top-width: 1px;
256 border-right-width: 1px;
257 border-bottom-width: 1px;
258 border-left-width: 1px;
259 border-top-color: #E0E0E0;
260 border-right-color: #E0E0E0;
261 border-bottom-color: #E0E0E0;
262 border-left-color: #E0E0E0;
263 border-top-style: solid;
264 border-right-style: none;
265 border-bottom-style: none;
266 border-left-style: none;
267 background-color: #FAFAFA;
268 font-size: 80%;
269}
270.memTemplItemLeft {
271 padding: 1px 0px 0px 8px;
272 margin: 4px;
273 border-top-width: 1px;
274 border-right-width: 1px;
275 border-bottom-width: 1px;
276 border-left-width: 1px;
277 border-top-color: #E0E0E0;
278 border-right-color: #E0E0E0;
279 border-bottom-color: #E0E0E0;
280 border-left-color: #E0E0E0;
281 border-top-style: none;
282 border-right-style: none;
283 border-bottom-style: none;
284 border-left-style: none;
285 background-color: #FAFAFA;
286 font-size: 80%;
287}
288.memTemplItemRight {
289 padding: 1px 8px 0px 8px;
290 margin: 4px;
291 border-top-width: 1px;
292 border-right-width: 1px;
293 border-bottom-width: 1px;
294 border-left-width: 1px;
295 border-top-color: #E0E0E0;
296 border-right-color: #E0E0E0;
297 border-bottom-color: #E0E0E0;
298 border-left-color: #E0E0E0;
299 border-top-style: none;
300 border-right-style: none;
301 border-bottom-style: none;
302 border-left-style: none;
303 background-color: #FAFAFA;
304 font-size: 80%;
305}
306.memTemplParams {
307 padding: 1px 0px 0px 8px;
308 margin: 4px;
309 border-top-width: 1px;
310 border-right-width: 1px;
311 border-bottom-width: 1px;
312 border-left-width: 1px;
313 border-top-color: #E0E0E0;
314 border-right-color: #E0E0E0;
315 border-bottom-color: #E0E0E0;
316 border-left-color: #E0E0E0;
317 border-top-style: solid;
318 border-right-style: none;
319 border-bottom-style: none;
320 border-left-style: none;
321 color: #606060;
322 background-color: #FAFAFA;
323 font-size: 80%;
324}
325.search {
326 color: #003399;
327 font-weight: bold;
328}
329FORM.search {
330 margin-bottom: 0px;
331 margin-top: 0px;
332}
333INPUT.search {
334 font-size: 75%;
335 color: #000080;
336 font-weight: normal;
337 background-color: #e8eef2;
338}
339TD.tiny {
340 font-size: 75%;
341}
342a {
343 color: #1A41A8;
344}
345a:visited {
346 color: #2A3798;
347}
348.dirtab {
349 padding: 4px;
350 border-collapse: collapse;
351 border: 1px solid #84b0c7;
352}
353TH.dirtab {
354 background: #e8eef2;
355 font-weight: bold;
356}
357HR {
358 height: 1px;
359 border: none;
360 border-top: 1px solid black;
361}
362
363/* Style for detailed member documentation */
364.memtemplate {
365 font-size: 80%;
366 color: #606060;
367 font-weight: normal;
368 margin-left: 3px;
369}
370.memnav {
371 background-color: #e8eef2;
372 border: 1px solid #84b0c7;
373 text-align: center;
374 margin: 2px;
375 margin-right: 15px;
376 padding: 2px;
377}
378.memitem {
379 padding: 4px;
380 background-color: #eef3f5;
381 border-width: 1px;
382 border-style: solid;
383 border-color: #dedeee;
384 -moz-border-radius: 8px 8px 8px 8px;
385}
386.memname {
387 white-space: nowrap;
388 font-weight: bold;
389}
390.memdoc{
391 padding-left: 10px;
392}
393.memproto {
394 background-color: #d5e1e8;
395 width: 100%;
396 border-width: 1px;
397 border-style: solid;
398 border-color: #84b0c7;
399 font-weight: bold;
400 -moz-border-radius: 8px 8px 8px 8px;
401}
402.paramkey {
403 text-align: right;
404}
405.paramtype {
406 white-space: nowrap;
407}
408.paramname {
409 color: #602020;
410 font-style: italic;
411 white-space: nowrap;
412}
413/* End Styling for detailed member documentation */
414
415/* for the tree view */
416.ftvtree {
417 font-family: sans-serif;
418 margin:0.5em;
419}
420/* these are for tree view when used as main index */
421.directory {
422 font-size: 9pt;
423 font-weight: bold;
424}
425.directory h3 {
426 margin: 0px;
427 margin-top: 1em;
428 font-size: 11pt;
429}
430
431/* The following two styles can be used to replace the root node title */
432/* with an image of your choice. Simply uncomment the next two styles, */
433/* specify the name of your image and be sure to set 'height' to the */
434/* proper pixel height of your image. */
435
436/* .directory h3.swap { */
437/* height: 61px; */
438/* background-repeat: no-repeat; */
439/* background-image: url("yourimage.gif"); */
440/* } */
441/* .directory h3.swap span { */
442/* display: none; */
443/* } */
444
445.directory > h3 {
446 margin-top: 0;
447}
448.directory p {
449 margin: 0px;
450 white-space: nowrap;
451}
452.directory div {
453 display: none;
454 margin: 0px;
455}
456.directory img {
457 vertical-align: -30%;
458}
459/* these are for tree view when not used as main index */
460.directory-alt {
461 font-size: 100%;
462 font-weight: bold;
463}
464.directory-alt h3 {
465 margin: 0px;
466 margin-top: 1em;
467 font-size: 11pt;
468}
469.directory-alt > h3 {
470 margin-top: 0;
471}
472.directory-alt p {
473 margin: 0px;
474 white-space: nowrap;
475}
476.directory-alt div {
477 display: none;
478 margin: 0px;
479}
480.directory-alt img {
481 vertical-align: -30%;
482}
483
484/*
485 * This file contain a custom doxygen style to match e.org graphics
486 */
487
488
489
490/* BODY,H1,H2,H3,H4,H5,H6,P,CENTER,TD,TH,UL,DL,DIV {
491 font-family: Geneva, Arial, Helvetica, sans-serif;
492}*/
493BODY, TD {
494 font-size: 12px;
495}
496H1 {
497 text-align: center;
498 font-size: 160%;
499}
500H2 {
501 font-size: 120%;
502}
503H3 {
504 font-size: 100%;
505}
506CAPTION {
507 font-weight: bold
508}
509DIV.qindex {
510 width: 100%;
511 background-color: #e8eef2;
512 border: 1px solid #84b0c7;
513 text-align: center;
514 margin: 2px;
515 padding: 2px;
516 line-height: 140%;
517}
518DIV.navpath {
519 width: 100%;
520 background-color: #e8eef2;
521 border: 1px solid #84b0c7;
522 text-align: center;
523 margin: 2px;
524 padding: 2px;
525 line-height: 140%;
526}
527DIV.navtab {
528 background-color: #e8eef2;
529 border: 1px solid #84b0c7;
530 text-align: center;
531 margin: 2px;
532 margin-right: 15px;
533 padding: 2px;
534}
535TD.navtab {
536 font-size: 70%;
537}
538A.qindex {
539 text-decoration: none;
540 font-weight: bold;
541 color: #1A419D;
542}
543A.qindex:visited {
544 text-decoration: none;
545 font-weight: bold;
546 color: #1A419D
547}
548A.qindex:hover {
549 text-decoration: none;
550 background-color: #ddddff;
551}
552A.qindexHL {
553 text-decoration: none;
554 font-weight: bold;
555 background-color: #6666cc;
556 color: #ffffff;
557 border: 1px double #9295C2;
558}
559A.qindexHL:hover {
560 text-decoration: none;
561 background-color: #6666cc;
562 color: #ffffff;
563}
564A.qindexHL:visited {
565 text-decoration: none;
566 background-color: #6666cc;
567 color: #ffffff
568}
569A.el {
570 text-decoration: none;
571 font-weight: bold
572}
573A.elRef {
574 font-weight: bold
575}
576A.code:link {
577 text-decoration: none;
578 font-weight: normal;
579 color: #0000FF
580}
581A.code:visited {
582 text-decoration: none;
583 font-weight: normal;
584 color: #0000FF
585}
586A.codeRef:link {
587 font-weight: normal;
588 color: #0000FF
589}
590A.codeRef:visited {
591 font-weight: normal;
592 color: #0000FF
593}
594A:hover, A:visited:hover {
595 text-decoration: none;
596 /* background-color: #f2f2ff; */
597 color: #000055;
598}
599A.anchor {
600 color: #000;
601}
602DL.el {
603 margin-left: -1cm
604}
605.fragment {
606 font-family: monospace, fixed;
607 font-size: 95%;
608}
609PRE.fragment {
610 border: 1px solid #CCCCCC;
611 background-color: #f5f5f5;
612 margin-top: 4px;
613 margin-bottom: 4px;
614 margin-left: 2px;
615 margin-right: 8px;
616 padding-left: 6px;
617 padding-right: 6px;
618 padding-top: 4px;
619 padding-bottom: 4px;
620}
621DIV.ah {
622 background-color: black;
623 font-weight: bold;
624 color: #ffffff;
625 margin-bottom: 3px;
626 margin-top: 3px
627}
628
629DIV.groupHeader {
630 margin-left: 16px;
631 margin-top: 12px;
632 margin-bottom: 6px;
633 font-weight: bold;
634}
635DIV.groupText {
636 margin-left: 16px;
637 font-style: italic;
638 font-size: 90%
639}
640/*BODY {
641 background: white;
642 color: black;
643 margin-right: 20px;
644 margin-left: 20px;
645}*/
646TD.indexkey {
647 background-color: #e8eef2;
648 font-weight: bold;
649 padding-right : 10px;
650 padding-top : 2px;
651 padding-left : 10px;
652 padding-bottom : 2px;
653 margin-left : 0px;
654 margin-right : 0px;
655 margin-top : 2px;
656 margin-bottom : 2px;
657 border: 1px solid #CCCCCC;
658}
659TD.indexvalue {
660 background-color: #e8eef2;
661 font-style: italic;
662 padding-right : 10px;
663 padding-top : 2px;
664 padding-left : 10px;
665 padding-bottom : 2px;
666 margin-left : 0px;
667 margin-right : 0px;
668 margin-top : 2px;
669 margin-bottom : 2px;
670 border: 1px solid #CCCCCC;
671}
672TR.memlist {
673 background-color: #f0f0f0;
674}
675P.formulaDsp {
676 text-align: center;
677}
678IMG.formulaDsp {
679}
680IMG.formulaInl {
681 vertical-align: middle;
682}
683SPAN.keyword { color: #008000 }
684SPAN.keywordtype { color: #604020 }
685SPAN.keywordflow { color: #e08000 }
686SPAN.comment { color: #800000 }
687SPAN.preprocessor { color: #806020 }
688SPAN.stringliteral { color: #002080 }
689SPAN.charliteral { color: #008080 }
690SPAN.vhdldigit { color: #ff00ff }
691SPAN.vhdlchar { color: #000000 }
692SPAN.vhdlkeyword { color: #700070 }
693SPAN.vhdllogic { color: #ff0000 }
694
695.mdescLeft {
696 padding: 0px 8px 4px 8px;
697 font-size: 80%;
698 font-style: italic;
699 background-color: #FAFAFA;
700 border-top: 1px none #E0E0E0;
701 border-right: 1px none #E0E0E0;
702 border-bottom: 1px none #E0E0E0;
703 border-left: 1px none #E0E0E0;
704 margin: 0px;
705}
706.mdescRight {
707 padding: 0px 8px 4px 8px;
708 font-size: 80%;
709 font-style: italic;
710 background-color: #FAFAFA;
711 border-top: 1px none #E0E0E0;
712 border-right: 1px none #E0E0E0;
713 border-bottom: 1px none #E0E0E0;
714 border-left: 1px none #E0E0E0;
715 margin: 0px;
716}
717.memItemLeft {
718 padding: 1px 0px 0px 8px;
719 margin: 4px;
720 border-top-width: 1px;
721 border-right-width: 1px;
722 border-bottom-width: 1px;
723 border-left-width: 1px;
724 border-top-color: #E0E0E0;
725 border-right-color: #E0E0E0;
726 border-bottom-color: #E0E0E0;
727 border-left-color: #E0E0E0;
728 border-top-style: solid;
729 border-right-style: none;
730 border-bottom-style: none;
731 border-left-style: none;
732 background-color: #FAFAFA;
733 font-size: 80%;
734}
735.memItemRight {
736 padding: 1px 8px 0px 8px;
737 margin: 4px;
738 border-top-width: 1px;
739 border-right-width: 1px;
740 border-bottom-width: 1px;
741 border-left-width: 1px;
742 border-top-color: #E0E0E0;
743 border-right-color: #E0E0E0;
744 border-bottom-color: #E0E0E0;
745 border-left-color: #E0E0E0;
746 border-top-style: solid;
747 border-right-style: none;
748 border-bottom-style: none;
749 border-left-style: none;
750 background-color: #FAFAFA;
751 font-size: 80%;
752}
753.memTemplItemLeft {
754 padding: 1px 0px 0px 8px;
755 margin: 4px;
756 border-top-width: 1px;
757 border-right-width: 1px;
758 border-bottom-width: 1px;
759 border-left-width: 1px;
760 border-top-color: #E0E0E0;
761 border-right-color: #E0E0E0;
762 border-bottom-color: #E0E0E0;
763 border-left-color: #E0E0E0;
764 border-top-style: none;
765 border-right-style: none;
766 border-bottom-style: none;
767 border-left-style: none;
768 background-color: #FAFAFA;
769 font-size: 80%;
770}
771.memTemplItemRight {
772 padding: 1px 8px 0px 8px;
773 margin: 4px;
774 border-top-width: 1px;
775 border-right-width: 1px;
776 border-bottom-width: 1px;
777 border-left-width: 1px;
778 border-top-color: #E0E0E0;
779 border-right-color: #E0E0E0;
780 border-bottom-color: #E0E0E0;
781 border-left-color: #E0E0E0;
782 border-top-style: none;
783 border-right-style: none;
784 border-bottom-style: none;
785 border-left-style: none;
786 background-color: #FAFAFA;
787 font-size: 80%;
788}
789.memTemplParams {
790 padding: 1px 0px 0px 8px;
791 margin: 4px;
792 border-top-width: 1px;
793 border-right-width: 1px;
794 border-bottom-width: 1px;
795 border-left-width: 1px;
796 border-top-color: #E0E0E0;
797 border-right-color: #E0E0E0;
798 border-bottom-color: #E0E0E0;
799 border-left-color: #E0E0E0;
800 border-top-style: solid;
801 border-right-style: none;
802 border-bottom-style: none;
803 border-left-style: none;
804 color: #606060;
805 background-color: #FAFAFA;
806 font-size: 80%;
807}
808.search {
809 color: #003399;
810 font-weight: bold;
811}
812FORM.search {
813 margin-bottom: 0px;
814 margin-top: 0px;
815}
816INPUT.search {
817 font-size: 75%;
818 color: #000080;
819 font-weight: normal;
820 background-color: #e8eef2;
821}
822TD.tiny {
823 font-size: 75%;
824}
825a {
826 color: #1A41A8;
827}
828a:visited {
829 color: #2A3798;
830}
831.dirtab {
832 padding: 4px;
833 border-collapse: collapse;
834 border: 1px solid #84b0c7;
835}
836TH.dirtab {
837 background: #e8eef2;
838 font-weight: bold;
839}
840HR {
841 height: 1px;
842 border: none;
843 border-top: 1px solid black;
844}
845
846/* Style for detailed member documentation */
847.memtemplate {
848 font-size: 80%;
849 color: #606060;
850 font-weight: normal;
851 margin-left: 3px;
852}
853.memnav {
854 background-color: #e8eef2;
855 border: 1px solid #84b0c7;
856 text-align: center;
857 margin: 2px;
858 margin-right: 15px;
859 padding: 2px;
860}
861.memitem {
862 padding: 4px;
863 background-color: #eef3f5;
864 border-width: 1px;
865 border-style: solid;
866 border-color: #dedeee;
867 -moz-border-radius: 8px 8px 8px 8px;
868}
869.memname {
870 white-space: nowrap;
871 font-weight: bold;
872}
873.memdoc{
874 padding-left: 10px;
875}
876.memproto {
877 background-color: #d5e1e8;
878 width: 100%;
879 border-width: 1px;
880 border-style: solid;
881 border-color: #84b0c7;
882 font-weight: bold;
883 -moz-border-radius: 8px 8px 8px 8px;
884}
885.paramkey {
886 text-align: right;
887}
888.paramtype {
889 white-space: nowrap;
890}
891.paramname {
892 color: #602020;
893 font-style: italic;
894 white-space: nowrap;
895}
896/* End Styling for detailed member documentation */
897
898/* for the tree view */
899.ftvtree {
900 font-family: sans-serif;
901 margin:0.5em;
902}
903/* these are for tree view when used as main index */
904.directory {
905 font-size: 9pt;
906 font-weight: bold;
907}
908.directory h3 {
909 margin: 0px;
910 margin-top: 1em;
911 font-size: 11pt;
912}
913
914/* The following two styles can be used to replace the root node title */
915/* with an image of your choice. Simply uncomment the next two styles, */
916/* specify the name of your image and be sure to set 'height' to the */
917/* proper pixel height of your image. */
918
919/* .directory h3.swap { */
920/* height: 61px; */
921/* background-repeat: no-repeat; */
922/* background-image: url("yourimage.gif"); */
923/* } */
924/* .directory h3.swap span { */
925/* display: none; */
926/* } */
927
928.directory > h3 {
929 margin-top: 0;
930}
931.directory p {
932 margin: 0px;
933 white-space: nowrap;
934}
935.directory div {
936 display: none;
937 margin: 0px;
938}
939.directory img {
940 vertical-align: -30%;
941}
942/* these are for tree view when not used as main index */
943.directory-alt {
944 font-size: 100%;
945 font-weight: bold;
946}
947.directory-alt h3 {
948 margin: 0px;
949 margin-top: 1em;
950 font-size: 11pt;
951}
952.directory-alt > h3 {
953 margin-top: 0;
954}
955.directory-alt p {
956 margin: 0px;
957 white-space: nowrap;
958}
959.directory-alt div {
960 display: none;
961 margin: 0px;
962}
963.directory-alt img {
964 vertical-align: -30%;
965}
966
diff --git a/libraries/eet/doc/img/eet.png b/libraries/eet/doc/img/eet.png
deleted file mode 100644
index 47597a8..0000000
--- a/libraries/eet/doc/img/eet.png
+++ /dev/null
Binary files differ
diff --git a/libraries/eet/doc/img/foot_bg.png b/libraries/eet/doc/img/foot_bg.png
deleted file mode 100755
index b24f3a4..0000000
--- a/libraries/eet/doc/img/foot_bg.png
+++ /dev/null
Binary files differ
diff --git a/libraries/eet/doc/img/head_bg.png b/libraries/eet/doc/img/head_bg.png
deleted file mode 100755
index 081dc13..0000000
--- a/libraries/eet/doc/img/head_bg.png
+++ /dev/null
Binary files differ
diff --git a/libraries/eet/doc/img/hilite.png b/libraries/eet/doc/img/hilite.png
deleted file mode 100644
index 88a4381..0000000
--- a/libraries/eet/doc/img/hilite.png
+++ /dev/null
Binary files differ
diff --git a/libraries/eet/doc/img/menu_bg.png b/libraries/eet/doc/img/menu_bg.png
deleted file mode 100755
index e978743..0000000
--- a/libraries/eet/doc/img/menu_bg.png
+++ /dev/null
Binary files differ
diff --git a/libraries/eet/doc/img/menu_bg_current.png b/libraries/eet/doc/img/menu_bg_current.png
deleted file mode 100755
index de97c92..0000000
--- a/libraries/eet/doc/img/menu_bg_current.png
+++ /dev/null
Binary files differ
diff --git a/libraries/eet/doc/img/menu_bg_hover.png b/libraries/eet/doc/img/menu_bg_hover.png
deleted file mode 100755
index 3fd851d..0000000
--- a/libraries/eet/doc/img/menu_bg_hover.png
+++ /dev/null
Binary files differ
diff --git a/libraries/eet/doc/img/menu_bg_last.png b/libraries/eet/doc/img/menu_bg_last.png
deleted file mode 100755
index 88c116c..0000000
--- a/libraries/eet/doc/img/menu_bg_last.png
+++ /dev/null
Binary files differ
diff --git a/libraries/eet/doc/img/menu_bg_unsel.png b/libraries/eet/doc/img/menu_bg_unsel.png
deleted file mode 100755
index 50e5fd8..0000000
--- a/libraries/eet/doc/img/menu_bg_unsel.png
+++ /dev/null
Binary files differ
generated by cgit v1.1 at 2024-10-31 13:02:51 +0000