summaryrefslogtreecommitdiff
path: root/legacy/eet
diff options
context:
space:
mode:
authorCarsten Haitzler <raster@rasterman.com>2012-11-13 23:52:18 +0000
committerCarsten Haitzler <raster@rasterman.com>2012-11-13 23:52:18 +0000
commitcd926b304dc8f072d99d55f90ef4bd6ad9d3a62f (patch)
treeab108ceeb5d9b72e9998c7e5c58d7ba3aaeed5e7 /legacy/eet
parent30965869f0e3aaea6adb2765e98a6797e9f03749 (diff)
move libs already in EFL into... IN-EFL - this will stop/prevent/limit
thnigs like people using them and patching them, etc. SVN revision: 79255
Diffstat (limited to 'legacy/eet')
-rw-r--r--legacy/eet/.gitignore45
-rw-r--r--legacy/eet/AUTHORS16
-rw-r--r--legacy/eet/INSTALL236
-rw-r--r--legacy/eet/Makefile.am89
-rwxr-xr-xlegacy/eet/autogen.sh38
-rw-r--r--legacy/eet/configure.ac541
-rw-r--r--legacy/eet/doc/Doxyfile.in1677
-rw-r--r--legacy/eet/doc/Makefile.am41
-rw-r--r--legacy/eet/doc/e.css436
-rw-r--r--legacy/eet/doc/eet.dox.in0
-rw-r--r--legacy/eet/doc/examples.dox184
-rw-r--r--legacy/eet/doc/head.html65
-rwxr-xr-xlegacy/eet/doc/img/e.pngbin3825 -> 0 bytes
-rwxr-xr-xlegacy/eet/doc/img/e_big.pngbin30052 -> 0 bytes
-rwxr-xr-xlegacy/eet/doc/img/edoxy.css966
-rw-r--r--legacy/eet/doc/img/eet.pngbin74944 -> 0 bytes
-rwxr-xr-xlegacy/eet/doc/img/foot_bg.pngbin173 -> 0 bytes
-rwxr-xr-xlegacy/eet/doc/img/head_bg.pngbin214 -> 0 bytes
-rw-r--r--legacy/eet/doc/img/hilite.pngbin6127 -> 0 bytes
-rwxr-xr-xlegacy/eet/doc/img/menu_bg.pngbin192 -> 0 bytes
-rwxr-xr-xlegacy/eet/doc/img/menu_bg_current.pngbin1200 -> 0 bytes
-rwxr-xr-xlegacy/eet/doc/img/menu_bg_hover.pngbin3278 -> 0 bytes
-rwxr-xr-xlegacy/eet/doc/img/menu_bg_last.pngbin637 -> 0 bytes
-rwxr-xr-xlegacy/eet/doc/img/menu_bg_unsel.pngbin1596 -> 0 bytes
-rw-r--r--legacy/eet/m4/ac_attribute.m447
-rw-r--r--legacy/eet/m4/ac_path_generic.m4137
-rw-r--r--legacy/eet/m4/efl_check_funcs.m4435
-rw-r--r--legacy/eet/m4/efl_compiler_flag.m457
-rw-r--r--legacy/eet/m4/efl_doxygen.m494
-rw-r--r--legacy/eet/m4/efl_path_max.m436
-rw-r--r--legacy/eet/m4/efl_tests.m465
-rw-r--r--legacy/eet/src/Makefile.am3
-rw-r--r--legacy/eet/src/bin/Makefile.am18
-rw-r--r--legacy/eet/src/examples/Makefile.am50
-rw-r--r--legacy/eet/src/lib/Makefile.am42
-rw-r--r--legacy/eet/src/tests/Makefile.am18
36 files changed, 0 insertions, 5336 deletions
diff --git a/legacy/eet/.gitignore b/legacy/eet/.gitignore
deleted file mode 100644
index 56157255ce..0000000000
--- a/legacy/eet/.gitignore
+++ /dev/null
@@ -1,45 +0,0 @@
1*~
2*.o
3*.lo
4*.la
5.libs
6.deps
7*.pc
8Makefile
9Makefile.in
10*.so
11.*.sw[po]
12/README
13/aclocal.m4
14/autom4te.cache/
15/config.cache
16/config.guess
17/config.h
18/config.h.in
19/config.log
20/config.status
21/config.sub
22/configure
23/depcomp
24/doc/evas.dox
25/evas.spec
26/install-sh
27/libtool
28/ltmain.sh
29/missing
30/stamp-h1
31tags
32cscope.out
33/config.cache
34/ABOUT-NLS
35/compile
36/config.cache-env
37doc/Doxyfile
38doc/eet.dox
39/eet.spec
40m4/libtool.m4
41m4/ltoptions.m4
42m4/ltsugar.m4
43m4/ltversion.m4
44m4/lt~obsolete.m4
45src/bin/eet
diff --git a/legacy/eet/AUTHORS b/legacy/eet/AUTHORS
deleted file mode 100644
index 9e2d1aab73..0000000000
--- a/legacy/eet/AUTHORS
+++ /dev/null
@@ -1,16 +0,0 @@
1The Rasterman (Carsten Haitzler) <raster@rasterman.com>
2David Goodlad <dgoodlad@gmail.com>
3Cedric Bail <cedric.bail@free.fr>
4Arnaud de Turckheim <quarium@gmail.com>
5Luis Felipe Strano Moraes <lfelipe@profusion.mobi>
6Chidambar Zinnoury <illogict@online.fr>
7Vincent Torri <vtorri@univ-evry.fr>
8Gustavo Sverzut Barbieri <barbieri@profusion.mobi>
9Raphael Kubo da Costa <kubo@profusion.mobi>
10Mathieu Taillefumier <mathieu.taillefumier@free.fr>
11Albin "Lutin" Tonnerre <albin.tonnerre@gmail.com>
12Adam Simpkins <adam@adamsimpkins.net>
13Mike Blumenkrantz <michael.blumenkrantz@gmail.com>
14Lionel Orry <lionel.orry@gmail.com>
15Jérôme Pinot <ngc891@gmail.com>
16Leandro Santiago <leandrosansilva@gmail.com>
diff --git a/legacy/eet/INSTALL b/legacy/eet/INSTALL
deleted file mode 100644
index 23e5f25d0e..0000000000
--- a/legacy/eet/INSTALL
+++ /dev/null
@@ -1,236 +0,0 @@
1Installation Instructions
2*************************
3
4Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
5Software Foundation, Inc.
6
7This file is free documentation; the Free Software Foundation gives
8unlimited permission to copy, distribute and modify it.
9
10Basic Installation
11==================
12
13These are generic installation instructions.
14
15 The `configure' shell script attempts to guess correct values for
16various system-dependent variables used during compilation. It uses
17those values to create a `Makefile' in each directory of the package.
18It may also create one or more `.h' files containing system-dependent
19definitions. Finally, it creates a shell script `config.status' that
20you can run in the future to recreate the current configuration, and a
21file `config.log' containing compiler output (useful mainly for
22debugging `configure').
23
24 It can also use an optional file (typically called `config.cache'
25and enabled with `--cache-file=config.cache' or simply `-C') that saves
26the results of its tests to speed up reconfiguring. (Caching is
27disabled by default to prevent problems with accidental use of stale
28cache files.)
29
30 If you need to do unusual things to compile the package, please try
31to figure out how `configure' could check whether to do them, and mail
32diffs or instructions to the address given in the `README' so they can
33be considered for the next release. If you are using the cache, and at
34some point `config.cache' contains results you don't want to keep, you
35may remove or edit it.
36
37 The file `configure.ac' (or `configure.in') is used to create
38`configure' by a program called `autoconf'. You only need
39`configure.ac' if you want to change it or regenerate `configure' using
40a newer version of `autoconf'.
41
42The simplest way to compile this package is:
43
44 1. `cd' to the directory containing the package's source code and type
45 `./configure' to configure the package for your system. If you're
46 using `csh' on an old version of System V, you might need to type
47 `sh ./configure' instead to prevent `csh' from trying to execute
48 `configure' itself.
49
50 Running `configure' takes awhile. While running, it prints some
51 messages telling which features it is checking for.
52
53 2. Type `make' to compile the package.
54
55 3. Optionally, type `make check' to run any self-tests that come with
56 the package.
57
58 4. Type `make install' to install the programs and any data files and
59 documentation.
60
61 5. You can remove the program binaries and object files from the
62 source code directory by typing `make clean'. To also remove the
63 files that `configure' created (so you can compile the package for
64 a different kind of computer), type `make distclean'. There is
65 also a `make maintainer-clean' target, but that is intended mainly
66 for the package's developers. If you use it, you may have to get
67 all sorts of other programs in order to regenerate files that came
68 with the distribution.
69
70Compilers and Options
71=====================
72
73Some systems require unusual options for compilation or linking that the
74`configure' script does not know about. Run `./configure --help' for
75details on some of the pertinent environment variables.
76
77 You can give `configure' initial values for configuration parameters
78by setting variables in the command line or in the environment. Here
79is an example:
80
81 ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
82
83 *Note Defining Variables::, for more details.
84
85Compiling For Multiple Architectures
86====================================
87
88You can compile the package for more than one kind of computer at the
89same time, by placing the object files for each architecture in their
90own directory. To do this, you must use a version of `make' that
91supports the `VPATH' variable, such as GNU `make'. `cd' to the
92directory where you want the object files and executables to go and run
93the `configure' script. `configure' automatically checks for the
94source code in the directory that `configure' is in and in `..'.
95
96 If you have to use a `make' that does not support the `VPATH'
97variable, you have to compile the package for one architecture at a
98time in the source code directory. After you have installed the
99package for one architecture, use `make distclean' before reconfiguring
100for another architecture.
101
102Installation Names
103==================
104
105By default, `make install' installs the package's commands under
106`/usr/local/bin', include files under `/usr/local/include', etc. You
107can specify an installation prefix other than `/usr/local' by giving
108`configure' the option `--prefix=PREFIX'.
109
110 You can specify separate installation prefixes for
111architecture-specific files and architecture-independent files. If you
112pass the option `--exec-prefix=PREFIX' to `configure', the package uses
113PREFIX as the prefix for installing programs and libraries.
114Documentation and other data files still use the regular prefix.
115
116 In addition, if you use an unusual directory layout you can give
117options like `--bindir=DIR' to specify different values for particular
118kinds of files. Run `configure --help' for a list of the directories
119you can set and what kinds of files go in them.
120
121 If the package supports it, you can cause programs to be installed
122with an extra prefix or suffix on their names by giving `configure' the
123option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
124
125Optional Features
126=================
127
128Some packages pay attention to `--enable-FEATURE' options to
129`configure', where FEATURE indicates an optional part of the package.
130They may also pay attention to `--with-PACKAGE' options, where PACKAGE
131is something like `gnu-as' or `x' (for the X Window System). The
132`README' should mention any `--enable-' and `--with-' options that the
133package recognizes.
134
135 For packages that use the X Window System, `configure' can usually
136find the X include and library files automatically, but if it doesn't,
137you can use the `configure' options `--x-includes=DIR' and
138`--x-libraries=DIR' to specify their locations.
139
140Specifying the System Type
141==========================
142
143There may be some features `configure' cannot figure out automatically,
144but needs to determine by the type of machine the package will run on.
145Usually, assuming the package is built to be run on the _same_
146architectures, `configure' can figure that out, but if it prints a
147message saying it cannot guess the machine type, give it the
148`--build=TYPE' option. TYPE can either be a short name for the system
149type, such as `sun4', or a canonical name which has the form:
150
151 CPU-COMPANY-SYSTEM
152
153where SYSTEM can have one of these forms:
154
155 OS KERNEL-OS
156
157 See the file `config.sub' for the possible values of each field. If
158`config.sub' isn't included in this package, then this package doesn't
159need to know the machine type.
160
161 If you are _building_ compiler tools for cross-compiling, you should
162use the option `--target=TYPE' to select the type of system they will
163produce code for.
164
165 If you want to _use_ a cross compiler, that generates code for a
166platform different from the build platform, you should specify the
167"host" platform (i.e., that on which the generated programs will
168eventually be run) with `--host=TYPE'.
169
170Sharing Defaults
171================
172
173If you want to set default values for `configure' scripts to share, you
174can create a site shell script called `config.site' that gives default
175values for variables like `CC', `cache_file', and `prefix'.
176`configure' looks for `PREFIX/share/config.site' if it exists, then
177`PREFIX/etc/config.site' if it exists. Or, you can set the
178`CONFIG_SITE' environment variable to the location of the site script.
179A warning: not all `configure' scripts look for a site script.
180
181Defining Variables
182==================
183
184Variables not defined in a site shell script can be set in the
185environment passed to `configure'. However, some packages may run
186configure again during the build, and the customized values of these
187variables may be lost. In order to avoid this problem, you should set
188them in the `configure' command line, using `VAR=value'. For example:
189
190 ./configure CC=/usr/local2/bin/gcc
191
192causes the specified `gcc' to be used as the C compiler (unless it is
193overridden in the site shell script). Here is a another example:
194
195 /bin/bash ./configure CONFIG_SHELL=/bin/bash
196
197Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
198configuration-related scripts to be executed by `/bin/bash'.
199
200`configure' Invocation
201======================
202
203`configure' recognizes the following options to control how it operates.
204
205`--help'
206`-h'
207 Print a summary of the options to `configure', and exit.
208
209`--version'
210`-V'
211 Print the version of Autoconf used to generate the `configure'
212 script, and exit.
213
214`--cache-file=FILE'
215 Enable the cache: use and save the results of the tests in FILE,
216 traditionally `config.cache'. FILE defaults to `/dev/null' to
217 disable caching.
218
219`--config-cache'
220`-C'
221 Alias for `--cache-file=config.cache'.
222
223`--quiet'
224`--silent'
225`-q'
226 Do not print messages saying which checks are being made. To
227 suppress all normal output, redirect it to `/dev/null' (any error
228 messages will still be shown).
229
230`--srcdir=DIR'
231 Look for the package's source code in directory DIR. Usually
232 `configure' can determine that directory automatically.
233
234`configure' also accepts some other, not widely useful, options. Run
235`configure --help' for more details.
236
diff --git a/legacy/eet/Makefile.am b/legacy/eet/Makefile.am
deleted file mode 100644
index 79b2a28176..0000000000
--- a/legacy/eet/Makefile.am
+++ /dev/null
@@ -1,89 +0,0 @@
1ACLOCAL_AMFLAGS = -I m4
2
3SUBDIRS = src doc
4
5MAINTAINERCLEANFILES = \
6Makefile.in \
7aclocal.m4 \
8compile \
9config.guess \
10config.h.in \
11config.h.in~ \
12config.sub \
13configure \
14depcomp \
15install-sh \
16ltmain.sh \
17missing \
18$(PACKAGE_TARNAME)-$(PACKAGE_VERSION).tar.gz \
19$(PACKAGE_TARNAME)-$(PACKAGE_VERSION).tar.bz2 \
20$(PACKAGE_TARNAME)-$(PACKAGE_VERSION)-doc.tar.bz2 \
21m4/libtool.m4 \
22m4/lt~obsolete.m4 \
23m4/ltoptions.m4 \
24m4/ltsugar.m4 \
25m4/ltversion.m4
26
27EXTRA_DIST = \
28AUTHORS \
29COPYING \
30autogen.sh \
31eet.pc.in \
32eet.spec.in \
33eet.spec \
34m4/ac_attribute.m4 \
35m4/ac_path_generic.m4 \
36m4/efl_binary.m4 \
37m4/efl_check_funcs.m4 \
38m4/efl_check_libs.m4 \
39m4/efl_doxygen.m4 \
40m4/efl_tests.m4 \
41m4/efl_path_max.m4
42
43pkgconfigdir = $(libdir)/pkgconfig
44pkgconfig_DATA = eet.pc
45
46.PHONY: doc
47
48# Documentation
49
50doc:
51 @echo "entering doc/"
52 $(MAKE) -C doc doc
53
54# Unit tests
55
56if EFL_ENABLE_TESTS
57
58lcov-reset:
59 @rm -rf $(top_builddir)/coverage
60 @find $(top_builddir) -name "*.gcda" -delete
61 @lcov --zerocounters --directory $(top_builddir)
62
63lcov-report:
64 @mkdir $(top_builddir)/coverage
65 lcov --capture --compat-libtool --output-file $(top_builddir)/coverage/coverage.info --directory $(top_builddir)
66 lcov --remove $(top_builddir)/coverage/coverage.info '*.h' --output-file $(top_builddir)/coverage/coverage.cleaned.info
67 genhtml -t "$(PACKAGE_STRING)" -o $(top_builddir)/coverage/html $(top_builddir)/coverage/coverage.cleaned.info
68 @echo "Coverage Report at $(top_builddir)/coverage/html"
69
70check-local:
71 @$(MAKE) lcov-reset
72 @./src/tests/eet_suite
73 @$(MAKE) lcov-report
74
75else
76
77lcov-reset:
78 @echo "reconfigure with --enable-tests"
79
80lcov-report:
81 @echo "reconfigure with --enable-tests"
82
83check-local:
84 @echo "reconfigure with --enable-tests"
85
86endif
87
88clean-local:
89 @rm -rf coverage
diff --git a/legacy/eet/autogen.sh b/legacy/eet/autogen.sh
deleted file mode 100755
index 72e10332c4..0000000000
--- a/legacy/eet/autogen.sh
+++ /dev/null
@@ -1,38 +0,0 @@
1#!/bin/sh
2
3rm -rf autom4te.cache
4rm -f aclocal.m4 ltmain.sh
5
6touch ABOUT-NLS
7
8echo "Running aclocal..." ; aclocal $ACLOCAL_FLAGS -I m4 || exit 1
9echo "Running autoheader..." ; autoheader || exit 1
10echo "Running autoconf..." ; autoconf || exit 1
11echo "Running libtoolize..." ; (libtoolize --copy --automake || glibtoolize --automake) || exit 1
12echo "Running automake..." ; automake --add-missing --copy --gnu || exit 1
13
14W=0
15
16rm -f config.cache-env.tmp
17echo "OLD_PARM=\"$@\"" >> config.cache-env.tmp
18echo "OLD_CFLAGS=\"$CFLAGS\"" >> config.cache-env.tmp
19echo "OLD_PATH=\"$PATH\"" >> config.cache-env.tmp
20echo "OLD_PKG_CONFIG_PATH=\"$PKG_CONFIG_PATH\"" >> config.cache-env.tmp
21echo "OLD_LDFLAGS=\"$LDFLAGS\"" >> config.cache-env.tmp
22
23cmp config.cache-env.tmp config.cache-env >> /dev/null
24if [ $? -ne 0 ]; then
25 W=1;
26fi
27
28if [ $W -ne 0 ]; then
29 echo "Cleaning configure cache...";
30 rm -f config.cache config.cache-env
31 mv config.cache-env.tmp config.cache-env
32else
33 rm -f config.cache-env.tmp
34fi
35
36if [ -z "$NOCONFIGURE" ]; then
37 ./configure -C "$@"
38fi
diff --git a/legacy/eet/configure.ac b/legacy/eet/configure.ac
deleted file mode 100644
index 444b8401a1..0000000000
--- a/legacy/eet/configure.ac
+++ /dev/null
@@ -1,541 +0,0 @@
1##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
2##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
3m4_define([v_maj], [1])
4m4_define([v_min], [7])
5m4_define([v_mic], [99])
6m4_define([v_rev], m4_esyscmd([(svnversion "${SVN_REPO_PATH:-.}" | grep -v '\(export\|Unversioned directory\)' || echo 0) | awk -F : '{printf("%s\n", $1);}' | tr -d ' :MSP\n']))
7m4_if(v_rev, [0], [m4_define([v_rev], m4_esyscmd([git log 2> /dev/null | (grep -m1 git-svn-id || echo 0) | sed -e 's/.*@\([0-9]*\).*/\1/' | tr -d '\n']))])
8##-- When released, remove the dnl on the below line
9dnl m4_undefine([v_rev])
10##-- When doing snapshots - change soname. remove dnl on below line
11dnl m4_define([relname], [ver-pre-svn-05])
12dnl m4_define([v_rel], [-release relname])
13##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
14m4_ifdef([v_rev], [m4_define([v_ver], [v_maj.v_min.v_mic.v_rev])], [m4_define([v_ver], [v_maj.v_min.v_mic])])
15m4_define([lt_cur], m4_eval(v_maj + v_min))
16m4_define([lt_rev], v_mic)
17m4_define([lt_age], v_min)
18##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
19##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
20
21AC_INIT([eet], [v_ver], [enlightenment-devel@lists.sourceforge.net])
22AC_PREREQ([2.52])
23AC_CONFIG_SRCDIR([configure.ac])
24AC_CONFIG_MACRO_DIR([m4])
25
26AC_CONFIG_HEADERS([config.h])
27AH_TOP([
28#ifndef EFL_CONFIG_H__
29#define EFL_CONFIG_H__
30])
31AH_BOTTOM([
32#endif /* EFL_CONFIG_H__ */
33])
34
35AM_INIT_AUTOMAKE([1.6 dist-bzip2])
36m4_ifdef([AM_SILENT_RULES], [AM_SILENT_RULES([yes])])
37
38AC_GNU_SOURCE
39
40AC_LIBTOOL_WIN32_DLL
41define([AC_LIBTOOL_LANG_CXX_CONFIG], [:])dnl
42define([AC_LIBTOOL_LANG_F77_CONFIG], [:])dnl
43AC_PROG_LIBTOOL
44
45##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
46##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
47m4_ifdef([v_rev], , [m4_define([v_rev], [0])])
48m4_ifdef([v_rel], , [m4_define([v_rel], [])])
49AC_DEFINE_UNQUOTED(VMAJ, [v_maj], [Major version])
50AC_DEFINE_UNQUOTED(VMIN, [v_min], [Minor version])
51AC_DEFINE_UNQUOTED(VMIC, [v_mic], [Micro version])
52AC_DEFINE_UNQUOTED(VREV, [v_rev], [Revison])
53version_info="lt_cur:lt_rev:lt_age"
54release_info="v_rel"
55AC_SUBST(version_info)
56AC_SUBST(release_info)
57##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
58##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
59VMAJ=v_maj
60AC_SUBST(VMAJ)
61
62
63### Needed information
64
65AC_CANONICAL_BUILD
66AC_CANONICAL_HOST
67
68### Default options with respect to host
69
70requirements_pc_eet=""
71requirements_libs_eet=""
72
73### Additional options to configure
74
75EFL_ENABLE_BIN([eet])
76
77# Old eet file format support
78
79AC_ARG_ENABLE(old-eet-file-format,
80 [AC_HELP_STRING(
81 [--disable-old-eet-file-format],
82 [disable old eet file format support @<:@default=enabled@:>@])],
83 [
84 if test "x${enableval}" = "xyes" ; then
85 old_eet_file_format="yes"
86 else
87 old_eet_file_format="no"
88 fi
89 ],
90 [old_eet_file_format="yes"])
91
92AC_MSG_CHECKING([whether to support old eet file format])
93AC_MSG_RESULT([${old_eet_file_format}])
94
95if test "x${old_eet_file_format}" = "xyes" ; then
96 AC_DEFINE(EET_OLD_EET_FILE_FORMAT, 1, [support old eet file format])
97else
98 AC_DEFINE(EET_OLD_EET_FILE_FORMAT, 0, [support old eet file format])
99fi
100
101# Openssl support
102
103AC_ARG_ENABLE([openssl],
104 [AC_HELP_STRING([--disable-openssl], [disable openssl eet support @<:@default=auto@:>@])],
105 [
106 if test "x${enableval}" = "xyes" ; then
107 want_openssl="yes"
108 else
109 want_openssl="no"
110 fi
111 ],
112 [want_openssl="auto"])
113
114AC_MSG_CHECKING([whether to use OpenSSL])
115AC_MSG_RESULT([${want_openssl}])
116
117# Cryptography support
118
119AC_ARG_ENABLE([cipher],
120 [AC_HELP_STRING([--disable-cipher], [disable cipher support for eet API @<:@default=yes@:>@])],
121 [
122 if test "x${enableval}" = "xyes" ; then
123 want_cipher="yes"
124 else
125 want_cipher="no"
126 fi
127 ],
128 [want_cipher="yes"])
129
130AC_MSG_CHECKING([whether to use cipher])
131AC_MSG_RESULT([${want_cipher}])
132
133AC_ARG_ENABLE([signature],
134 [AC_HELP_STRING([--disable-signature], [disable signature file support for eet @<:@default=yes@:>@])],
135 [
136 if test "x${enableval}" = "xyes" ; then
137 want_signature="yes"
138 else
139 want_signature="no"
140 fi
141 ],
142 [want_signature="yes"])
143
144AC_MSG_CHECKING([whether to use signature])
145AC_MSG_RESULT([${want_signature}])
146
147# Assert or fail.
148
149AC_ARG_ENABLE([assert],
150 [AC_HELP_STRING([--enable-assert], [enable assert, @<:@default=no@:>@])],
151 [
152 if test "x${enableval}" = "xyes" ; then
153 prefer_assert="yes"
154 else
155 prefer_assert="no"
156 fi
157 ],
158 [prefer_assert="no"])
159
160# Examples
161
162AC_ARG_ENABLE([install-examples],
163 [AC_HELP_STRING([--disable-install-examples],
164 [disable installing examples (compiled or just source). @<:@default=yes@:>@])],
165 [
166 if test "x${enableval}" = "xyes" ; then
167 install_examples="yes"
168 else
169 install_examples="no"
170 fi
171 ],
172 [install_examples="yes"])
173
174AM_CONDITIONAL([INSTALL_EXAMPLES], [test "x${install_examples}" = "xyes"])
175
176AC_ARG_ENABLE([build-examples],
177 [AC_HELP_STRING([--enable-build-examples],
178 [enable building examples @<:@default=yes@:>@])],
179 [
180 if test "x${enableval}" = "xyes" ; then
181 build_examples="yes"
182 else
183 build_examples="no"
184 fi
185 ],
186 [build_examples="no"])
187AM_CONDITIONAL([BUILD_EXAMPLES], [test "x${build_examples}" = "xyes"])
188
189
190### Checks for programs
191AC_PROG_CC
192
193# pkg-config
194PKG_PROG_PKG_CONFIG
195
196# Check whether pkg-config supports Requires.private
197if $PKG_CONFIG --atleast-pkgconfig-version 0.22; then
198 pkgconfig_requires_private="Requires.private"
199else
200 pkgconfig_requires_private="Requires"
201fi
202AC_SUBST(pkgconfig_requires_private)
203
204
205# doxygen program for documentation building
206
207EFL_CHECK_DOXYGEN([build_doc="yes"], [build_doc="no"])
208
209### Checks for libraries
210
211## Compatibility layers
212
213# Evil library for compilation on Windows
214
215EFL_EET_BUILD=""
216case "$host_os" in
217 mingw*)
218 PKG_CHECK_EXISTS([evil >= 1.1.0])
219 AC_DEFINE([HAVE_EVIL], [1], [Set to 1 if Evil package is installed])
220 requirements_pc_eet="evil ${requirements_pc_eet}"
221 EFL_EET_BUILD="-DEFL_EET_BUILD"
222 ;;
223esac
224AC_SUBST(EFL_EET_BUILD)
225
226# Exotic library for copilation on Coyote
227
228PKG_CHECK_EXISTS([exotic],
229 [
230 enable_exotic="yes"
231 AC_DEFINE([HAVE_EXOTIC_H], [1], [Define to 1 if you have Exotic.])
232 requirements_pc_eet="exotic ${requirements_pc_eet}"
233 ],
234 [enable_exotic="no"])
235
236## Secure layer
237
238# Gnutls library
239
240AC_ARG_ENABLE([gnutls],
241 [AC_HELP_STRING([--disable-gnutls], [disable gnutls eet support @<:@default=auto@:>@])],
242 [
243 if test "x${enableval}" = "xyes" ; then
244 want_gnutls="yes"
245 else
246 want_gnutls="no"
247 fi
248 ],
249 [want_gnutls="auto"])
250
251AC_MSG_CHECKING([whether to use Gnutls])
252AC_MSG_RESULT([${want_gnutls}])
253
254have_gnutls="no"
255if test "x${want_gnutls}" = "xyes" || test "x${want_gnutls}" = "xauto" ; then
256 PKG_CHECK_MODULES([GNUTLS], [gnutls >= 1.7.6],
257 [
258 have_gnutls="yes"
259 want_openssl="no"
260 AC_DEFINE([HAVE_GNUTLS], [1], [Have Gnutls support])
261 requirements_pc_eet="gnutls >= 1.7.6 ${requirements_pc_eet}"
262 ],
263 [have_gnutls="no"])
264fi
265
266# libgcrypt
267
268if test "x${have_gnutls}" = "xyes" ; then
269 AC_PATH_GENERIC([libgcrypt], [], [have_gnutls="yes"], [have_gnutls="no"])
270 if test "x${have_gnutls}" = "xyes" ; then
271 requirements_libs_eet="${LIBGCRYPT_LIBS} ${requirements_libs_eet}"
272 fi
273fi
274
275# Specific GNUTLS improvement
276
277AC_ARG_ENABLE(new-gnutls-api,
278 [AC_HELP_STRING(
279 [--disable-new-gnutls-api],
280 [enable use of gnutls_x509_crt_verify_hash. @<:@default=yes@:>@])],
281 [
282 if test "x${enableval}" = "xyes" ; then
283 new_gnutls_api="yes"
284 else
285 new_gnutls_api="no"
286 fi
287 ],
288 [new_gnutls_api="yes"])
289
290AC_MSG_CHECKING([whether to use gnutls_x509_crt_verify_hash])
291AC_MSG_RESULT([${new_gnutls_api}])
292
293if test "x${have_gnutls}" = "xyes" && test "x${new_gnutls_api}" = "xyes" ; then
294 CFLAGS_save="${CFLAGS}"
295 LIBS_save="${LIBS}"
296 CFLAGS="${GNUTLS_CFLAGS}"
297 LIBS="${GNUTLS_LIBS}"
298 AC_CHECK_LIB([gnutls], [gnutls_x509_crt_verify_hash],
299 [
300 AC_DEFINE([EET_USE_NEW_GNUTLS_API], [1], [use gnutls_x509_crt_verify_hash])
301 new_gnutls_api="yes"
302 ],
303 [new_gnutls_api="no"])
304 CFLAGS="${CFLAGS_save}"
305 LIBS="${LIBS_save}"
306fi
307
308use_gnutls_privkey_sign_data="no"
309if test "x${have_gnutls}" = "xyes" ; then
310 CFLAGS_save="${CFLAGS}"
311 LIBS_save="${LIBS}"
312 CFLAGS="${GNUTLS_CFLAGS}"
313 LIBS="${GNUTLS_LIBS}"
314 AC_CHECK_LIB([gnutls], [gnutls_privkey_sign_data],
315 [
316 AC_DEFINE([EET_USE_NEW_PRIVKEY_SIGN_DATA], [1], [use gnutls_privkey_sign_data])
317 use_gnutls_privkey_sign_data="yes"
318 ],
319 [use_gnutls_privkey_sign_data="no"])
320 CFLAGS="${CFLAGS_save}"
321 LIBS="${LIBS_save}"
322fi
323
324AC_MSG_CHECKING([whether to use gnutls_privkey_sign_data])
325AC_MSG_RESULT([${use_gnutls_privkey_sign_data}])
326
327use_gnutls_pubkey_verify_hash="no"
328if test "x${have_gnutls}" = "xyes" ; then
329 CFLAGS_save="${CFLAGS}"
330 LIBS_save="${LIBS}"
331 CFLAGS="${GNUTLS_CFLAGS}"
332 LIBS="${GNUTLS_LIBS}"
333 AC_CHECK_LIB([gnutls], [gnutls_pubkey_verify_hash],
334 [
335 AC_DEFINE([EET_USE_NEW_PUBKEY_VERIFY_HASH], [1], [use gnutls_pubkey_verify_hash])
336 use_gnutls_pubkey_verify_hash="yes"
337 ],
338 [use_gnutls_pubkey_verify_hash="no"])
339 CFLAGS="${CFLAGS_save}"
340 LIBS="${LIBS_save}"
341fi
342
343AC_MSG_CHECKING([whether to use gnutls_pubkey_verify_hash])
344AC_MSG_RESULT([${use_gnutls_pubkey_verify_hash}])
345
346# Openssl library
347have_openssl="no"
348if test "x${want_openssl}" = "xyes" || test "x${want_openssl}" = "xauto" ; then
349 PKG_CHECK_EXISTS([openssl],
350 [
351 have_openssl="yes"
352 AC_DEFINE([HAVE_OPENSSL], [1], [Have Openssl support])
353 requirements_pc_eet="openssl ${requirements_pc_eet}"
354 ],
355 [have_openssl="no"])
356fi
357
358if test "x${have_gnutls}" = "xyes" ; then
359 secure_layer="GnuTLS"
360elif test "x${have_openssl}" = "xyes" ; then
361 secure_layer="OpenSSL"
362else
363 secure_layer="no"
364fi
365
366have_cipher="no"
367if test "x${have_gnutls}" = "xyes" && test "x${want_cipher}" = "xyes" ; then
368 have_cipher="yes"
369 AC_DEFINE([HAVE_CIPHER], [1], [Have cipher support built in eet])
370elif test "x${have_openssl}" = "xyes" && test "x${want_cipher}" = "xyes" ; then
371 have_cipher="yes"
372 AC_DEFINE([HAVE_CIPHER], [1], [Have cipher support built in eet])
373fi
374
375AC_MSG_CHECKING([whether to activate cipher support in eet])
376AC_MSG_RESULT([${have_cipher}])
377
378have_signature="no"
379if test "x${have_gnutls}" = "xyes" && test "x${want_signature}" = "xyes" ; then
380 have_signature="yes"
381 AC_DEFINE([HAVE_SIGNATURE], [1], [Have signature support for eet file])
382elif test "x${have_openssl}" = "xyes" && test "x${want_signature}" = "xyes" ; then
383 have_signature="yes"
384 AC_DEFINE([HAVE_SIGNATURE], [1], [Have signature support for eet file])
385fi
386
387AC_MSG_CHECKING([whether to activate signature support in eet])
388AC_MSG_RESULT([${have_signature}])
389
390# libjpeg and zlib
391EFL_CHECK_LIBS([eet], [libjpeg zlib])
392
393# Eina library
394
395requirements_pc_eet="eina >= 1.2.0 ${requirements_pc_eet}"
396PKG_CHECK_MODULES([EET], [${requirements_pc_eet}])
397
398case "$host_os" in
399 mingw32ce*)
400 requirements_libs_eet="${requirements_libs_eet} -lws2"
401 ;;
402 mingw*)
403 requirements_libs_eet="${requirements_libs_eet} -lws2_32"
404 ;;
405esac
406
407EET_LIBS="${EET_LIBS} ${requirements_libs_eet}"
408
409
410### Checks for header files
411
412AC_CHECK_HEADERS(netinet/in.h unistd.h)
413EFL_CHECK_PATH_MAX
414
415### Checks for types
416
417
418### Checks for structures
419
420
421### Checks for compiler characteristics
422AM_PROG_CC_C_O
423AC_C_INLINE
424AC_PROG_CC_STDC
425AC_C___ATTRIBUTE__
426
427# Check whether the null pointer is zero on this arch
428AC_TRY_RUN(
429 [
430#include <stdlib.h>
431#include <inttypes.h>
432int main (int argc, char **argv) {
433 void *foo = NULL;
434 uintptr_t bar = (uintptr_t)foo;
435 return (uintptr_t)foo;
436}
437 ],
438 [have_null="yes"],
439 [have_null="no"],
440 [
441 AC_MSG_WARN([Cannot check when cross-compiling -- assuming null is okay])
442 have_null="yes"
443 ])
444AC_MSG_CHECKING([value of the null pointer])
445AC_MSG_RESULT([${have_null}])
446
447if test ! "x${have_null}" = "xyes" ; then
448 AC_MSG_WARN([Your system is a bit too funny, eet might not work properly])
449fi
450
451
452### Checks for linker characteristics
453
454# use --enable-auto-import on Windows
455
456lt_enable_auto_import=""
457case "$host_os" in
458 mingw*)
459 lt_enable_auto_import="-Wl,--enable-auto-import"
460 ;;
461esac
462AC_SUBST([lt_enable_auto_import])
463
464case "${host_os}" in
465 openbsd*)
466 ;;
467 *)
468 EFL_LINKER_FLAG([-Wl,--as-needed])
469 ;;
470esac
471
472
473### Checks for library functions
474AC_ISC_POSIX
475AC_FUNC_ALLOCA
476
477EFL_CHECK_FUNCS([eet], [fnmatch])
478
479
480### Unit tests, coverage and benchmarking
481
482EFL_CHECK_TESTS([eet], [enable_tests="yes"], [enable_tests="no"])
483
484
485AC_SUBST([requirements_pc_eet])
486AC_SUBST([requirements_libs_eet])
487
488AC_OUTPUT([
489Makefile
490eet.pc
491doc/Makefile
492doc/Doxyfile
493doc/eet.dox
494src/Makefile
495src/lib/Makefile
496src/bin/Makefile
497src/tests/Makefile
498src/examples/Makefile
499eet.spec
500])
501
502
503#####################################################################
504## Info
505
506echo
507echo
508echo
509echo "------------------------------------------------------------------------"
510echo "$PACKAGE_NAME $PACKAGE_VERSION"
511echo "------------------------------------------------------------------------"
512echo
513echo "Configuration Options Summary:"
514echo
515echo " Secure layer.........: ${secure_layer}"
516if test "x${have_gnutls}" = "xyes" || test "x${have_openssl}" = "xyes" ; then
517 echo " Cipher support.....: ${have_cipher}"
518 echo " Signature..........: ${have_signature}"
519fi
520echo
521echo " Old eet file format..: ${old_eet_file_format}"
522echo
523echo " Tests................: ${enable_tests} (Coverage: ${efl_enable_coverage})"
524echo
525echo " Build eet............: $have_eet"
526echo
527echo " Documentation........: ${build_doc}"
528if test "x${build_doc}" = "xyes" ; then
529 echo " Building...........: make doc"
530fi
531echo " Examples.............: ${build_examples}"
532echo " Examples installed...: ${install_examples}"
533echo
534echo "Compilation............: make (or gmake)"
535echo " CPPFLAGS.............: $CPPFLAGS"
536echo " CFLAGS...............: $CFLAGS"
537echo " LDFLAGS..............: $LDFLAGS"
538echo
539echo "Installation...........: make install (as root if needed, with 'su' or 'sudo')"
540echo " prefix...............: $prefix"
541echo
diff --git a/legacy/eet/doc/Doxyfile.in b/legacy/eet/doc/Doxyfile.in
deleted file mode 100644
index 126b6567a4..0000000000
--- a/legacy/eet/doc/Doxyfile.in
+++ /dev/null
@@ -1,1677 +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# Set the SHOW_FILES tag to NO to disable the generation of the Files page.
504# This will remove the Files entry from the Quick Index and from the
505# Folder Tree View (if specified). The default is YES.
506
507SHOW_FILES = YES
508
509# Set the SHOW_NAMESPACES tag to NO to disable the generation of the
510# Namespaces page.
511# This will remove the Namespaces entry from the Quick Index
512# and from the Folder Tree View (if specified). The default is YES.
513
514SHOW_NAMESPACES = YES
515
516# The FILE_VERSION_FILTER tag can be used to specify a program or script that
517# doxygen should invoke to get the current version for each file (typically from
518# the version control system). Doxygen will invoke the program by executing (via
519# popen()) the command <command> <input-file>, where <command> is the value of
520# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
521# provided by doxygen. Whatever the program writes to standard output
522# is used as the file version. See the manual for examples.
523
524FILE_VERSION_FILTER =
525
526# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
527# by doxygen. The layout file controls the global structure of the generated
528# output files in an output format independent way. The create the layout file
529# that represents doxygen's defaults, run doxygen with the -l option.
530# You can optionally specify a file name after the option, if omitted
531# DoxygenLayout.xml will be used as the name of the layout file.
532
533LAYOUT_FILE =
534
535#---------------------------------------------------------------------------
536# configuration options related to warning and progress messages
537#---------------------------------------------------------------------------
538
539# The QUIET tag can be used to turn on/off the messages that are generated
540# by doxygen. Possible values are YES and NO. If left blank NO is used.
541
542QUIET = NO
543
544# The WARNINGS tag can be used to turn on/off the warning messages that are
545# generated by doxygen. Possible values are YES and NO. If left blank
546# NO is used.
547
548WARNINGS = YES
549
550# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
551# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
552# automatically be disabled.
553
554WARN_IF_UNDOCUMENTED = YES
555
556# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
557# potential errors in the documentation, such as not documenting some
558# parameters in a documented function, or documenting parameters that
559# don't exist or using markup commands wrongly.
560
561WARN_IF_DOC_ERROR = YES
562
563# The WARN_NO_PARAMDOC option can be enabled to get warnings for
564# functions that are documented, but have no documentation for their parameters
565# or return value. If set to NO (the default) doxygen will only warn about
566# wrong or incomplete parameter documentation, but not about the absence of
567# documentation.
568
569WARN_NO_PARAMDOC = YES
570
571# The WARN_FORMAT tag determines the format of the warning messages that
572# doxygen can produce. The string should contain the $file, $line, and $text
573# tags, which will be replaced by the file and line number from which the
574# warning originated and the warning text. Optionally the format may contain
575# $version, which will be replaced by the version of the file (if it could
576# be obtained via FILE_VERSION_FILTER)
577
578WARN_FORMAT = "$file:$line: $text"
579
580# The WARN_LOGFILE tag can be used to specify a file to which warning
581# and error messages should be written. If left blank the output is written
582# to stderr.
583
584WARN_LOGFILE =
585
586#---------------------------------------------------------------------------
587# configuration options related to the input files
588#---------------------------------------------------------------------------
589
590# The INPUT tag can be used to specify the files and/or directories that contain
591# documented source files. You may enter file names like "myfile.cpp" or
592# directories like "/usr/src/myproject". Separate the files or directories
593# with spaces.
594
595INPUT = @builddir@/eet.dox \
596 @srcdir@/examples.dox \
597 @top_srcdir@/src/lib
598
599# This tag can be used to specify the character encoding of the source files
600# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is
601# also the default input encoding. Doxygen uses libiconv (or the iconv built
602# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for
603# the list of possible encodings.
604
605INPUT_ENCODING = UTF-8
606
607# If the value of the INPUT tag contains directories, you can use the
608# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
609# and *.h) to filter out the source-files in the directories. If left
610# blank the following patterns are tested:
611# *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh
612# *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py
613# *.f90 *.f *.for *.vhd *.vhdl
614
615FILE_PATTERNS = *.c \
616 *.h
617
618# The RECURSIVE tag can be used to turn specify whether or not subdirectories
619# should be searched for input files as well. Possible values are YES and NO.
620# If left blank NO is used.
621
622RECURSIVE = YES
623
624# The EXCLUDE tag can be used to specify files and/or directories that should
625# excluded from the INPUT source files. This way you can easily exclude a
626# subdirectory from a directory tree whose root is specified with the INPUT tag.
627
628EXCLUDE = @top_builddir@/src/lib/eet_amalgamation.c
629
630# The EXCLUDE_SYMLINKS tag can be used select whether or not files or
631# directories that are symbolic links (a Unix file system feature) are excluded
632# from the input.
633
634EXCLUDE_SYMLINKS = NO
635
636# If the value of the INPUT tag contains directories, you can use the
637# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
638# certain files from those directories. Note that the wildcards are matched
639# against the file with absolute path, so to exclude all test directories
640# for example use the pattern */test/*
641
642EXCLUDE_PATTERNS =
643
644# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
645# (namespaces, classes, functions, etc.) that should be excluded from the
646# output. The symbol name can be a fully qualified name, a word, or if the
647# wildcard * is used, a substring. Examples: ANamespace, AClass,
648# AClass::ANamespace, ANamespace::*Test
649
650EXCLUDE_SYMBOLS =
651
652# The EXAMPLE_PATH tag can be used to specify one or more files or
653# directories that contain example code fragments that are included (see
654# the \include command).
655
656EXAMPLE_PATH = @top_srcdir@/src/examples
657
658# If the value of the EXAMPLE_PATH tag contains directories, you can use the
659# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
660# and *.h) to filter out the source-files in the directories. If left
661# blank all files are included.
662
663EXAMPLE_PATTERNS =
664
665# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
666# searched for input files to be used with the \include or \dontinclude
667# commands irrespective of the value of the RECURSIVE tag.
668# Possible values are YES and NO. If left blank NO is used.
669
670EXAMPLE_RECURSIVE = NO
671
672# The IMAGE_PATH tag can be used to specify one or more files or
673# directories that contain image that are included in the documentation (see
674# the \image command).
675
676IMAGE_PATH = @top_srcdir@/doc/img
677
678# The INPUT_FILTER tag can be used to specify a program that doxygen should
679# invoke to filter for each input file. Doxygen will invoke the filter program
680# by executing (via popen()) the command <filter> <input-file>, where <filter>
681# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
682# input file. Doxygen will then use the output that the filter program writes
683# to standard output.
684# If FILTER_PATTERNS is specified, this tag will be
685# ignored.
686
687INPUT_FILTER =
688
689# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
690# basis.
691# Doxygen will compare the file name with each pattern and apply the
692# filter if there is a match.
693# The filters are a list of the form:
694# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
695# info on how filters are used. If FILTER_PATTERNS is empty or if
696# non of the patterns match the file name, INPUT_FILTER is applied.
697
698FILTER_PATTERNS =
699
700# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
701# INPUT_FILTER) will be used to filter the input files when producing source
702# files to browse (i.e. when SOURCE_BROWSER is set to YES).
703
704FILTER_SOURCE_FILES = NO
705
706# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
707# pattern. A pattern will override the setting for FILTER_PATTERN (if any)
708# and it is also possible to disable source filtering for a specific pattern
709# using *.ext= (so without naming a filter). This option only has effect when
710# FILTER_SOURCE_FILES is enabled.
711
712FILTER_SOURCE_PATTERNS =
713
714#---------------------------------------------------------------------------
715# configuration options related to source browsing
716#---------------------------------------------------------------------------
717
718# If the SOURCE_BROWSER tag is set to YES then a list of source files will
719# be generated. Documented entities will be cross-referenced with these sources.
720# Note: To get rid of all source code in the generated output, make sure also
721# VERBATIM_HEADERS is set to NO.
722
723SOURCE_BROWSER = NO
724
725# Setting the INLINE_SOURCES tag to YES will include the body
726# of functions and classes directly in the documentation.
727
728INLINE_SOURCES = NO
729
730# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
731# doxygen to hide any special comment blocks from generated source code
732# fragments. Normal C and C++ comments will always remain visible.
733
734STRIP_CODE_COMMENTS = YES
735
736# If the REFERENCED_BY_RELATION tag is set to YES
737# then for each documented function all documented
738# functions referencing it will be listed.
739
740REFERENCED_BY_RELATION = YES
741
742# If the REFERENCES_RELATION tag is set to YES
743# then for each documented function all documented entities
744# called/used by that function will be listed.
745
746REFERENCES_RELATION = YES
747
748# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
749# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
750# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
751# link to the source code.
752# Otherwise they will link to the documentation.
753
754REFERENCES_LINK_SOURCE = YES
755
756# If the USE_HTAGS tag is set to YES then the references to source code
757# will point to the HTML generated by the htags(1) tool instead of doxygen
758# built-in source browser. The htags tool is part of GNU's global source
759# tagging system (see http://www.gnu.org/software/global/global.html). You
760# will need version 4.8.6 or higher.
761
762USE_HTAGS = NO
763
764# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
765# will generate a verbatim copy of the header file for each class for
766# which an include is specified. Set to NO to disable this.
767
768VERBATIM_HEADERS = NO
769
770#---------------------------------------------------------------------------
771# configuration options related to the alphabetical class index
772#---------------------------------------------------------------------------
773
774# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
775# of all compounds will be generated. Enable this if the project
776# contains a lot of classes, structs, unions or interfaces.
777
778ALPHABETICAL_INDEX = YES
779
780# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
781# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
782# in which this list will be split (can be a number in the range [1..20])
783
784COLS_IN_ALPHA_INDEX = 2
785
786# In case all classes in a project start with a common prefix, all
787# classes will be put under the same header in the alphabetical index.
788# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
789# should be ignored while generating the index headers.
790
791IGNORE_PREFIX = eet_ \
792 _eet_ \
793 Eet_ \
794 _Eet_ \
795 EET_ \
796 _EET_
797
798#---------------------------------------------------------------------------
799# configuration options related to the HTML output
800#---------------------------------------------------------------------------
801
802# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
803# generate HTML output.
804
805GENERATE_HTML = YES
806
807# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
808# If a relative path is entered the value of OUTPUT_DIRECTORY will be
809# put in front of it. If left blank `html' will be used as the default path.
810
811HTML_OUTPUT = html
812
813# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
814# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
815# doxygen will generate files with .html extension.
816
817HTML_FILE_EXTENSION = .html
818
819# The HTML_HEADER tag can be used to specify a personal HTML header for
820# each generated HTML page. If it is left blank doxygen will generate a
821# standard header.
822
823HTML_HEADER = @srcdir@/head.html
824
825# The HTML_FOOTER tag can be used to specify a personal HTML footer for
826# each generated HTML page. If it is left blank doxygen will generate a
827# standard footer.
828
829HTML_FOOTER = @srcdir@/foot.html
830
831# The HTML_STYLESHEET tag can be used to specify a user-defined cascading
832# style sheet that is used by each HTML page. It can be used to
833# fine-tune the look of the HTML output. If the tag is left blank doxygen
834# will generate a default style sheet. Note that doxygen will try to copy
835# the style sheet file to the HTML output directory, so don't put your own
836# stylesheet in the HTML output directory as well, or it will be erased!
837
838HTML_STYLESHEET = @srcdir@/e.css
839
840# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output.
841# Doxygen will adjust the colors in the stylesheet and background images
842# according to this color. Hue is specified as an angle on a colorwheel,
843# see http://en.wikipedia.org/wiki/Hue for more information.
844# For instance the value 0 represents red, 60 is yellow, 120 is green,
845# 180 is cyan, 240 is blue, 300 purple, and 360 is red again.
846# The allowed range is 0 to 359.
847
848HTML_COLORSTYLE_HUE = 220
849
850# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of
851# the colors in the HTML output. For a value of 0 the output will use
852# grayscales only. A value of 255 will produce the most vivid colors.
853
854HTML_COLORSTYLE_SAT = 100
855
856# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to
857# the luminance component of the colors in the HTML output. Values below
858# 100 gradually make the output lighter, whereas values above 100 make
859# the output darker. The value divided by 100 is the actual gamma applied,
860# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2,
861# and 100 does not change the gamma.
862
863HTML_COLORSTYLE_GAMMA = 80
864
865# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
866# page will contain the date and time when the page was generated. Setting
867# this to NO can help when comparing the output of multiple runs.
868
869HTML_TIMESTAMP = YES
870
871# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
872# documentation will contain sections that can be hidden and shown after the
873# page has loaded. For this to work a browser that supports
874# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox
875# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).
876
877HTML_DYNAMIC_SECTIONS = YES
878
879# If the GENERATE_DOCSET tag is set to YES, additional index files
880# will be generated that can be used as input for Apple's Xcode 3
881# integrated development environment, introduced with OSX 10.5 (Leopard).
882# To create a documentation set, doxygen will generate a Makefile in the
883# HTML output directory. Running make will produce the docset in that
884# directory and running "make install" will install the docset in
885# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
886# it at startup.
887# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
888# for more information.
889
890GENERATE_DOCSET = YES
891
892# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the
893# feed. A documentation feed provides an umbrella under which multiple
894# documentation sets from a single provider (such as a company or product suite)
895# can be grouped.
896
897DOCSET_FEEDNAME = "Doxygen generated docs"
898
899# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that
900# should uniquely identify the documentation set bundle. This should be a
901# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen
902# will append .docset to the name.
903
904DOCSET_BUNDLE_ID = org.enlightenment.Eet
905
906# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify
907# the documentation publisher. This should be a reverse domain-name style
908# string, e.g. com.mycompany.MyDocSet.documentation.
909
910DOCSET_PUBLISHER_ID = org.enlightenment.Eet
911
912# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.
913
914DOCSET_PUBLISHER_NAME = Enlightenment
915
916# If the GENERATE_HTMLHELP tag is set to YES, additional index files
917# will be generated that can be used as input for tools like the
918# Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
919# of the generated HTML documentation.
920
921GENERATE_HTMLHELP = YES
922
923# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
924# be used to specify the file name of the resulting .chm file. You
925# can add a path in front of the file if the result should not be
926# written to the html output directory.
927
928CHM_FILE =
929
930# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
931# be used to specify the location (absolute path including file name) of
932# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
933# the HTML help compiler on the generated index.hhp.
934
935HHC_LOCATION =
936
937# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
938# controls if a separate .chi index file is generated (YES) or that
939# it should be included in the master .chm file (NO).
940
941GENERATE_CHI = NO
942
943# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING
944# is used to encode HtmlHelp index (hhk), content (hhc) and project file
945# content.
946
947CHM_INDEX_ENCODING =
948
949# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
950# controls whether a binary table of contents is generated (YES) or a
951# normal table of contents (NO) in the .chm file.
952
953BINARY_TOC = NO
954
955# The TOC_EXPAND flag can be set to YES to add extra items for group members
956# to the contents of the HTML help documentation and to the tree view.
957
958TOC_EXPAND = NO
959
960# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
961# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated
962# that can be used as input for Qt's qhelpgenerator to generate a
963# Qt Compressed Help (.qch) of the generated HTML documentation.
964
965GENERATE_QHP = NO
966
967# If the QHG_LOCATION tag is specified, the QCH_FILE tag can
968# be used to specify the file name of the resulting .qch file.
969# The path specified is relative to the HTML output folder.
970
971QCH_FILE =
972
973# The QHP_NAMESPACE tag specifies the namespace to use when generating
974# Qt Help Project output. For more information please see
975# http://doc.trolltech.com/qthelpproject.html#namespace
976
977QHP_NAMESPACE = org.enlightenment.Eet
978
979# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating
980# Qt Help Project output. For more information please see
981# http://doc.trolltech.com/qthelpproject.html#virtual-folders
982
983QHP_VIRTUAL_FOLDER = doc
984
985# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to
986# add. For more information please see
987# http://doc.trolltech.com/qthelpproject.html#custom-filters
988
989QHP_CUST_FILTER_NAME =
990
991# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the
992# custom filter to add. For more information please see
993# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">
994# Qt Help Project / Custom Filters</a>.
995
996QHP_CUST_FILTER_ATTRS =
997
998# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
999# project's
1000# filter section matches.
1001# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">
1002# Qt Help Project / Filter Attributes</a>.
1003
1004QHP_SECT_FILTER_ATTRS =
1005
1006# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can
1007# be used to specify the location of Qt's qhelpgenerator.
1008# If non-empty doxygen will try to run qhelpgenerator on the generated
1009# .qhp file.
1010
1011QHG_LOCATION =
1012
1013# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files
1014# will be generated, which together with the HTML files, form an Eclipse help
1015# plugin. To install this plugin and make it available under the help contents
1016# menu in Eclipse, the contents of the directory containing the HTML and XML
1017# files needs to be copied into the plugins directory of eclipse. The name of
1018# the directory within the plugins directory should be the same as
1019# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before
1020# the help appears.
1021
1022GENERATE_ECLIPSEHELP = NO
1023
1024# A unique identifier for the eclipse help plugin. When installing the plugin
1025# the directory name containing the HTML and XML files should also have
1026# this name.
1027
1028ECLIPSE_DOC_ID = org.enlightenment.Eet
1029
1030# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
1031# top of each HTML page. The value NO (the default) enables the index and
1032# the value YES disables it.
1033
1034DISABLE_INDEX = YES
1035
1036# This tag can be used to set the number of enum values (range [0,1..20])
1037# that doxygen will group on one line in the generated HTML documentation.
1038# Note that a value of 0 will completely suppress the enum values from appearing in the overview section.
1039
1040ENUM_VALUES_PER_LINE = 1
1041
1042# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1043# structure should be generated to display hierarchical information.
1044# If the tag value is set to YES, a side panel will be generated
1045# containing a tree-like index structure (just like the one that
1046# is generated for HTML Help). For this to work a browser that supports
1047# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).
1048# Windows users are probably better off using the HTML help feature.
1049
1050GENERATE_TREEVIEW = NO
1051
1052# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
1053# used to set the initial width (in pixels) of the frame in which the tree
1054# is shown.
1055
1056TREEVIEW_WIDTH = 250
1057
1058# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open
1059# links to external symbols imported via tag files in a separate window.
1060
1061EXT_LINKS_IN_WINDOW = NO
1062
1063# Use this tag to change the font size of Latex formulas included
1064# as images in the HTML documentation. The default is 10. Note that
1065# when you change the font size after a successful doxygen run you need
1066# to manually remove any form_*.png images from the HTML output directory
1067# to force them to be regenerated.
1068
1069FORMULA_FONTSIZE = 10
1070
1071# Use the FORMULA_TRANPARENT tag to determine whether or not the images
1072# generated for formulas are transparent PNGs. Transparent PNGs are
1073# not supported properly for IE 6.0, but are supported on all modern browsers.
1074# Note that when changing this option you need to delete any form_*.png files
1075# in the HTML output before the changes have effect.
1076
1077FORMULA_TRANSPARENT = YES
1078
1079# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax
1080# (see http://www.mathjax.org) which uses client side Javascript for the
1081# rendering instead of using prerendered bitmaps. Use this if you do not
1082# have LaTeX installed or if you want to formulas look prettier in the HTML
1083# output. When enabled you also need to install MathJax separately and
1084# configure the path to it using the MATHJAX_RELPATH option.
1085
1086USE_MATHJAX = NO
1087
1088# When MathJax is enabled you need to specify the location relative to the
1089# HTML output directory using the MATHJAX_RELPATH option. The destination
1090# directory should contain the MathJax.js script. For instance, if the mathjax
1091# directory is located at the same level as the HTML output directory, then
1092# MATHJAX_RELPATH should be ../mathjax. The default value points to the mathjax.org site, so you can quickly see the result without installing
1093# MathJax, but it is strongly recommended to install a local copy of MathJax
1094# before deployment.
1095
1096MATHJAX_RELPATH = http://www.mathjax.org/mathjax
1097
1098# When the SEARCHENGINE tag is enabled doxygen will generate a search box
1099# for the HTML output. The underlying search engine uses javascript
1100# and DHTML and should work on any modern browser. Note that when using
1101# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets
1102# (GENERATE_DOCSET) there is already a search function so this one should
1103# typically be disabled. For large projects the javascript based search engine
1104# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.
1105
1106SEARCHENGINE = NO
1107
1108# When the SERVER_BASED_SEARCH tag is enabled the search engine will be
1109# implemented using a PHP enabled web server instead of at the web client
1110# using Javascript. Doxygen will generate the search PHP script and index
1111# file to put on the web server. The advantage of the server
1112# based approach is that it scales better to large projects and allows
1113# full text search. The disadvantages are that it is more difficult to setup
1114# and does not have live searching capabilities.
1115
1116SERVER_BASED_SEARCH = NO
1117
1118#---------------------------------------------------------------------------
1119# configuration options related to the LaTeX output
1120#---------------------------------------------------------------------------
1121
1122# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
1123# generate Latex output.
1124
1125GENERATE_LATEX = YES
1126
1127# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
1128# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1129# put in front of it. If left blank `latex' will be used as the default path.
1130
1131LATEX_OUTPUT = latex
1132
1133# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
1134# invoked. If left blank `latex' will be used as the default command name.
1135# Note that when enabling USE_PDFLATEX this option is only used for
1136# generating bitmaps for formulas in the HTML output, but not in the
1137# Makefile that is written to the output directory.
1138
1139LATEX_CMD_NAME = latex
1140
1141# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
1142# generate index for LaTeX. If left blank `makeindex' will be used as the
1143# default command name.
1144
1145MAKEINDEX_CMD_NAME = makeindex
1146
1147# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
1148# LaTeX documents. This may be useful for small projects and may help to
1149# save some trees in general.
1150
1151COMPACT_LATEX = NO
1152
1153# The PAPER_TYPE tag can be used to set the paper type that is used
1154# by the printer. Possible values are: a4, letter, legal and
1155# executive. If left blank a4wide will be used.
1156
1157PAPER_TYPE = a4wide
1158
1159# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
1160# packages that should be included in the LaTeX output.
1161
1162EXTRA_PACKAGES =
1163
1164# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
1165# the generated latex document. The header should contain everything until
1166# the first chapter. If it is left blank doxygen will generate a
1167# standard header. Notice: only use this tag if you know what you are doing!
1168
1169LATEX_HEADER =
1170
1171# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
1172# is prepared for conversion to pdf (using ps2pdf). The pdf file will
1173# contain links (just like the HTML output) instead of page references
1174# This makes the output suitable for online browsing using a pdf viewer.
1175
1176PDF_HYPERLINKS = YES
1177
1178# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
1179# plain latex in the generated Makefile. Set this option to YES to get a
1180# higher quality PDF documentation.
1181
1182USE_PDFLATEX = YES
1183
1184# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
1185# command to the generated LaTeX files. This will instruct LaTeX to keep
1186# running if errors occur, instead of asking the user for help.
1187# This option is also used when generating formulas in HTML.
1188
1189LATEX_BATCHMODE = NO
1190
1191# If LATEX_HIDE_INDICES is set to YES then doxygen will not
1192# include the index chapters (such as File Index, Compound Index, etc.)
1193# in the output.
1194
1195LATEX_HIDE_INDICES = NO
1196
1197# If LATEX_SOURCE_CODE is set to YES then doxygen will include
1198# source code with syntax highlighting in the LaTeX output.
1199# Note that which sources are shown also depends on other settings
1200# such as SOURCE_BROWSER.
1201
1202LATEX_SOURCE_CODE = NO
1203
1204#---------------------------------------------------------------------------
1205# configuration options related to the RTF output
1206#---------------------------------------------------------------------------
1207
1208# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
1209# The RTF output is optimized for Word 97 and may not look very pretty with
1210# other RTF readers or editors.
1211
1212GENERATE_RTF = NO
1213
1214# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
1215# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1216# put in front of it. If left blank `rtf' will be used as the default path.
1217
1218RTF_OUTPUT = rtf
1219
1220# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
1221# RTF documents. This may be useful for small projects and may help to
1222# save some trees in general.
1223
1224COMPACT_RTF = NO
1225
1226# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
1227# will contain hyperlink fields. The RTF file will
1228# contain links (just like the HTML output) instead of page references.
1229# This makes the output suitable for online browsing using WORD or other
1230# programs which support those fields.
1231# Note: wordpad (write) and others do not support links.
1232
1233RTF_HYPERLINKS = NO
1234
1235# Load stylesheet definitions from file. Syntax is similar to doxygen's
1236# config file, i.e. a series of assignments. You only have to provide
1237# replacements, missing definitions are set to their default value.
1238
1239RTF_STYLESHEET_FILE =
1240
1241# Set optional variables used in the generation of an rtf document.
1242# Syntax is similar to doxygen's config file.
1243
1244RTF_EXTENSIONS_FILE =
1245
1246#---------------------------------------------------------------------------
1247# configuration options related to the man page output
1248#---------------------------------------------------------------------------
1249
1250# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
1251# generate man pages
1252
1253GENERATE_MAN = NO
1254
1255# The MAN_OUTPUT tag is used to specify where the man pages will be put.
1256# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1257# put in front of it. If left blank `man' will be used as the default path.
1258
1259MAN_OUTPUT = man
1260
1261# The MAN_EXTENSION tag determines the extension that is added to
1262# the generated man pages (default is the subroutine's section .3)
1263
1264MAN_EXTENSION = .3
1265
1266# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
1267# then it will generate one additional man file for each entity
1268# documented in the real man page(s). These additional files
1269# only source the real man page, but without them the man command
1270# would be unable to find the correct page. The default is NO.
1271
1272MAN_LINKS = YES
1273
1274#---------------------------------------------------------------------------
1275# configuration options related to the XML output
1276#---------------------------------------------------------------------------
1277
1278# If the GENERATE_XML tag is set to YES Doxygen will
1279# generate an XML file that captures the structure of
1280# the code including all documentation.
1281
1282GENERATE_XML = NO
1283
1284# The XML_OUTPUT tag is used to specify where the XML pages will be put.
1285# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1286# put in front of it. If left blank `xml' will be used as the default path.
1287
1288XML_OUTPUT = xml
1289
1290# The XML_SCHEMA tag can be used to specify an XML schema,
1291# which can be used by a validating XML parser to check the
1292# syntax of the XML files.
1293
1294XML_SCHEMA =
1295
1296# The XML_DTD tag can be used to specify an XML DTD,
1297# which can be used by a validating XML parser to check the
1298# syntax of the XML files.
1299
1300XML_DTD =
1301
1302# If the XML_PROGRAMLISTING tag is set to YES Doxygen will
1303# dump the program listings (including syntax highlighting
1304# and cross-referencing information) to the XML output. Note that
1305# enabling this will significantly increase the size of the XML output.
1306
1307XML_PROGRAMLISTING = YES
1308
1309#---------------------------------------------------------------------------
1310# configuration options for the AutoGen Definitions output
1311#---------------------------------------------------------------------------
1312
1313# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
1314# generate an AutoGen Definitions (see autogen.sf.net) file
1315# that captures the structure of the code including all
1316# documentation. Note that this feature is still experimental
1317# and incomplete at the moment.
1318
1319GENERATE_AUTOGEN_DEF = NO
1320
1321#---------------------------------------------------------------------------
1322# configuration options related to the Perl module output
1323#---------------------------------------------------------------------------
1324
1325# If the GENERATE_PERLMOD tag is set to YES Doxygen will
1326# generate a Perl module file that captures the structure of
1327# the code including all documentation. Note that this
1328# feature is still experimental and incomplete at the
1329# moment.
1330
1331GENERATE_PERLMOD = NO
1332
1333# If the PERLMOD_LATEX tag is set to YES Doxygen will generate
1334# the necessary Makefile rules, Perl scripts and LaTeX code to be able
1335# to generate PDF and DVI output from the Perl module output.
1336
1337PERLMOD_LATEX = NO
1338
1339# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
1340# nicely formatted so it can be parsed by a human reader.
1341# This is useful
1342# if you want to understand what is going on.
1343# On the other hand, if this
1344# tag is set to NO the size of the Perl module output will be much smaller
1345# and Perl will parse it just the same.
1346
1347PERLMOD_PRETTY = YES
1348
1349# The names of the make variables in the generated doxyrules.make file
1350# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
1351# This is useful so different doxyrules.make files included by the same
1352# Makefile don't overwrite each other's variables.
1353
1354PERLMOD_MAKEVAR_PREFIX =
1355
1356#---------------------------------------------------------------------------
1357# Configuration options related to the preprocessor
1358#---------------------------------------------------------------------------
1359
1360# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
1361# evaluate all C-preprocessor directives found in the sources and include
1362# files.
1363
1364ENABLE_PREPROCESSING = YES
1365
1366# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
1367# names in the source code. If set to NO (the default) only conditional
1368# compilation will be performed. Macro expansion can be done in a controlled
1369# way by setting EXPAND_ONLY_PREDEF to YES.
1370
1371MACRO_EXPANSION = YES
1372
1373# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
1374# then the macro expansion is limited to the macros specified with the
1375# PREDEFINED and EXPAND_AS_DEFINED tags.
1376
1377EXPAND_ONLY_PREDEF = YES
1378
1379# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
1380# in the INCLUDE_PATH (see below) will be search if a #include is found.
1381
1382SEARCH_INCLUDES = NO
1383
1384# The INCLUDE_PATH tag can be used to specify one or more directories that
1385# contain include files that are not input files but should be processed by
1386# the preprocessor.
1387
1388INCLUDE_PATH =
1389
1390# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
1391# patterns (like *.h and *.hpp) to filter out the header-files in the
1392# directories. If left blank, the patterns specified with FILE_PATTERNS will
1393# be used.
1394
1395INCLUDE_FILE_PATTERNS =
1396
1397# The PREDEFINED tag can be used to specify one or more macro names that
1398# are defined before the preprocessor is started (similar to the -D option of
1399# gcc). The argument of the tag is a list of macros of the form: name
1400# or name=definition (no spaces). If the definition and the = are
1401# omitted =1 is assumed. To prevent a macro definition from being
1402# undefined via #undef or recursively expanded use the := operator
1403# instead of the = operator.
1404
1405PREDEFINED = EINA_MAGIC_DEBUG \
1406 __UNUSED__= \
1407 EINA_ARG_NONNULL()= \
1408 EINA_MALLOC= \
1409 EINA_WARN_UNUSED_RESULT= \
1410 EAPI= \
1411 EINA_PURE= \
1412 EINA_CONST=
1413
1414# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
1415# this tag can be used to specify a list of macro names that should be expanded.
1416# The macro definition that is found in the sources will be used.
1417# Use the PREDEFINED tag if you want to use a different macro definition that overrules the definition found in the source code.
1418
1419EXPAND_AS_DEFINED =
1420
1421# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
1422# doxygen's preprocessor will remove all references to function-like macros
1423# that are alone on a line, have an all uppercase name, and do not end with a
1424# semicolon, because these will confuse the parser if not removed.
1425
1426SKIP_FUNCTION_MACROS = YES
1427
1428#---------------------------------------------------------------------------
1429# Configuration::additions related to external references
1430#---------------------------------------------------------------------------
1431
1432# The TAGFILES option can be used to specify one or more tagfiles.
1433# Optionally an initial location of the external documentation
1434# can be added for each tagfile. The format of a tag file without
1435# this location is as follows:
1436#
1437# TAGFILES = file1 file2 ...
1438# Adding location for the tag files is done as follows:
1439#
1440# TAGFILES = file1=loc1 "file2 = loc2" ...
1441# where "loc1" and "loc2" can be relative or absolute paths or
1442# URLs. If a location is present for each tag, the installdox tool
1443# does not have to be run to correct the links.
1444# Note that each tag file must have a unique name
1445# (where the name does NOT include the path)
1446# If a tag file is not located in the directory in which doxygen
1447# is run, you must also specify the path to the tagfile here.
1448
1449TAGFILES =
1450
1451# When a file name is specified after GENERATE_TAGFILE, doxygen will create
1452# a tag file that is based on the input files it reads.
1453
1454GENERATE_TAGFILE =
1455
1456# If the ALLEXTERNALS tag is set to YES all external classes will be listed
1457# in the class index. If set to NO only the inherited external classes
1458# will be listed.
1459
1460ALLEXTERNALS = NO
1461
1462# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1463# in the modules index. If set to NO, only the current project's groups will
1464# be listed.
1465
1466EXTERNAL_GROUPS = YES
1467
1468# The PERL_PATH should be the absolute path and name of the perl script
1469# interpreter (i.e. the result of `which perl').
1470
1471PERL_PATH = /usr/bin/perl
1472
1473#---------------------------------------------------------------------------
1474# Configuration options related to the dot tool
1475#---------------------------------------------------------------------------
1476
1477# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1478# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
1479# or super classes. Setting the tag to NO turns the diagrams off. Note that
1480# this option also works with HAVE_DOT disabled, but it is recommended to
1481# install and use dot, since it yields more powerful graphs.
1482
1483CLASS_DIAGRAMS = NO
1484
1485# You can define message sequence charts within doxygen comments using the \msc
1486# command. Doxygen will then run the mscgen tool (see
1487# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the
1488# documentation. The MSCGEN_PATH tag allows you to specify the directory where
1489# the mscgen tool resides. If left empty the tool is assumed to be found in the
1490# default search path.
1491
1492MSCGEN_PATH =
1493
1494# If set to YES, the inheritance and collaboration graphs will hide
1495# inheritance and usage relations if the target is undocumented
1496# or is not a class.
1497
1498HIDE_UNDOC_RELATIONS = YES
1499
1500# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1501# available from the path. This tool is part of Graphviz, a graph visualization
1502# toolkit from AT&T and Lucent Bell Labs. The other options in this section
1503# have no effect if this option is set to NO (the default)
1504
1505HAVE_DOT = NO
1506
1507# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is
1508# allowed to run in parallel. When set to 0 (the default) doxygen will
1509# base this on the number of processors available in the system. You can set it
1510# explicitly to a value larger than 0 to get control over the balance
1511# between CPU load and processing speed.
1512
1513DOT_NUM_THREADS = 0
1514
1515# By default doxygen will write a font called Helvetica to the output
1516# directory and reference it in all dot files that doxygen generates.
1517# When you want a differently looking font you can specify the font name
1518# using DOT_FONTNAME. You need to make sure dot is able to find the font,
1519# which can be done by putting it in a standard location or by setting the
1520# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory
1521# containing the font.
1522
1523DOT_FONTNAME = Helvetica
1524
1525# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs.
1526# The default size is 10pt.
1527
1528DOT_FONTSIZE = 10
1529
1530# By default doxygen will tell dot to use the output directory to look for the
1531# FreeSans.ttf font (which doxygen will put there itself). If you specify a
1532# different font using DOT_FONTNAME you can set the path where dot
1533# can find it using this tag.
1534
1535DOT_FONTPATH =
1536
1537# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
1538# will generate a graph for each documented class showing the direct and
1539# indirect inheritance relations. Setting this tag to YES will force the
1540# the CLASS_DIAGRAMS tag to NO.
1541
1542CLASS_GRAPH = NO
1543
1544# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
1545# will generate a graph for each documented class showing the direct and
1546# indirect implementation dependencies (inheritance, containment, and
1547# class references variables) of the class with other documented classes.
1548
1549COLLABORATION_GRAPH = NO
1550
1551# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
1552# will generate a graph for groups, showing the direct groups dependencies
1553
1554GROUP_GRAPHS = YES
1555
1556# If the UML_LOOK tag is set to YES doxygen will generate inheritance and
1557# collaboration diagrams in a style similar to the OMG's Unified Modeling
1558# Language.
1559
1560UML_LOOK = NO
1561
1562# If set to YES, the inheritance and collaboration graphs will show the
1563# relations between templates and their instances.
1564
1565TEMPLATE_RELATIONS = NO
1566
1567# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
1568# tags are set to YES then doxygen will generate a graph for each documented
1569# file showing the direct and indirect include dependencies of the file with
1570# other documented files.
1571
1572INCLUDE_GRAPH = NO
1573
1574# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
1575# HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1576# documented header file showing the documented files that directly or
1577# indirectly include this file.
1578
1579INCLUDED_BY_GRAPH = NO
1580
1581# If the CALL_GRAPH and HAVE_DOT options are set to YES then
1582# doxygen will generate a call dependency graph for every global function
1583# or class method. Note that enabling this option will significantly increase
1584# the time of a run. So in most cases it will be better to enable call graphs
1585# for selected functions only using the \callgraph command.
1586
1587CALL_GRAPH = NO
1588
1589# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then
1590# doxygen will generate a caller dependency graph for every global function
1591# or class method. Note that enabling this option will significantly increase
1592# the time of a run. So in most cases it will be better to enable caller
1593# graphs for selected functions only using the \callergraph command.
1594
1595CALLER_GRAPH = NO
1596
1597# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
1598# will generate a graphical hierarchy of all classes instead of a textual one.
1599
1600GRAPHICAL_HIERARCHY = NO
1601
1602# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
1603# then doxygen will show the dependencies a directory has on other directories
1604# in a graphical way. The dependency relations are determined by the #include
1605# relations between the files in the directories.
1606
1607DIRECTORY_GRAPH = YES
1608
1609# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1610# generated by dot. Possible values are png, svg, gif or svg.
1611# If left blank png will be used.
1612
1613DOT_IMAGE_FORMAT = png
1614
1615# The tag DOT_PATH can be used to specify the path where the dot tool can be
1616# found. If left blank, it is assumed the dot tool can be found in the path.
1617
1618DOT_PATH =
1619
1620# The DOTFILE_DIRS tag can be used to specify one or more directories that
1621# contain dot files that are included in the documentation (see the
1622# \dotfile command).
1623
1624DOTFILE_DIRS =
1625
1626# The MSCFILE_DIRS tag can be used to specify one or more directories that
1627# contain msc files that are included in the documentation (see the
1628# \mscfile command).
1629
1630MSCFILE_DIRS =
1631
1632# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of
1633# nodes that will be shown in the graph. If the number of nodes in a graph
1634# becomes larger than this value, doxygen will truncate the graph, which is
1635# visualized by representing a node as a red box. Note that doxygen if the
1636# number of direct children of the root node in a graph is already larger than
1637# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note
1638# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
1639
1640DOT_GRAPH_MAX_NODES = 50
1641
1642# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
1643# graphs generated by dot. A depth value of 3 means that only nodes reachable
1644# from the root by following a path via at most 3 edges will be shown. Nodes
1645# that lay further from the root node will be omitted. Note that setting this
1646# option to 1 or 2 may greatly reduce the computation time needed for large
1647# code bases. Also note that the size of a graph can be further restricted by
1648# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
1649
1650MAX_DOT_GRAPH_DEPTH = 0
1651
1652# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
1653# background. This is disabled by default, because dot on Windows does not
1654# seem to support this out of the box. Warning: Depending on the platform used,
1655# enabling this option may lead to badly anti-aliased labels on the edges of
1656# a graph (i.e. they become hard to read).
1657
1658DOT_TRANSPARENT = YES
1659
1660# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
1661# files in one run (i.e. multiple -o and -T options on the command line). This
1662# makes dot run faster, but since only newer versions of dot (>1.8.10)
1663# support this, this feature is disabled by default.
1664
1665DOT_MULTI_TARGETS = NO
1666
1667# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1668# generate a legend page explaining the meaning of the various boxes and
1669# arrows in the dot generated graphs.
1670
1671GENERATE_LEGEND = YES
1672
1673# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1674# remove the intermediate dot files that are used to generate
1675# the various graphs.
1676
1677DOT_CLEANUP = YES
diff --git a/legacy/eet/doc/Makefile.am b/legacy/eet/doc/Makefile.am
deleted file mode 100644
index f49a79b896..0000000000
--- a/legacy/eet/doc/Makefile.am
+++ /dev/null
@@ -1,41 +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 \
41 $(srcdir)/examples.dox
diff --git a/legacy/eet/doc/e.css b/legacy/eet/doc/e.css
deleted file mode 100644
index 07ebd1e5bb..0000000000
--- a/legacy/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/legacy/eet/doc/eet.dox.in b/legacy/eet/doc/eet.dox.in
deleted file mode 100644
index e69de29bb2..0000000000
--- a/legacy/eet/doc/eet.dox.in
+++ /dev/null
diff --git a/legacy/eet/doc/examples.dox b/legacy/eet/doc/examples.dox
deleted file mode 100644
index b842584466..0000000000
--- a/legacy/eet/doc/examples.dox
+++ /dev/null
@@ -1,184 +0,0 @@
1/**
2 * @page Examples Examples
3 *
4 * Here is a page with examples.
5 *
6 * @ref Example_Eet_Data_Simple
7 *
8 * @ref Example_Eet_Data_Nested
9 *
10 * @ref Example_Eet_Data_File_Descriptor_01
11 *
12 * @ref Example_Eet_Data_File_Descriptor_02
13 *
14 * @ref Example_Eet_Data_Cipher_Decipher
15 *
16 * <a href="examples.html">List of examples</a>
17 */
18
19/**
20 * @page Example_Eet_Basic Very basic Eet example
21 *
22 * @includelineno eet-basic.c
23 * @example eet-basic.c
24 */
25
26/**
27 * @page Example_Eet_File Example of the various ways to interface with an Eet File
28 *
29 * @includelineno eet-file.c
30 * @example eet-file.c
31 */
32
33/**
34 * @page Example_Eet_Data_Simple Simple data example
35 *
36 * @includelineno eet-data-simple.c
37 * @example eet-data-simple.c
38 */
39
40/**
41 * @page Example_Eet_Data_Nested Nested data example
42 *
43 * @includelineno eet-data-nested.c
44 * @example eet-data-nested.c
45 */
46
47/**
48 * @page Example_Eet_Data_File_Descriptor_01 File descriptor data example
49 *
50 * @includelineno eet-data-file_descriptor_01.c
51 * @example eet-data-file_descriptor_01.c
52 */
53
54/**
55 * @page Example_Eet_Data_File_Descriptor_02 File descriptor data example, with Eet unions and variants
56 *
57 * This is an example much like the one shown in @ref
58 * eet_data_file_descriptor. The difference is that here we're
59 * attaining ourselves to two new data types to store in an Eet file
60 * -- @b unions and @b variants. We don't try to come with data
61 * mapping to real world use cases, here. Instead, we're defining
62 * 3 different simple structures to be used throughout the example:
63 * @dontinclude eet-data-file_descriptor_02.c
64 * @skip typedef struct _Example_Struct1
65 * @until typedef struct _Example_Struct3
66 * @skip struct _Example_Struct1
67 * @until int body
68 * @until };
69 *
70 * To identify, for both union and variant data cases, the type of
71 * each chunk of data, we're defining types to point to each of those
72 * structs:
73 * @dontinclude eet-data-file_descriptor_02.c
74 * @skip typedef enum _Example_Data_Type
75 * @until ;
76 * @skip enum _Example_Data_Type
77 * @until };
78 *
79 * We have also a mapping from those types to name strings, to be used
80 * in the Eet unions and variants @c type_get() and @c type_set() type
81 * identifying callbacks:
82 * @skip struct
83 * @until };
84 *
85 * In this example, we have no fancy hash to store our data into
86 * profiles/accounts, but just two lists for union and variant data
87 * nodes:
88 * @dontinclude eet-data-file_descriptor_02.c
89 * @skip typedef struct _Example_Lists
90 * @until typedef struct _Example_Lists
91 * @skip struct _Example_Lists
92 * @until };
93 *
94 * Let's begin with our unions, then, which look like:
95 * @dontinclude eet-data-file_descriptor_02.c
96 * @skip typedef struct _Example_Union
97 * @until typedef struct _Example_Union
98 * @skip struct _Example_Union
99 * @until };
100 *
101 * The first interesting part of the code is where we define our data
102 * descriptors for the main lists, the unions and all of structures
103 * upon which those two depend.
104 * @dontinclude eet-data-file_descriptor_02.c
105 * @skip declaring types
106 * @until _union_descriptor);
107 * The code for descriptors on @c Example_Struct1, @c Example_Struct2
108 * and @c Example_Struct3 is straightforward, a matter already covered
109 * on @ref eet_data_file_descriptor. What is new, here, are the two
110 * type matching functions for our unions. There, we must set the @c
111 * data pointer to its matching type, on @c _union_type_set and return
112 * the correct matching type, on @c _union_type_get:
113 * @dontinclude eet-data-file_descriptor_02.c
114 * @skip union type_get()
115 * @until _union_type_set
116 * @until _union_type_set
117 *
118 * With the #EET_DATA_DESCRIPTOR_ADD_MAPPING calls, which follow, we
119 * make the the link between our type names and their respective
120 * structs. The code handling actual data is pretty much the same as in
121 * @ref eet_data_file_descriptor -- one uses command line arguments to
122 * enter new data chunks (or just to visualize the contents of an Eet
123 * file), signalling if they are unions or variants. One must also
124 * pass the type of the data chuck to enter, with integers 1, 2 or
125 * 3. Then, come the fields for each type:
126 * @dontinclude eet-data-file_descriptor_02.c
127 * @skip Usage
128 * @until argv
129 *
130 * Variants are very similar to unions, except that data chunks need
131 * @b not contain previously allocated space for each of the possible
132 * types of data going in them:
133 * @dontinclude eet-data-file_descriptor_02.c
134 * @skip typedef struct _Example_Variant
135 * @until typedef struct _Example_Variant
136 * @skip struct _Example_Variant_Type
137 * @until };
138 * @until };
139 *
140 * The code declaring the data descriptors and handling the data is
141 * very similar to the unions part, and is left for the reader to
142 * check for him/herself. The complete code of the example follows.
143 *
144 * @includelineno eet-data-file_descriptor_02.c
145 * @example eet-data-file_descriptor_02.c
146 */
147
148/**
149 * @page Example_Eet_Data_Cipher_Decipher Eet data cipher/decipher example
150 *
151 * In this example, we exemplify the usage of eet_write_cipher() and
152 * eet_read_cipher(). For it to work, <b>make sure</b> to have your
153 * Eet installation with a ciphering backend enabled.
154 *
155 * We start by defining the information to record in an Eet file (@c
156 * buffer), the key to cipher that (@c key) and a dummy wrong key to
157 * try to access that information, later (@c key_bad).
158 * @dontinclude eet-data-cipher_decipher.c
159 * @skip buffer =
160 * @until bad =
161 *
162 * After opening our file, we simply use the first cited function to
163 * write our string ciphered:
164 * @dontinclude eet-data-cipher_decipher.c
165 * @skip eet_open
166 * @until eet_close
167 *
168 * Then, after closing it on purpose, we open it again, to retrieve
169 * the encrypted information back, in a readable format:
170 * @skip eet_open
171 * @until eet_close
172 * @until eet_close
173 *
174 * Note that we do it twice, being the last time with the wrong
175 * key. In this last case, if the information is read back and matches
176 * the original @c buffer, something wrong is going on (we made it to
177 * fail on purpose). The former access is OK, and must work.
178 *
179 * What we do in sequence is just to delete the file. The complete
180 * code of the example follows.
181 *
182 * @includelineno eet-data-cipher_decipher.c
183 * @example eet-data-cipher_decipher.c
184 */
diff --git a/legacy/eet/doc/head.html b/legacy/eet/doc/head.html
deleted file mode 100644
index 519631b676..0000000000
--- a/legacy/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/legacy/eet/doc/img/e.png b/legacy/eet/doc/img/e.png
deleted file mode 100755
index b3884a5cbc..0000000000
--- a/legacy/eet/doc/img/e.png
+++ /dev/null
Binary files differ
diff --git a/legacy/eet/doc/img/e_big.png b/legacy/eet/doc/img/e_big.png
deleted file mode 100755
index d42aeb4200..0000000000
--- a/legacy/eet/doc/img/e_big.png
+++ /dev/null
Binary files differ
diff --git a/legacy/eet/doc/img/edoxy.css b/legacy/eet/doc/img/edoxy.css
deleted file mode 100755
index 616a0c56ae..0000000000
--- a/legacy/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;