summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCarsten Haitzler <raster@rasterman.com>2012-12-13 05:32:12 +0000
committerCarsten Haitzler <raster@rasterman.com>2012-12-13 05:32:12 +0000
commit6e7e05a008fffdb927bf73a81c14512b10aca10d (patch)
tree99099e61f457e660536e0c7f28fba4e8fe2a5e0c
parent1a542bcf8bbcb94dcee65b8adf0b844d0478c809 (diff)
move escape and eio to IN-EFL.
SVN revision: 80794
-rw-r--r--legacy/eio/.gitignore44
-rw-r--r--legacy/eio/AUTHORS8
-rw-r--r--legacy/eio/COPYING537
-rw-r--r--legacy/eio/INSTALL365
-rw-r--r--legacy/eio/Makefile.am53
-rw-r--r--legacy/eio/TODO1
-rwxr-xr-xlegacy/eio/autogen.sh39
-rw-r--r--legacy/eio/configure.ac281
-rw-r--r--legacy/eio/doc/Doxyfile.in1613
-rw-r--r--legacy/eio/doc/Makefile.am32
-rw-r--r--legacy/eio/doc/e.css218
-rw-r--r--legacy/eio/doc/eio.dox.in456
-rw-r--r--legacy/eio/doc/foot.html19
-rw-r--r--legacy/eio/doc/head.html67
-rw-r--r--legacy/eio/doc/img/e.pngbin3825 -> 0 bytes
-rw-r--r--legacy/eio/doc/img/edoxy.css483
-rw-r--r--legacy/eio/doc/img/foot_bg.pngbin173 -> 0 bytes
-rw-r--r--legacy/eio/doc/img/head_bg.pngbin214 -> 0 bytes
-rw-r--r--legacy/eio/doc/img/menu_bg.pngbin192 -> 0 bytes
-rw-r--r--legacy/eio/doc/img/menu_bg_current.pngbin1200 -> 0 bytes
-rw-r--r--legacy/eio/doc/img/menu_bg_hover.pngbin3278 -> 0 bytes
-rw-r--r--legacy/eio/doc/img/menu_bg_last.pngbin637 -> 0 bytes
-rw-r--r--legacy/eio/doc/img/menu_bg_unsel.pngbin1596 -> 0 bytes
-rw-r--r--legacy/eio/eio.spec.in60
-rw-r--r--legacy/eio/m4/ac_attribute.m446
-rw-r--r--legacy/eio/m4/efl_doxygen.m494
-rw-r--r--legacy/eio/m4/efl_examples.m463
-rw-r--r--legacy/eio/m4/efl_path_max.m436
-rw-r--r--legacy/eio/m4/efl_threads.m4206
-rw-r--r--legacy/eio/m4/eio_check_options.m486
-rw-r--r--legacy/eio/src/Makefile.am4
-rw-r--r--legacy/eio/src/examples/Makefile.am30
-rw-r--r--legacy/eio/src/lib/Makefile.am34
-rw-r--r--legacy/escape/ABOUT-NLS0
-rw-r--r--legacy/escape/AUTHORS3
-rw-r--r--legacy/escape/COPYING674
-rw-r--r--legacy/escape/Makefile.am30
-rw-r--r--legacy/escape/NEWS1
-rwxr-xr-xlegacy/escape/autogen.sh40
-rw-r--r--legacy/escape/configure.ac122
-rw-r--r--legacy/escape/m4/efl_path_max.m436
-rw-r--r--legacy/escape/src/Makefile.am3
-rw-r--r--legacy/escape/src/lib/Makefile.am31
43 files changed, 0 insertions, 5815 deletions
diff --git a/legacy/eio/.gitignore b/legacy/eio/.gitignore
deleted file mode 100644
index 18023e6d49..0000000000
--- a/legacy/eio/.gitignore
+++ /dev/null
@@ -1,44 +0,0 @@
1*.o
2*.swp
3*.swo
4*~
5*.lo
6*.la
7.deps
8.libs
9ABOUT-NLS
10Makefile
11Makefile.in
12aclocal.m4
13autom4te.cache/
14compile
15config.cache
16config.cache-env
17config.guess
18config.h
19config.h.in
20config.log
21config.status
22config.sub
23configure
24depcomp
25doc/Doxyfile
26doc/Makefile
27doc/Makefile.in
28doc/eio.dox
29eio.pc
30eio.spec
31install-sh
32libtool
33ltmain.sh
34m4/libtool.m4
35m4/ltoptions.m4
36m4/ltsugar.m4
37m4/ltversion.m4
38m4/lt~obsolete.m4
39missing
40src/Makefile
41src/Makefile.in
42src/lib/Makefile
43src/lib/Makefile.in
44stamp-h1
diff --git a/legacy/eio/AUTHORS b/legacy/eio/AUTHORS
deleted file mode 100644
index 27aeadc3bf..0000000000
--- a/legacy/eio/AUTHORS
+++ /dev/null
@@ -1,8 +0,0 @@
1Cedric Bail <cedric.bail@free.fr>
2Stephen Houston <UnixTitan@gmail.com>
3Gustavo Sverzut Barbieri <barbieri@gmail.com>
4Vincent "caro" Torri <vtorri at univ-evry dot fr>
5Mikael SANS <sans.mikael@gmail.com>
6Mike Blumenkrantz (zmike/discomfitor) <michael.blumenkrantz@gmail.com>
7Jérôme Pinot <ngc891@gmail.com>
8Daniel Willmann <d.willmann@samsung.com>
diff --git a/legacy/eio/COPYING b/legacy/eio/COPYING
deleted file mode 100644
index 63f364e837..0000000000
--- a/legacy/eio/COPYING
+++ /dev/null
@@ -1,537 +0,0 @@
1Copyright notice for EIO:
2
3Copyright (C) 2010-2011 Cedric Bail and various contributors (see AUTHORS)
4
5This library is free software; you can redistribute it and/or modify it
6under the terms of the GNU Lesser General Public License as published by the
7Free Software Foundation; version 2.1 of the License.
8
9This library is distributed in the hope that it will be useful, but WITHOUT
10ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
11FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more
12details.
13
14Below is a copy of the GNU Lesser General Public License that is distributed
15along with this library. If you do not have a copy below, write to the Free
16Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
1702110-1301 USA
18
19 GNU LESSER GENERAL PUBLIC LICENSE
20 Version 2.1, February 1999
21
22 Copyright (C) 1991, 1999 Free Software Foundation, Inc.
23 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
24 Everyone is permitted to copy and distribute verbatim copies
25 of this license document, but changing it is not allowed.
26
27[This is the first released version of the Lesser GPL. It also counts
28 as the successor of the GNU Library Public License, version 2, hence
29 the version number 2.1.]
30
31 Preamble
32
33 The licenses for most software are designed to take away your
34freedom to share and change it. By contrast, the GNU General Public
35Licenses are intended to guarantee your freedom to share and change
36free software--to make sure the software is free for all its users.
37
38 This license, the Lesser General Public License, applies to some
39specially designated software packages--typically libraries--of the
40Free Software Foundation and other authors who decide to use it. You
41can use it too, but we suggest you first think carefully about whether
42this license or the ordinary General Public License is the better
43strategy to use in any particular case, based on the explanations below.
44
45 When we speak of free software, we are referring to freedom of use,
46not price. Our General Public Licenses are designed to make sure that
47you have the freedom to distribute copies of free software (and charge
48for this service if you wish); that you receive source code or can get
49it if you want it; that you can change the software and use pieces of
50it in new free programs; and that you are informed that you can do
51these things.
52
53 To protect your rights, we need to make restrictions that forbid
54distributors to deny you these rights or to ask you to surrender these
55rights. These restrictions translate to certain responsibilities for
56you if you distribute copies of the library or if you modify it.
57
58 For example, if you distribute copies of the library, whether gratis
59or for a fee, you must give the recipients all the rights that we gave
60you. You must make sure that they, too, receive or can get the source
61code. If you link other code with the library, you must provide
62complete object files to the recipients, so that they can relink them
63with the library after making changes to the library and recompiling
64it. And you must show them these terms so they know their rights.
65
66 We protect your rights with a two-step method: (1) we copyright the
67library, and (2) we offer you this license, which gives you legal
68permission to copy, distribute and/or modify the library.
69
70 To protect each distributor, we want to make it very clear that
71there is no warranty for the free library. Also, if the library is
72modified by someone else and passed on, the recipients should know
73that what they have is not the original version, so that the original
74author's reputation will not be affected by problems that might be
75introduced by others.
76
77 Finally, software patents pose a constant threat to the existence of
78any free program. We wish to make sure that a company cannot
79effectively restrict the users of a free program by obtaining a
80restrictive license from a patent holder. Therefore, we insist that
81any patent license obtained for a version of the library must be
82consistent with the full freedom of use specified in this license.
83
84 Most GNU software, including some libraries, is covered by the
85ordinary GNU General Public License. This license, the GNU Lesser
86General Public License, applies to certain designated libraries, and
87is quite different from the ordinary General Public License. We use
88this license for certain libraries in order to permit linking those
89libraries into non-free programs.
90
91 When a program is linked with a library, whether statically or using
92a shared library, the combination of the two is legally speaking a
93combined work, a derivative of the original library. The ordinary
94General Public License therefore permits such linking only if the
95entire combination fits its criteria of freedom. The Lesser General
96Public License permits more lax criteria for linking other code with
97the library.
98
99 We call this license the "Lesser" General Public License because it
100does Less to protect the user's freedom than the ordinary General
101Public License. It also provides other free software developers Less
102of an advantage over competing non-free programs. These disadvantages
103are the reason we use the ordinary General Public License for many
104libraries. However, the Lesser license provides advantages in certain
105special circumstances.
106
107 For example, on rare occasions, there may be a special need to
108encourage the widest possible use of a certain library, so that it becomes
109a de-facto standard. To achieve this, non-free programs must be
110allowed to use the library. A more frequent case is that a free
111library does the same job as widely used non-free libraries. In this
112case, there is little to gain by limiting the free library to free
113software only, so we use the Lesser General Public License.
114
115 In other cases, permission to use a particular library in non-free
116programs enables a greater number of people to use a large body of
117free software. For example, permission to use the GNU C Library in
118non-free programs enables many more people to use the whole GNU
119operating system, as well as its variant, the GNU/Linux operating
120system.
121
122 Although the Lesser General Public License is Less protective of the
123users' freedom, it does ensure that the user of a program that is
124linked with the Library has the freedom and the wherewithal to run
125that program using a modified version of the Library.
126
127 The precise terms and conditions for copying, distribution and
128modification follow. Pay close attention to the difference between a
129"work based on the library" and a "work that uses the library". The
130former contains code derived from the library, whereas the latter must
131be combined with the library in order to run.
132
133 GNU LESSER GENERAL PUBLIC LICENSE
134 TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
135
136 0. This License Agreement applies to any software library or other
137program which contains a notice placed by the copyright holder or
138other authorized party saying it may be distributed under the terms of
139this Lesser General Public License (also called "this License").
140Each licensee is addressed as "you".
141
142 A "library" means a collection of software functions and/or data
143prepared so as to be conveniently linked with application programs
144(which use some of those functions and data) to form executables.
145
146 The "Library", below, refers to any such software library or work
147which has been distributed under these terms. A "work based on the
148Library" means either the Library or any derivative work under
149copyright law: that is to say, a work containing the Library or a
150portion of it, either verbatim or with modifications and/or translated
151straightforwardly into another language. (Hereinafter, translation is
152included without limitation in the term "modification".)
153
154 "Source code" for a work means the preferred form of the work for
155making modifications to it. For a library, complete source code means
156all the source code for all modules it contains, plus any associated
157interface definition files, plus the scripts used to control compilation
158and installation of the library.
159
160 Activities other than copying, distribution and modification are not
161covered by this License; they are outside its scope. The act of
162running a program using the Library is not restricted, and output from
163such a program is covered only if its contents constitute a work based
164on the Library (independent of the use of the Library in a tool for
165writing it). Whether that is true depends on what the Library does
166and what the program that uses the Library does.
167
168 1. You may copy and distribute verbatim copies of the Library's
169complete source code as you receive it, in any medium, provided that
170you conspicuously and appropriately publish on each copy an
171appropriate copyright notice and disclaimer of warranty; keep intact
172all the notices that refer to this License and to the absence of any
173warranty; and distribute a copy of this License along with the
174Library.
175
176 You may charge a fee for the physical act of transferring a copy,
177and you may at your option offer warranty protection in exchange for a
178fee.
179
180 2. You may modify your copy or copies of the Library or any portion
181of it, thus forming a work based on the Library, and copy and
182distribute such modifications or work under the terms of Section 1
183above, provided that you also meet all of these conditions:
184
185 a) The modified work must itself be a software library.
186
187 b) You must cause the files modified to carry prominent notices
188 stating that you changed the files and the date of any change.
189
190 c) You must cause the whole of the work to be licensed at no
191 charge to all third parties under the terms of this License.
192
193 d) If a facility in the modified Library refers to a function or a
194 table of data to be supplied by an application program that uses
195 the facility, other than as an argument passed when the facility
196 is invoked, then you must make a good faith effort to ensure that,
197 in the event an application does not supply such function or
198 table, the facility still operates, and performs whatever part of
199 its purpose remains meaningful.
200
201 (For example, a function in a library to compute square roots has
202 a purpose that is entirely well-defined independent of the
203 application. Therefore, Subsection 2d requires that any
204 application-supplied function or table used by this function must
205 be optional: if the application does not supply it, the square
206 root function must still compute square roots.)
207
208These requirements apply to the modified work as a whole. If
209identifiable sections of that work are not derived from the Library,
210and can be reasonably considered independent and separate works in
211themselves, then this License, and its terms, do not apply to those
212sections when you distribute them as separate works. But when you
213distribute the same sections as part of a whole which is a work based
214on the Library, the distribution of the whole must be on the terms of
215this License, whose permissions for other licensees extend to the
216entire whole, and thus to each and every part regardless of who wrote
217it.
218
219Thus, it is not the intent of this section to claim rights or contest
220your rights to work written entirely by you; rather, the intent is to
221exercise the right to control the distribution of derivative or
222collective works based on the Library.
223
224In addition, mere aggregation of another work not based on the Library
225with the Library (or with a work based on the Library) on a volume of
226a storage or distribution medium does not bring the other work under
227the scope of this License.
228
229Linking this library statically or dynamically with other modules is
230making a combined work based on this library. Thus, the terms and
231conditions of the GNU General Public License cover the whole combination.
232
233As a special exception, the copyright holders of this library give you
234permission to link this library with independent modules to produce an
235executable, regardless of the license terms of these independent modules,
236and to copy and distribute the resulting executable under terms of your
237choice, provided that you also meet, for each linked independent module,
238the terms and conditions of the license of that module. An independent
239module is a module which is not derived from or based on this library.
240If you modify this library, you may extend this exception to your version
241of the library, but you are not obliged to do so. If you do not wish to
242do so, delete this exception statement from your version.
243
244 3. You may opt to apply the terms of the ordinary GNU General Public
245License instead of this License to a given copy of the Library. To do
246this, you must alter all the notices that refer to this License, so
247that they refer to the ordinary GNU General Public License, version 2,
248instead of to this License. (If a newer version than version 2 of the
249ordinary GNU General Public License has appeared, then you can specify
250that version instead if you wish.) Do not make any other change in
251these notices.
252
253 Once this change is made in a given copy, it is irreversible for
254that copy, so the ordinary GNU General Public License applies to all
255subsequent copies and derivative works made from that copy.
256
257 This option is useful when you wish to copy part of the code of
258the Library into a program that is not a library.
259
260 4. You may copy and distribute the Library (or a portion or
261derivative of it, under Section 2) in object code or executable form
262under the terms of Sections 1 and 2 above provided that you accompany
263it with the complete corresponding machine-readable source code, which
264must be distributed under the terms of Sections 1 and 2 above on a
265medium customarily used for software interchange.
266
267 If distribution of object code is made by offering access to copy
268from a designated place, then offering equivalent access to copy the
269source code from the same place satisfies the requirement to
270distribute the source code, even though third parties are not
271compelled to copy the source along with the object code.
272
273 5. A program that contains no derivative of any portion of the
274Library, but is designed to work with the Library by being compiled or
275linked with it, is called a "work that uses the Library". Such a
276work, in isolation, is not a derivative work of the Library, and
277therefore falls outside the scope of this License.
278
279 However, linking a "work that uses the Library" with the Library
280creates an executable that is a derivative of the Library (because it
281contains portions of the Library), rather than a "work that uses the
282library". The executable is therefore covered by this License.
283Section 6 states terms for distribution of such executables.
284
285 When a "work that uses the Library" uses material from a header file
286that is part of the Library, the object code for the work may be a
287derivative work of the Library even though the source code is not.
288Whether this is true is especially significant if the work can be
289linked without the Library, or if the work is itself a library. The
290threshold for this to be true is not precisely defined by law.
291
292 If such an object file uses only numerical parameters, data
293structure layouts and accessors, and small macros and small inline
294functions (ten lines or less in length), then the use of the object
295file is unrestricted, regardless of whether it is legally a derivative
296work. (Executables containing this object code plus portions of the
297Library will still fall under Section 6.)
298
299 Otherwise, if the work is a derivative of the Library, you may
300distribute the object code for the work under the terms of Section 6.
301Any executables containing that work also fall under Section 6,
302whether or not they are linked directly with the Library itself.
303
304 6. As an exception to the Sections above, you may also combine or
305link a "work that uses the Library" with the Library to produce a
306work containing portions of the Library, and distribute that work
307under terms of your choice, provided that the terms permit
308modification of the work for the customer's own use and reverse
309engineering for debugging such modifications.
310
311 You must give prominent notice with each copy of the work that the
312Library is used in it and that the Library and its use are covered by
313this License. You must supply a copy of this License. If the work
314during execution displays copyright notices, you must include the
315copyright notice for the Library among them, as well as a reference
316directing the user to the copy of this License. Also, you must do one
317of these things:
318
319 a) Accompany the work with the complete corresponding
320 machine-readable source code for the Library including whatever
321 changes were used in the work (which must be distributed under
322 Sections 1 and 2 above); and, if the work is an executable linked
323 with the Library, with the complete machine-readable "work that
324 uses the Library", as object code and/or source code, so that the
325 user can modify the Library and then relink to produce a modified
326 executable containing the modified Library. (It is understood
327 that the user who changes the contents of definitions files in the
328 Library will not necessarily be able to recompile the application
329 to use the modified definitions.)
330
331 b) Use a suitable shared library mechanism for linking with the
332 Library. A suitable mechanism is one that (1) uses at run time a
333 copy of the library already present on the user's computer system,
334 rather than copying library functions into the executable, and (2)
335 will operate properly with a modified version of the library, if
336 the user installs one, as long as the modified version is
337 interface-compatible with the version that the work was made with.
338
339 c) Accompany the work with a written offer, valid for at
340 least three years, to give the same user the materials
341 specified in Subsection 6a, above, for a charge no more
342 than the cost of performing this distribution.
343
344 d) If distribution of the work is made by offering access to copy
345 from a designated place, offer equivalent access to copy the above
346 specified materials from the same place.
347
348 e) Verify that the user has already received a copy of these
349 materials or that you have already sent this user a copy.
350
351 For an executable, the required form of the "work that uses the
352Library" must include any data and utility programs needed for
353reproducing the executable from it. However, as a special exception,
354the materials to be distributed need not include anything that is
355normally distributed (in either source or binary form) with the major
356components (compiler, kernel, and so on) of the operating system on
357which the executable runs, unless that component itself accompanies
358the executable.
359
360 It may happen that this requirement contradicts the license
361restrictions of other proprietary libraries that do not normally
362accompany the operating system. Such a contradiction means you cannot
363use both them and the Library together in an executable that you
364distribute.
365
366 7. You may place library facilities that are a work based on the
367Library side-by-side in a single library together with other library
368facilities not covered by this License, and distribute such a combined
369library, provided that the separate distribution of the work based on
370the Library and of the other library facilities is otherwise
371permitted, and provided that you do these two things:
372
373 a) Accompany the combined library with a copy of the same work
374 based on the Library, uncombined with any other library
375 facilities. This must be distributed under the terms of the
376 Sections above.
377
378 b) Give prominent notice with the combined library of the fact
379 that part of it is a work based on the Library, and explaining
380 where to find the accompanying uncombined form of the same work.
381
382 8. You may not copy, modify, sublicense, link with, or distribute
383the Library except as expressly provided under this License. Any
384attempt otherwise to copy, modify, sublicense, link with, or
385distribute the Library is void, and will automatically terminate your
386rights under this License. However, parties who have received copies,
387or rights, from you under this License will not have their licenses
388terminated so long as such parties remain in full compliance.
389
390 9. You are not required to accept this License, since you have not
391signed it. However, nothing else grants you permission to modify or
392distribute the Library or its derivative works. These actions are
393prohibited by law if you do not accept this License. Therefore, by
394modifying or distributing the Library (or any work based on the
395Library), you indicate your acceptance of this License to do so, and
396all its terms and conditions for copying, distributing or modifying
397the Library or works based on it.
398
399 10. Each time you redistribute the Library (or any work based on the
400Library), the recipient automatically receives a license from the
401original licensor to copy, distribute, link with or modify the Library
402subject to these terms and conditions. You may not impose any further
403restrictions on the recipients' exercise of the rights granted herein.
404You are not responsible for enforcing compliance by third parties with
405this License.
406
407 11. If, as a consequence of a court judgment or allegation of patent
408infringement or for any other reason (not limited to patent issues),
409conditions are imposed on you (whether by court order, agreement or
410otherwise) that contradict the conditions of this License, they do not
411excuse you from the conditions of this License. If you cannot
412distribute so as to satisfy simultaneously your obligations under this
413License and any other pertinent obligations, then as a consequence you
414may not distribute the Library at all. For example, if a patent
415license would not permit royalty-free redistribution of the Library by
416all those who receive copies directly or indirectly through you, then
417the only way you could satisfy both it and this License would be to
418refrain entirely from distribution of the Library.
419
420If any portion of this section is held invalid or unenforceable under any
421particular circumstance, the balance of the section is intended to apply,
422and the section as a whole is intended to apply in other circumstances.
423
424It is not the purpose of this section to induce you to infringe any
425patents or other property right claims or to contest validity of any
426such claims; this section has the sole purpose of protecting the
427integrity of the free software distribution system which is
428implemented by public license practices. Many people have made
429generous contributions to the wide range of software distributed
430through that system in reliance on consistent application of that
431system; it is up to the author/donor to decide if he or she is willing
432to distribute software through any other system and a licensee cannot
433impose that choice.
434
435This section is intended to make thoroughly clear what is believed to
436be a consequence of the rest of this License.
437
438 12. If the distribution and/or use of the Library is restricted in
439certain countries either by patents or by copyrighted interfaces, the
440original copyright holder who places the Library under this License may add
441an explicit geographical distribution limitation excluding those countries,
442so that distribution is permitted only in or among countries not thus
443excluded. In such case, this License incorporates the limitation as if
444written in the body of this License.
445
446 13. The Free Software Foundation may publish revised and/or new
447versions of the Lesser General Public License from time to time.
448Such new versions will be similar in spirit to the present version,
449but may differ in detail to address new problems or concerns.
450
451Each version is given a distinguishing version number. If the Library
452specifies a version number of this License which applies to it and
453"any later version", you have the option of following the terms and
454conditions either of that version or of any later version published by
455the Free Software Foundation. If the Library does not specify a
456license version number, you may choose any version ever published by
457the Free Software Foundation.
458
459 14. If you wish to incorporate parts of the Library into other free
460programs whose distribution conditions are incompatible with these,
461write to the author to ask for permission. For software which is
462copyrighted by the Free Software Foundation, write to the Free
463Software Foundation; we sometimes make exceptions for this. Our
464decision will be guided by the two goals of preserving the free status
465of all derivatives of our free software and of promoting the sharing
466and reuse of software generally.
467
468 NO WARRANTY
469
470 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
471WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
472EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
473OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
474KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
475IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
476PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
477LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
478THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
479
480 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
481WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
482AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
483FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
484CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
485LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
486RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
487FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
488SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
489DAMAGES.
490
491 END OF TERMS AND CONDITIONS
492
493 How to Apply These Terms to Your New Libraries
494
495 If you develop a new library, and you want it to be of the greatest
496possible use to the public, we recommend making it free software that
497everyone can redistribute and change. You can do so by permitting
498redistribution under these terms (or, alternatively, under the terms of the
499ordinary General Public License).
500
501 To apply these terms, attach the following notices to the library. It is
502safest to attach them to the start of each source file to most effectively
503convey the exclusion of warranty; and each file should have at least the
504"copyright" line and a pointer to where the full notice is found.
505
506 <one line to give the library's name and a brief idea of what it does.>
507 Copyright (C) <year> <name of author>
508
509 This library is free software; you can redistribute it and/or
510 modify it under the terms of the GNU Lesser General Public
511 License as published by the Free Software Foundation; either
512 version 2.1 of the License, or (at your option) any later version.
513
514 This library is distributed in the hope that it will be useful,
515 but WITHOUT ANY WARRANTY; without even the implied warranty of
516 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
517 Lesser General Public License for more details.
518
519 You should have received a copy of the GNU Lesser General Public
520 License along with this library; if not, write to the Free Software
521 Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
522
523Also add information on how to contact you by electronic and paper mail.
524
525You should also get your employer (if you work as a programmer) or your
526school, if any, to sign a "copyright disclaimer" for the library, if
527necessary. Here is a sample; alter the names:
528
529 Yoyodyne, Inc., hereby disclaims all copyright interest in the
530 library `Frob' (a library for tweaking knobs) written by James Random Hacker.
531
532 <signature of Ty Coon>, 1 April 1990
533 Ty Coon, President of Vice
534
535That's all there is to it!
536
537
diff --git a/legacy/eio/INSTALL b/legacy/eio/INSTALL
deleted file mode 100644
index 7d1c323bea..0000000000
--- a/legacy/eio/INSTALL
+++ /dev/null
@@ -1,365 +0,0 @@
1Installation Instructions
2*************************
3
4Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
52006, 2007, 2008, 2009 Free Software Foundation, Inc.
6
7 Copying and distribution of this file, with or without modification,
8are permitted in any medium without royalty provided the copyright
9notice and this notice are preserved. This file is offered as-is,
10without warranty of any kind.
11
12Basic Installation
13==================
14
15 Briefly, the shell commands `./configure; make; make install' should
16configure, build, and install this package. The following
17more-detailed instructions are generic; see the `README' file for
18instructions specific to this package. Some packages provide this
19`INSTALL' file but do not implement all of the features documented
20below. The lack of an optional feature in a given package is not
21necessarily a bug. More recommendations for GNU packages can be found
22in *note Makefile Conventions: (standards)Makefile Conventions.
23
24 The `configure' shell script attempts to guess correct values for
25various system-dependent variables used during compilation. It uses
26those values to create a `Makefile' in each directory of the package.
27It may also create one or more `.h' files containing system-dependent
28definitions. Finally, it creates a shell script `config.status' that
29you can run in the future to recreate the current configuration, and a
30file `config.log' containing compiler output (useful mainly for
31debugging `configure').
32
33 It can also use an optional file (typically called `config.cache'
34and enabled with `--cache-file=config.cache' or simply `-C') that saves
35the results of its tests to speed up reconfiguring. Caching is
36disabled by default to prevent problems with accidental use of stale
37cache files.
38
39 If you need to do unusual things to compile the package, please try
40to figure out how `configure' could check whether to do them, and mail
41diffs or instructions to the address given in the `README' so they can
42be considered for the next release. If you are using the cache, and at
43some point `config.cache' contains results you don't want to keep, you
44may remove or edit it.
45
46 The file `configure.ac' (or `configure.in') is used to create
47`configure' by a program called `autoconf'. You need `configure.ac' if
48you want to change it or regenerate `configure' using a newer version
49of `autoconf'.
50
51 The simplest way to compile this package is:
52
53 1. `cd' to the directory containing the package's source code and type
54 `./configure' to configure the package for your system.
55
56 Running `configure' might take a while. While running, it prints
57 some messages telling which features it is checking for.
58
59 2. Type `make' to compile the package.
60
61 3. Optionally, type `make check' to run any self-tests that come with
62 the package, generally using the just-built uninstalled binaries.
63
64 4. Type `make install' to install the programs and any data files and
65 documentation. When installing into a prefix owned by root, it is
66 recommended that the package be configured and built as a regular
67 user, and only the `make install' phase executed with root
68 privileges.
69
70 5. Optionally, type `make installcheck' to repeat any self-tests, but
71 this time using the binaries in their final installed location.
72 This target does not install anything. Running this target as a
73 regular user, particularly if the prior `make install' required
74 root privileges, verifies that the installation completed
75 correctly.
76
77 6. You can remove the program binaries and object files from the
78 source code directory by typing `make clean'. To also remove the
79 files that `configure' created (so you can compile the package for
80 a different kind of computer), type `make distclean'. There is
81 also a `make maintainer-clean' target, but that is intended mainly
82 for the package's developers. If you use it, you may have to get
83 all sorts of other programs in order to regenerate files that came
84 with the distribution.
85
86 7. Often, you can also type `make uninstall' to remove the installed
87 files again. In practice, not all packages have tested that
88 uninstallation works correctly, even though it is required by the
89 GNU Coding Standards.
90
91 8. Some packages, particularly those that use Automake, provide `make
92 distcheck', which can by used by developers to test that all other
93 targets like `make install' and `make uninstall' work correctly.
94 This target is generally not run by end users.
95
96Compilers and Options
97=====================
98
99 Some systems require unusual options for compilation or linking that
100the `configure' script does not know about. Run `./configure --help'
101for details on some of the pertinent environment variables.
102
103 You can give `configure' initial values for configuration parameters
104by setting variables in the command line or in the environment. Here
105is an example:
106
107 ./configure CC=c99 CFLAGS=-g LIBS=-lposix
108
109 *Note Defining Variables::, for more details.
110
111Compiling For Multiple Architectures
112====================================
113
114 You can compile the package for more than one kind of computer at the
115same time, by placing the object files for each architecture in their
116own directory. To do this, you can use GNU `make'. `cd' to the
117directory where you want the object files and executables to go and run
118the `configure' script. `configure' automatically checks for the
119source code in the directory that `configure' is in and in `..'. This
120is known as a "VPATH" build.
121
122 With a non-GNU `make', it is safer to compile the package for one
123architecture at a time in the source code directory. After you have
124installed the package for one architecture, use `make distclean' before
125reconfiguring for another architecture.
126
127 On MacOS X 10.5 and later systems, you can create libraries and
128executables that work on multiple system types--known as "fat" or
129"universal" binaries--by specifying multiple `-arch' options to the
130compiler but only a single `-arch' option to the preprocessor. Like
131this:
132
133 ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
134 CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
135 CPP="gcc -E" CXXCPP="g++ -E"
136
137 This is not guaranteed to produce working output in all cases, you
138may have to build one architecture at a time and combine the results
139using the `lipo' tool if you have problems.
140
141Installation Names
142==================
143
144 By default, `make install' installs the package's commands under
145`/usr/local/bin', include files under `/usr/local/include', etc. You
146can specify an installation prefix other than `/usr/local' by giving
147`configure' the option `--prefix=PREFIX', where PREFIX must be an
148absolute file name.
149
150 You can specify separate installation prefixes for
151architecture-specific files and architecture-independent files. If you
152pass the option `--exec-prefix=PREFIX' to `configure', the package uses
153PREFIX as the prefix for installing programs and libraries.
154Documentation and other data files still use the regular prefix.
155
156 In addition, if you use an unusual directory layout you can give
157options like `--bindir=DIR' to specify different values for particular
158kinds of files. Run `configure --help' for a list of the directories
159you can set and what kinds of files go in them. In general, the
160default for these options is expressed in terms of `${prefix}', so that
161specifying just `--prefix' will affect all of the other directory
162specifications that were not explicitly provided.
163
164 The most portable way to affect installation locations is to pass the
165correct locations to `configure'; however, many packages provide one or
166both of the following shortcuts of passing variable assignments to the
167`make install' command line to change installation locations without
168having to reconfigure or recompile.
169
170 The first method involves providing an override variable for each
171affected directory. For example, `make install
172prefix=/alternate/directory' will choose an alternate location for all
173directory configuration variables that were expressed in terms of
174`${prefix}'. Any directories that were specified during `configure',
175but not in terms of `${prefix}', must each be overridden at install
176time for the entire installation to be relocated. The approach of
177makefile variable overrides for each directory variable is required by
178the GNU Coding Standards, and ideally causes no recompilation.
179However, some platforms have known limitations with the semantics of
180shared libraries that end up requiring recompilation when using this
181method, particularly noticeable in packages that use GNU Libtool.
182
183 The second method involves providing the `DESTDIR' variable. For
184example, `make install DESTDIR=/alternate/directory' will prepend
185`/alternate/directory' before all installation names. The approach of
186`DESTDIR' overrides is not required by the GNU Coding Standards, and
187does not work on platforms that have drive letters. On the other hand,
188it does better at avoiding recompilation issues, and works well even
189when some directory options were not specified in terms of `${prefix}'
190at `configure' time.
191
192Optional Features
193=================
194
195 If the package supports it, you can cause programs to be installed
196with an extra prefix or suffix on their names by giving `configure' the
197option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
198
199 Some packages pay attention to `--enable-FEATURE' options to
200`configure', where FEATURE indicates an optional part of the package.
201They may also pay attention to `--with-PACKAGE' options, where PACKAGE
202is something like `gnu-as' or `x' (for the X Window System). The
203`README' should mention any `--enable-' and `--with-' options that the
204package recognizes.
205
206 For packages that use the X Window System, `configure' can usually
207find the X include and library files automatically, but if it doesn't,
208you can use the `configure' options `--x-includes=DIR' and
209`--x-libraries=DIR' to specify their locations.
210
211 Some packages offer the ability to configure how verbose the
212execution of `make' will be. For these packages, running `./configure
213--enable-silent-rules' sets the default to minimal output, which can be
214overridden with `make V=1'; while running `./configure
215--disable-silent-rules' sets the default to verbose, which can be
216overridden with `make V=0'.
217
218Particular systems
219==================
220
221 On HP-UX, the default C compiler is not ANSI C compatible. If GNU
222CC is not installed, it is recommended to use the following options in
223order to use an ANSI C compiler:
224
225 ./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
226
227and if that doesn't work, install pre-built binaries of GCC for HP-UX.
228
229 On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
230parse its `<wchar.h>' header file. The option `-nodtk' can be used as
231a workaround. If GNU CC is not installed, it is therefore recommended
232to try
233
234 ./configure CC="cc"
235
236and if that doesn't work, try
237
238 ./configure CC="cc -nodtk"
239
240 On Solaris, don't put `/usr/ucb' early in your `PATH'. This
241directory contains several dysfunctional programs; working variants of
242these programs are available in `/usr/bin'. So, if you need `/usr/ucb'
243in your `PATH', put it _after_ `/usr/bin'.
244
245 On Haiku, software installed for all users goes in `/boot/common',
246not `/usr/local'. It is recommended to use the following options:
247
248 ./configure --prefix=/boot/common
249
250Specifying the System Type
251==========================
252
253 There may be some features `configure' cannot figure out
254automatically, but needs to determine by the type of machine the package
255will run on. Usually, assuming the package is built to be run on the
256_same_ architectures, `configure' can figure that out, but if it prints
257a message saying it cannot guess the machine type, give it the
258`--build=TYPE' option. TYPE can either be a short name for the system
259type, such as `sun4', or a canonical name which has the form:
260
261 CPU-COMPANY-SYSTEM
262
263where SYSTEM can have one of these forms:
264
265 OS
266 KERNEL-OS
267
268 See the file `config.sub' for the possible values of each field. If
269`config.sub' isn't included in this package, then this package doesn't
270need to know the machine type.
271
272 If you are _building_ compiler tools for cross-compiling, you should
273use the option `--target=TYPE' to select the type of system they will
274produce code for.
275
276 If you want to _use_ a cross compiler, that generates code for a
277platform different from the build platform, you should specify the
278"host" platform (i.e., that on which the generated programs will
279eventually be run) with `--host=TYPE'.
280
281Sharing Defaults
282================
283
284 If you want to set default values for `configure' scripts to share,
285you can create a site shell script called `config.site' that gives
286default values for variables like `CC', `cache_file', and `prefix'.
287`configure' looks for `PREFIX/share/config.site' if it exists, then
288`PREFIX/etc/config.site' if it exists. Or, you can set the
289`CONFIG_SITE' environment variable to the location of the site script.
290A warning: not all `configure' scripts look for a site script.
291
292Defining Variables
293==================
294
295 Variables not defined in a site shell script can be set in the
296environment passed to `configure'. However, some packages may run
297configure again during the build, and the customized values of these
298variables may be lost. In order to avoid this problem, you should set
299them in the `configure' command line, using `VAR=value'. For example:
300
301 ./configure CC=/usr/local2/bin/gcc
302
303causes the specified `gcc' to be used as the C compiler (unless it is
304overridden in the site shell script).
305
306Unfortunately, this technique does not work for `CONFIG_SHELL' due to
307an Autoconf bug. Until the bug is fixed you can use this workaround:
308
309 CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
310
311`configure' Invocation
312======================
313
314 `configure' recognizes the following options to control how it
315operates.
316
317`--help'
318`-h'
319 Print a summary of all of the options to `configure', and exit.
320
321`--help=short'
322`--help=recursive'
323 Print a summary of the options unique to this package's
324 `configure', and exit. The `short' variant lists options used
325 only in the top level, while the `recursive' variant lists options
326 also present in any nested packages.
327
328`--version'
329`-V'
330 Print the version of Autoconf used to generate the `configure'
331 script, and exit.
332
333`--cache-file=FILE'
334 Enable the cache: use and save the results of the tests in FILE,
335 traditionally `config.cache'. FILE defaults to `/dev/null' to
336 disable caching.
337
338`--config-cache'
339`-C'
340 Alias for `--cache-file=config.cache'.
341
342`--quiet'
343`--silent'
344`-q'
345 Do not print messages saying which checks are being made. To
346 suppress all normal output, redirect it to `/dev/null' (any error
347 messages will still be shown).
348
349`--srcdir=DIR'
350 Look for the package's source code in directory DIR. Usually
351 `configure' can determine that directory automatically.
352
353`--prefix=DIR'
354 Use DIR as the installation prefix. *note Installation Names::
355 for more details, including other options available for fine-tuning
356 the installation locations.
357
358`--no-create'
359`-n'
360 Run the configure checks, but stop before creating any output
361 files.
362
363`configure' also accepts some other, not widely useful, options. Run
364`configure --help' for more details.
365
diff --git a/legacy/eio/Makefile.am b/legacy/eio/Makefile.am
deleted file mode 100644
index 2fad093c5e..0000000000
--- a/legacy/eio/Makefile.am
+++ /dev/null
@@ -1,53 +0,0 @@
1ACLOCAL_AMFLAGS = -I m4
2
3SUBDIRS = src doc
4
5MAINTAINERCLEANFILES = \
6ABOUT-NLS \
7Makefile.in \
8aclocal.m4 \
9compile \
10config.cache-env \
11config.guess \
12config.h.in \
13config.h.in~ \
14config.rpath \
15config.sub \
16configure \
17depcomp \
18install-sh \
19ltmain.sh \
20missing \
21mkinstalldirs \
22$(PACKAGE_TARNAME)-$(PACKAGE_VERSION).tar.gz \
23$(PACKAGE_TARNAME)-$(PACKAGE_VERSION).tar.bz2 \
24$(PACKAGE_TARNAME)-$(PACKAGE_VERSION)-doc.tar.bz2 \
25m4/libtool.m4 \
26m4/lt~obsolete.m4 \
27m4/ltoptions.m4 \
28m4/ltsugar.m4 \
29m4/ltversion.m4
30
31EXTRA_DIST = \
32AUTHORS \
33COPYING \
34README \
35autogen.sh \
36eio.spec \
37eio.pc.in \
38m4/ac_attribute.m4 \
39m4/efl_doxygen.m4 \
40m4/efl_path_max.m4 \
41m4/efl_threads.m4 \
42m4/eio_check_options.m4
43
44pkgconfigdir = $(libdir)/pkgconfig
45pkgconfig_DATA = eio.pc
46
47.PHONY: doc coverage benchmark
48
49# Documentation
50
51doc:
52 @echo "entering doc/"
53 make -C doc doc
diff --git a/legacy/eio/TODO b/legacy/eio/TODO
deleted file mode 100644
index 01c6f05a5c..0000000000
--- a/legacy/eio/TODO
+++ /dev/null
@@ -1 +0,0 @@
1 * Fix file monitoring on Windows when we pass a file and not just a directory \ No newline at end of file
diff --git a/legacy/eio/autogen.sh b/legacy/eio/autogen.sh
deleted file mode 100755
index 00116eaf80..0000000000
--- a/legacy/eio/autogen.sh
+++ /dev/null
@@ -1,39 +0,0 @@
1#!/bin/sh
2
3rm -rf autom4te.cache
4rm -f aclocal.m4 ltmain.sh
5
6touch README
7touch ABOUT-NLS
8
9echo "Running aclocal..." ; aclocal $ACLOCAL_FLAGS -I m4 || exit 1
10echo "Running autoheader..." ; autoheader || exit 1
11echo "Running autoconf..." ; autoconf || exit 1
12echo "Running libtoolize..." ; (libtoolize --copy --automake || glibtoolize --automake) || exit 1
13echo "Running automake..." ; automake --add-missing --copy --gnu || exit 1
14
15W=0
16
17rm -f config.cache-env.tmp
18echo "OLD_PARM=\"$@\"" >> config.cache-env.tmp
19echo "OLD_CFLAGS=\"$CFLAGS\"" >> config.cache-env.tmp
20echo "OLD_PATH=\"$PATH\"" >> config.cache-env.tmp
21echo "OLD_PKG_CONFIG_PATH=\"$PKG_CONFIG_PATH\"" >> config.cache-env.tmp
22echo "OLD_LDFLAGS=\"$LDFLAGS\"" >> config.cache-env.tmp
23
24cmp config.cache-env.tmp config.cache-env >> /dev/null
25if [ $? -ne 0 ]; then
26 W=1;
27fi
28
29if [ $W -ne 0 ]; then
30 echo "Cleaning configure cache...";
31 rm -f config.cache config.cache-env
32 mv config.cache-env.tmp config.cache-env
33else
34 rm -f config.cache-env.tmp
35fi
36
37if [ -z "$NOCONFIGURE" ]; then
38 ./configure -C "$@"
39fi
diff --git a/legacy/eio/configure.ac b/legacy/eio/configure.ac
deleted file mode 100644
index 610449e338..0000000000
--- a/legacy/eio/configure.ac
+++ /dev/null
@@ -1,281 +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-09])
12dnl m4_define([v_rel], [-release relname])
13##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
14m4_ifdef([v_rev], [m4_define([v_ver], [v_maj.v_min.v_mic.v_rev])],
15[m4_define([v_ver], [v_maj.v_min.v_mic])])
16m4_define([lt_rev], m4_eval(v_maj + v_min))
17m4_define([lt_cur], v_mic)
18m4_define([lt_age], v_min)
19##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
20##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
21
22AC_INIT([eio], [v_ver], [enlightenment-devel@lists.sourceforge.net])
23AC_PREREQ([2.52])
24AC_CONFIG_SRCDIR([configure.ac])
25AC_CONFIG_MACRO_DIR([m4])
26
27AC_CONFIG_HEADERS([config.h])
28AH_TOP([
29#ifndef EFL_CONFIG_H__
30#define EFL_CONFIG_H__
31])
32AH_BOTTOM([
33#endif /* EFL_CONFIG_H__ */
34])
35
36AM_INIT_AUTOMAKE([1.6 dist-bzip2])
37m4_ifdef([AM_SILENT_RULES], [AM_SILENT_RULES([yes])])
38
39AC_GNU_SOURCE
40AC_SYS_LARGEFILE
41
42AC_LIBTOOL_WIN32_DLL
43define([AC_LIBTOOL_LANG_CXX_CONFIG], [:])dnl
44define([AC_LIBTOOL_LANG_F77_CONFIG], [:])dnl
45AC_PROG_LIBTOOL
46
47##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
48##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
49m4_ifdef([v_rev], , [m4_define([v_rev], [0])])
50m4_ifdef([v_rel], , [m4_define([v_rel], [])])
51AC_DEFINE_UNQUOTED(VMAJ, [v_maj], [Major version])
52AC_DEFINE_UNQUOTED(VMIN, [v_min], [Minor version])
53AC_DEFINE_UNQUOTED(VMIC, [v_mic], [Micro version])
54AC_DEFINE_UNQUOTED(VREV, [v_rev], [Revison])
55version_info="lt_rev:lt_cur:lt_age"
56release_info="v_rel"
57AC_SUBST([version_info])
58AC_SUBST([release_info])
59##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
60##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
61VMAJ=v_maj
62AC_SUBST([VMAJ])
63
64
65### Needed information
66
67AC_CANONICAL_BUILD
68AC_CANONICAL_HOST
69
70
71### Default options with respect to host
72
73want_inotify="no"
74want_notify_win32="no"
75
76case "$host_os" in
77 mingw*)
78 want_notify_win32="yes"
79 ;;
80 *)
81 want_inotify="yes"
82 ;;
83esac
84
85
86### Checks for programs
87
88AC_PROG_CC
89
90# pkg-config
91PKG_PROG_PKG_CONFIG
92
93# Check whether pkg-config supports Requires.private
94if $PKG_CONFIG --atleast-pkgconfig-version 0.22; then
95 pkgconfig_requires_private="Requires.private"
96else
97 pkgconfig_requires_private="Requires"
98fi
99AC_SUBST([pkgconfig_requires_private])
100
101# doxygen program for documentation building
102
103EFL_CHECK_DOXYGEN([build_doc="yes"], [build_doc="no"])
104
105
106### Checks for libraries
107
108case "$host_os" in
109 mingw*)
110 PKG_CHECK_EXISTS([evil >= 1.6.99])
111 AC_DEFINE([HAVE_EVIL], [1], [Set to 1 if evil package is installed])
112 requirements_eio="${requirements_eio} evil >= 1.6.99"
113 ;;
114esac
115
116requirements_eio="${requirements_eio} eet >= 1.6.99 eina >= 1.6.99 ecore >= 1.6.99"
117AC_SUBST([requirements_eio])
118
119PKG_CHECK_MODULES([EIO], [${requirements_eio}])
120
121
122### Checks for header files
123
124AC_HEADER_DIRENT
125AC_HEADER_TIME
126AC_CHECK_HEADERS([unistd.h libgen.h grp.h features.h pwd.h])
127
128EFL_CHECK_THREADS(
129 [
130 if test "x${_efl_have_posix_threads}" = "xyes" ; then
131 have_threads="POSIX"
132 else
133 if test "x${_efl_have_win32_threads}" = "xyes" ; then
134 have_threads="Win32"
135 else
136 have_threads="no"
137 fi
138 fi
139 ],
140 [have_threads="no"])
141
142if test "x${have_threads}" = "xno" ; then
143 AC_MSG_ERROR([Threads not supported. Be sure to have pthread on non Windows OS])
144fi
145
146EFL_CHECK_PATH_MAX
147
148### Checks for types
149
150### Checks for structures
151
152### Checks for compiler characteristics
153AC_C_BIGENDIAN
154AC_C_INLINE
155AC_C___ATTRIBUTE__
156AM_PROG_CC_C_O
157
158### Checks for linker characteristics
159
160### Checks for library functions
161AC_FUNC_ALLOCA
162AC_CHECK_FUNCS([fchmod chown getpwnam getgrnam])
163
164### Check for splice system call
165
166AC_MSG_CHECKING([whether to use splice for file copy])
167AC_TRY_LINK(
168 [
169#if defined(HAVE_UNISTD_H)
170# include <unistd.h>
171#endif
172#include <fcntl.h>
173 ],
174 [
175long ret = splice(0,0,1,0,400,0);
176 ],
177 [have_splice="yes"],
178 [have_splice="no"])
179AC_MSG_RESULT([${have_splice}])
180
181if test "x${have_splice}" = "xyes" ; then
182 AC_DEFINE([HAVE_SPLICE], [1], [Define to mention that splice syscall is supported])
183fi
184
185# Check for lstat
186
187AC_MSG_CHECKING([whether lstat is available])
188AC_TRY_LINK(
189 [
190#include <sys/types.h>
191#include <sys/stat.h>
192#if defined(HAVE_UNISTD_H)
193# include <unistd.h>
194#endif
195 ],
196 [
197struct stat st;
198lstat("/tmp", &st);
199 ],
200 [have_lstat="yes"],
201 [have_lstat="no"])
202AC_MSG_RESULT([${have_lstat}])
203
204if test "x${have_lstat}" = "xyes" ; then
205 AC_DEFINE([HAVE_LSTAT], [1], [Define to mention that lstat syscall is supported])
206fi
207
208# extended attribute
209
210AC_MSG_CHECKING([for extended attributes])
211
212AC_COMPILE_IFELSE(
213 [AC_LANG_PROGRAM(
214 [[
215#include <stdlib.h>
216#include <sys/types.h>
217#include <sys/xattr.h>
218 ]],
219 [[
220size_t tmp = listxattr("/", NULL, 0);
221tmp = getxattr("/", "user.ethumb.md5", NULL, 0);
222setxattr("/", "user.ethumb.md5", NULL, 0, 0);
223 ]])],
224 [
225 AC_DEFINE([HAVE_XATTR], [1], [Define to 1 if you have the `listxattr', `setxattr' and `getxattr' functions.])
226 have_xattr="yes"
227 ],
228 [have_xattr="no"])
229
230AC_MSG_RESULT([${have_xattr}])
231
232# Check for inotify specificity
233have_inotify="no"
234have_notify_win32="no"
235EIO_CHECK_INOTIFY([${want_inotify}], [have_inotify="yes"], [have_inotify="no"])
236EIO_CHECK_NOTIFY_WIN32([${want_notify_win32}], [have_notify_win32="yes"], [have_notify_win32="no"])
237
238AM_CONDITIONAL([EIO_HAVE_INOTIFY], [test "x$have_inotify" = "xyes"])
239AM_CONDITIONAL([EIO_HAVE_WINCHANGE], [test "x$have_notify_win32" = "xyes"])
240EFL_CHECK_BUILD_EXAMPLES([enable_build_examples="yes"], [enable_build_examples="no"])
241EFL_CHECK_INSTALL_EXAMPLES([enable_install_examples="yes"], [enable_install_examples="no"])
242
243
244AC_OUTPUT([
245eio.pc
246eio.spec
247Makefile
248doc/Makefile
249doc/eio.dox
250doc/Doxyfile
251src/Makefile
252src/lib/Makefile
253src/examples/Makefile
254])
255
256echo
257echo
258echo "------------------------------------------------------------------------"
259echo "$PACKAGE_NAME $PACKAGE_VERSION"
260echo "------------------------------------------------------------------------"
261echo
262echo
263echo
264echo "Configuration Options Summary:"
265echo
266echo " Thread Support.......: ${have_threads}"
267echo " Inotify..............: ${have_inotify}"
268echo " Windows notification.: ${have_notify_win32}"
269echo
270echo " Documentation........: ${build_doc}"
271echo " Examples...............: ${enable_build_examples}"
272echo " Examples installed.....: ${enable_install_examples}"
273echo
274echo "Compilation............: make (or gmake)"
275echo " CPPFLAGS.............: $CPPFLAGS"
276echo " CFLAGS...............: $CFLAGS"
277echo " LDFLAGS..............: $LDFLAGS"
278echo
279echo "Installation...........: make install (as root if needed, with 'su' or 'sudo')"
280echo " prefix...............: $prefix"
281echo
diff --git a/legacy/eio/doc/Doxyfile.in b/legacy/eio/doc/Doxyfile.in
deleted file mode 100644
index 5045cc5d86..0000000000
--- a/legacy/eio/doc/Doxyfile.in
+++ /dev/null
@@ -1,1613 +0,0 @@
1# Doxyfile 1.7.1
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 = Eio
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# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
37# base path where the generated documentation will be put.
38# If a relative path is entered, it will be relative to the location
39# where doxygen was started. If left blank the current directory will be used.
40
41OUTPUT_DIRECTORY = .
42
43# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
44# 4096 sub-directories (in 2 levels) under the output directory of each output
45# format and will distribute the generated files over these directories.
46# Enabling this option can be useful when feeding doxygen a huge amount of
47# source files, where putting all generated files in the same directory would
48# otherwise cause performance problems for the file system.
49
50CREATE_SUBDIRS = NO
51
52# The OUTPUT_LANGUAGE tag is used to specify the language in which all
53# documentation generated by doxygen is written. Doxygen will use this
54# information to generate all constant output in the proper language.
55# The default language is English, other supported languages are:
56# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,
57# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German,
58# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English
59# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian,
60# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrilic, Slovak,
61# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.
62
63OUTPUT_LANGUAGE = English
64
65# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
66# include brief member descriptions after the members that are listed in
67# the file and class documentation (similar to JavaDoc).
68# Set to NO to disable this.
69
70BRIEF_MEMBER_DESC = YES
71
72# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
73# the brief description of a member or function before the detailed description.
74# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
75# brief descriptions will be completely suppressed.
76
77REPEAT_BRIEF = YES
78
79# This tag implements a quasi-intelligent brief description abbreviator
80# that is used to form the text in various listings. Each string
81# in this list, if found as the leading text of the brief description, will be
82# stripped from the text and the result after processing the whole list, is
83# used as the annotated text. Otherwise, the brief description is used as-is.
84# If left blank, the following values are used ("$name" is automatically
85# replaced with the name of the entity): "The $name class" "The $name widget"
86# "The $name file" "is" "provides" "specifies" "contains"
87# "represents" "a" "an" "the"
88
89ABBREVIATE_BRIEF =
90
91# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
92# Doxygen will generate a detailed section even if there is only a brief
93# description.
94
95ALWAYS_DETAILED_SEC = NO
96
97# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
98# inherited members of a class in the documentation of that class as if those
99# members were ordinary class members. Constructors, destructors and assignment
100# operators of the base classes will not be shown.
101
102INLINE_INHERITED_MEMB = NO
103
104# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
105# path before files name in the file list and in the header files. If set
106# to NO the shortest path that makes the file name unique will be used.
107
108FULL_PATH_NAMES = NO
109
110# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
111# can be used to strip a user-defined part of the path. Stripping is
112# only done if one of the specified strings matches the left-hand part of
113# the path. The tag can be used to show relative paths in the file list.
114# If left blank the directory from which doxygen is run is used as the
115# path to strip.
116
117STRIP_FROM_PATH =
118
119# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
120# the path mentioned in the documentation of a class, which tells
121# the reader which header file to include in order to use a class.
122# If left blank only the name of the header file containing the class
123# definition is used. Otherwise one should specify the include paths that
124# are normally passed to the compiler using the -I flag.
125
126STRIP_FROM_INC_PATH =
127
128# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
129# (but less readable) file names. This can be useful is your file systems
130# doesn't support long names like on DOS, Mac, or CD-ROM.
131
132SHORT_NAMES = NO
133
134# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
135# will interpret the first line (until the first dot) of a JavaDoc-style
136# comment as the brief description. If set to NO, the JavaDoc
137# comments will behave just like regular Qt-style comments
138# (thus requiring an explicit @brief command for a brief description.)
139
140JAVADOC_AUTOBRIEF = NO
141
142# If the QT_AUTOBRIEF tag is set to YES then Doxygen will
143# interpret the first line (until the first dot) of a Qt-style
144# comment as the brief description. If set to NO, the comments
145# will behave just like regular Qt-style comments (thus requiring
146# an explicit \brief command for a brief description.)
147
148QT_AUTOBRIEF = NO
149
150# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
151# treat a multi-line C++ special comment block (i.e. a block of //! or ///
152# comments) as a brief description. This used to be the default behaviour.
153# The new default is to treat a multi-line C++ comment block as a detailed
154# description. Set this tag to YES if you prefer the old behaviour instead.
155
156MULTILINE_CPP_IS_BRIEF = NO
157
158# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
159# member inherits the documentation from any documented member that it
160# re-implements.
161
162INHERIT_DOCS = YES
163
164# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
165# a new page for each member. If set to NO, the documentation of a member will
166# be part of the file/class/namespace that contains it.
167
168SEPARATE_MEMBER_PAGES = NO
169
170# The TAB_SIZE tag can be used to set the number of spaces in a tab.
171# Doxygen uses this value to replace tabs by spaces in code fragments.
172
173TAB_SIZE = 8
174
175# This tag can be used to specify a number of aliases that acts
176# as commands in the documentation. An alias has the form "name=value".
177# For example adding "sideeffect=\par Side Effects:\n" will allow you to
178# put the command \sideeffect (or @sideeffect) in the documentation, which
179# will result in a user-defined paragraph with heading "Side Effects:".
180# You can put \n's in the value part of an alias to insert newlines.
181
182ALIASES =
183
184# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
185# sources only. Doxygen will then generate output that is more tailored for C.
186# For instance, some of the names that are used will be different. The list
187# of all members will be omitted, etc.
188
189OPTIMIZE_OUTPUT_FOR_C = YES
190
191# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java
192# sources only. Doxygen will then generate output that is more tailored for
193# Java. For instance, namespaces will be presented as packages, qualified
194# scopes will look different, etc.
195
196OPTIMIZE_OUTPUT_JAVA = NO
197
198# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
199# sources only. Doxygen will then generate output that is more tailored for
200# Fortran.
201
202OPTIMIZE_FOR_FORTRAN = NO
203
204# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
205# sources. Doxygen will then generate output that is tailored for
206# VHDL.
207
208OPTIMIZE_OUTPUT_VHDL = NO
209
210# Doxygen selects the parser to use depending on the extension of the files it
211# parses. With this tag you can assign which parser to use for a given extension.
212# Doxygen has a built-in mapping, but you can override or extend it using this
213# tag. The format is ext=language, where ext is a file extension, and language
214# is one of the parsers supported by doxygen: IDL, Java, Javascript, CSharp, C,
215# C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. For instance to make
216# doxygen treat .inc files as Fortran files (default is PHP), and .f files as C
217# (default is Fortran), use: inc=Fortran f=C. Note that for custom extensions
218# you also need to set FILE_PATTERNS otherwise the files are not read by doxygen.
219
220EXTENSION_MAPPING =
221
222# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
223# to include (a tag file for) the STL sources as input, then you should
224# set this tag to YES in order to let doxygen match functions declarations and
225# definitions whose arguments contain STL classes (e.g. func(std::string); v.s.
226# func(std::string) {}). This also make the inheritance and collaboration
227# diagrams that involve STL classes more complete and accurate.
228
229BUILTIN_STL_SUPPORT = NO
230
231# If you use Microsoft's C++/CLI language, you should set this option to YES to
232# enable parsing support.
233
234CPP_CLI_SUPPORT = NO
235
236# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only.
237# Doxygen will parse them like normal C++ but will assume all classes use public
238# instead of private inheritance when no explicit protection keyword is present.
239
240SIP_SUPPORT = NO
241
242# For Microsoft's IDL there are propget and propput attributes to indicate getter
243# and setter methods for a property. Setting this option to YES (the default)
244# will make doxygen to replace the get and set methods by a property in the
245# documentation. This will only work if the methods are indeed getting or
246# setting a simple type. If this is not the case, or you want to show the
247# methods anyway, you should set this option to NO.
248
249IDL_PROPERTY_SUPPORT = YES
250
251# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
252# tag is set to YES, then doxygen will reuse the documentation of the first
253# member in the group (if any) for the other members of the group. By default
254# all members of a group must be documented explicitly.
255
256DISTRIBUTE_GROUP_DOC = NO
257
258# Set the SUBGROUPING tag to YES (the default) to allow class member groups of
259# the same type (for instance a group of public functions) to be put as a
260# subgroup of that type (e.g. under the Public Functions section). Set it to
261# NO to prevent subgrouping. Alternatively, this can be done per class using
262# the \nosubgrouping command.
263
264SUBGROUPING = YES
265
266# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum
267# is documented as struct, union, or enum with the name of the typedef. So
268# typedef struct TypeS {} TypeT, will appear in the documentation as a struct
269# with name TypeT. When disabled the typedef will appear as a member of a file,
270# namespace, or class. And the struct will be named TypeS. This can typically
271# be useful for C code in case the coding convention dictates that all compound
272# types are typedef'ed and only the typedef is referenced, never the tag name.
273
274TYPEDEF_HIDES_STRUCT = NO
275
276# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to
277# determine which symbols to keep in memory and which to flush to disk.
278# When the cache is full, less often used symbols will be written to disk.
279# For small to medium size projects (<1000 input files) the default value is
280# probably good enough. For larger projects a too small cache size can cause
281# doxygen to be busy swapping symbols to and from disk most of the time
282# causing a significant performance penality.
283# If the system has enough physical memory increasing the cache will improve the
284# performance by keeping more symbols in memory. Note that the value works on
285# a logarithmic scale so increasing the size by one will rougly double the
286# memory usage. The cache size is given by this formula:
287# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,
288# corresponding to a cache size of 2^16 = 65536 symbols
289
290SYMBOL_CACHE_SIZE = 0
291
292#---------------------------------------------------------------------------
293# Build related configuration options
294#---------------------------------------------------------------------------
295
296# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
297# documentation are documented, even if no documentation was available.
298# Private class members and static file members will be hidden unless
299# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
300
301EXTRACT_ALL = NO
302
303# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
304# will be included in the documentation.
305
306EXTRACT_PRIVATE = NO
307
308# If the EXTRACT_STATIC tag is set to YES all static members of a file
309# will be included in the documentation.
310
311EXTRACT_STATIC = YES
312
313# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
314# defined locally in source files will be included in the documentation.
315# If set to NO only classes defined in header files are included.
316
317EXTRACT_LOCAL_CLASSES = NO
318
319# This flag is only useful for Objective-C code. When set to YES local
320# methods, which are defined in the implementation section but not in
321# the interface are included in the documentation.
322# If set to NO (the default) only methods in the interface are included.
323
324EXTRACT_LOCAL_METHODS = NO
325
326# If this flag is set to YES, the members of anonymous namespaces will be
327# extracted and appear in the documentation as a namespace called
328# 'anonymous_namespace{file}', where file will be replaced with the base
329# name of the file that contains the anonymous namespace. By default
330# anonymous namespace are hidden.
331
332EXTRACT_ANON_NSPACES = NO
333
334# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
335# undocumented members of documented classes, files or namespaces.
336# If set to NO (the default) these members will be included in the
337# various overviews, but no documentation section is generated.
338# This option has no effect if EXTRACT_ALL is enabled.
339
340HIDE_UNDOC_MEMBERS = NO
341
342# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
343# undocumented classes that are normally visible in the class hierarchy.
344# If set to NO (the default) these classes will be included in the various
345# overviews. This option has no effect if EXTRACT_ALL is enabled.
346
347HIDE_UNDOC_CLASSES = NO
348
349# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
350# friend (class|struct|union) declarations.
351# If set to NO (the default) these declarations will be included in the
352# documentation.
353
354HIDE_FRIEND_COMPOUNDS = NO
355
356# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
357# documentation blocks found inside the body of a function.
358# If set to NO (the default) these blocks will be appended to the
359# function's detailed documentation block.
360
361HIDE_IN_BODY_DOCS = NO
362
363# The INTERNAL_DOCS tag determines if documentation
364# that is typed after a \internal command is included. If the tag is set
365# to NO (the default) then the documentation will be excluded.
366# Set it to YES to include the internal documentation.
367
368INTERNAL_DOCS = NO
369
370# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
371# file names in lower-case letters. If set to YES upper-case letters are also
372# allowed. This is useful if you have classes or files whose names only differ
373# in case and if your file system supports case sensitive file names. Windows
374# and Mac users are advised to set this option to NO.
375
376CASE_SENSE_NAMES = YES
377
378# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
379# will show members with their full class and namespace scopes in the
380# documentation. If set to YES the scope will be hidden.
381
382HIDE_SCOPE_NAMES = NO
383
384# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
385# will put a list of the files that are included by a file in the documentation
386# of that file.
387
388SHOW_INCLUDE_FILES = NO
389
390# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen
391# will list include files with double quotes in the documentation
392# rather than with sharp brackets.
393
394FORCE_LOCAL_INCLUDES = NO
395
396# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
397# is inserted in the documentation for inline members.
398
399INLINE_INFO = YES
400
401# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
402# will sort the (detailed) documentation of file and class members
403# alphabetically by member name. If set to NO the members will appear in
404# declaration order.
405
406SORT_MEMBER_DOCS = NO
407
408# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
409# brief documentation of file, namespace and class members alphabetically
410# by member name. If set to NO (the default) the members will appear in
411# declaration order.
412
413SORT_BRIEF_DOCS = NO
414
415# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen
416# will sort the (brief and detailed) documentation of class members so that
417# constructors and destructors are listed first. If set to NO (the default)
418# the constructors will appear in the respective orders defined by
419# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS.
420# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO
421# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.
422
423SORT_MEMBERS_CTORS_1ST = NO
424
425# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the
426# hierarchy of group names into alphabetical order. If set to NO (the default)
427# the group names will appear in their defined order.
428
429SORT_GROUP_NAMES = NO
430
431# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
432# sorted by fully-qualified names, including namespaces. If set to
433# NO (the default), the class list will be sorted only by class name,
434# not including the namespace part.
435# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
436# Note: This option applies only to the class list, not to the
437# alphabetical list.
438
439SORT_BY_SCOPE_NAME = NO
440
441# The GENERATE_TODOLIST tag can be used to enable (YES) or
442# disable (NO) the todo list. This list is created by putting \todo
443# commands in the documentation.
444
445GENERATE_TODOLIST = YES
446
447# The GENERATE_TESTLIST tag can be used to enable (YES) or
448# disable (NO) the test list. This list is created by putting \test
449# commands in the documentation.
450
451GENERATE_TESTLIST = YES
452
453# The GENERATE_BUGLIST tag can be used to enable (YES) or
454# disable (NO) the bug list. This list is created by putting \bug
455# commands in the documentation.
456
457GENERATE_BUGLIST = YES
458
459# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
460# disable (NO) the deprecated list. This list is created by putting
461# \deprecated commands in the documentation.
462
463GENERATE_DEPRECATEDLIST= YES
464
465# The ENABLED_SECTIONS tag can be used to enable conditional
466# documentation sections, marked by \if sectionname ... \endif.
467
468ENABLED_SECTIONS =
469
470# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
471# the initial value of a variable or define consists of for it to appear in
472# the documentation. If the initializer consists of more lines than specified
473# here it will be hidden. Use a value of 0 to hide initializers completely.
474# The appearance of the initializer of individual variables and defines in the
475# documentation can be controlled using \showinitializer or \hideinitializer
476# command in the documentation regardless of this setting.
477
478MAX_INITIALIZER_LINES = 30
479
480# Set the SHOW_USED_FILES tag to NO to disable the list of files generated
481# at the bottom of the documentation of classes and structs. If set to YES the
482# list will mention the files that were used to generate the documentation.
483
484SHOW_USED_FILES = NO
485
486# Set the SHOW_FILES tag to NO to disable the generation of the Files page.
487# This will remove the Files entry from the Quick Index and from the
488# Folder Tree View (if specified). The default is YES.
489
490SHOW_FILES = YES
491
492# Set the SHOW_NAMESPACES tag to NO to disable the generation of the
493# Namespaces page.
494# This will remove the Namespaces entry from the Quick Index
495# and from the Folder Tree View (if specified). The default is YES.
496
497SHOW_NAMESPACES = NO
498
499# The FILE_VERSION_FILTER tag can be used to specify a program or script that
500# doxygen should invoke to get the current version for each file (typically from
501# the version control system). Doxygen will invoke the program by executing (via
502# popen()) the command <command> <input-file>, where <command> is the value of
503# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
504# provided by doxygen. Whatever the program writes to standard output
505# is used as the file version. See the manual for examples.
506
507FILE_VERSION_FILTER =
508
509# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
510# by doxygen. The layout file controls the global structure of the generated
511# output files in an output format independent way. The create the layout file
512# that represents doxygen's defaults, run doxygen with the -l option.
513# You can optionally specify a file name after the option, if omitted
514# DoxygenLayout.xml will be used as the name of the layout file.
515
516LAYOUT_FILE =
517
518#---------------------------------------------------------------------------
519# configuration options related to warning and progress messages
520#---------------------------------------------------------------------------
521
522# The QUIET tag can be used to turn on/off the messages that are generated
523# by doxygen. Possible values are YES and NO. If left blank NO is used.
524
525QUIET = NO
526
527# The WARNINGS tag can be used to turn on/off the warning messages that are
528# generated by doxygen. Possible values are YES and NO. If left blank
529# NO is used.
530
531WARNINGS = YES
532
533# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
534# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
535# automatically be disabled.
536
537WARN_IF_UNDOCUMENTED = YES
538
539# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
540# potential errors in the documentation, such as not documenting some
541# parameters in a documented function, or documenting parameters that
542# don't exist or using markup commands wrongly.
543
544WARN_IF_DOC_ERROR = YES
545
546# This WARN_NO_PARAMDOC option can be abled to get warnings for
547# functions that are documented, but have no documentation for their parameters
548# or return value. If set to NO (the default) doxygen will only warn about
549# wrong or incomplete parameter documentation, but not about the absence of
550# documentation.
551
552WARN_NO_PARAMDOC = NO
553
554# The WARN_FORMAT tag determines the format of the warning messages that
555# doxygen can produce. The string should contain the $file, $line, and $text
556# tags, which will be replaced by the file and line number from which the
557# warning originated and the warning text. Optionally the format may contain
558# $version, which will be replaced by the version of the file (if it could
559# be obtained via FILE_VERSION_FILTER)
560
561WARN_FORMAT = "$file:$line: $text"
562
563# The WARN_LOGFILE tag can be used to specify a file to which warning
564# and error messages should be written. If left blank the output is written
565# to stderr.
566
567WARN_LOGFILE =
568
569#---------------------------------------------------------------------------
570# configuration options related to the input files
571#---------------------------------------------------------------------------
572
573# The INPUT tag can be used to specify the files and/or directories that contain
574# documented source files. You may enter file names like "myfile.cpp" or
575# directories like "/usr/src/myproject". Separate the files or directories
576# with spaces.
577
578INPUT = @top_srcdir@/src/lib eio.dox
579
580# This tag can be used to specify the character encoding of the source files
581# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is
582# also the default input encoding. Doxygen uses libiconv (or the iconv built
583# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for
584# the list of possible encodings.
585
586INPUT_ENCODING = UTF-8
587
588# If the value of the INPUT tag contains directories, you can use the
589# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
590# and *.h) to filter out the source-files in the directories. If left
591# blank the following patterns are tested:
592# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx
593# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90
594
595FILE_PATTERNS = *.c *.h
596
597# The RECURSIVE tag can be used to turn specify whether or not subdirectories
598# should be searched for input files as well. Possible values are YES and NO.
599# If left blank NO is used.
600
601RECURSIVE = YES
602
603# The EXCLUDE tag can be used to specify files and/or directories that should
604# excluded from the INPUT source files. This way you can easily exclude a
605# subdirectory from a directory tree whose root is specified with the INPUT tag.
606
607EXCLUDE = ../src/lib/eio_private.h
608
609# The EXCLUDE_SYMLINKS tag can be used select whether or not files or
610# directories that are symbolic links (a Unix filesystem feature) are excluded
611# from the input.
612
613EXCLUDE_SYMLINKS = NO
614
615# If the value of the INPUT tag contains directories, you can use the
616# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
617# certain files from those directories. Note that the wildcards are matched
618# against the file with absolute path, so to exclude all test directories
619# for example use the pattern */test/*
620
621EXCLUDE_PATTERNS =
622
623# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
624# (namespaces, classes, functions, etc.) that should be excluded from the
625# output. The symbol name can be a fully qualified name, a word, or if the
626# wildcard * is used, a substring. Examples: ANamespace, AClass,
627# AClass::ANamespace, ANamespace::*Test
628
629EXCLUDE_SYMBOLS =
630
631# The EXAMPLE_PATH tag can be used to specify one or more files or
632# directories that contain example code fragments that are included (see
633# the \include command).
634
635EXAMPLE_PATH =
636
637# If the value of the EXAMPLE_PATH tag contains directories, you can use the
638# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
639# and *.h) to filter out the source-files in the directories. If left
640# blank all files are included.
641
642EXAMPLE_PATTERNS =
643
644# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
645# searched for input files to be used with the \include or \dontinclude
646# commands irrespective of the value of the RECURSIVE tag.
647# Possible values are YES and NO. If left blank NO is used.
648
649EXAMPLE_RECURSIVE = NO
650
651# The IMAGE_PATH tag can be used to specify one or more files or
652# directories that contain image that are included in the documentation (see
653# the \image command).
654
655IMAGE_PATH = img
656
657# The INPUT_FILTER tag can be used to specify a program that doxygen should
658# invoke to filter for each input file. Doxygen will invoke the filter program
659# by executing (via popen()) the command <filter> <input-file>, where <filter>
660# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
661# input file. Doxygen will then use the output that the filter program writes
662# to standard output.
663# If FILTER_PATTERNS is specified, this tag will be
664# ignored.
665
666INPUT_FILTER =
667
668# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
669# basis.
670# Doxygen will compare the file name with each pattern and apply the
671# filter if there is a match.
672# The filters are a list of the form:
673# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
674# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER
675# is applied to all files.
676
677FILTER_PATTERNS =
678
679# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
680# INPUT_FILTER) will be used to filter the input files when producing source
681# files to browse (i.e. when SOURCE_BROWSER is set to YES).
682
683FILTER_SOURCE_FILES = NO
684
685#---------------------------------------------------------------------------
686# configuration options related to source browsing
687#---------------------------------------------------------------------------
688
689# If the SOURCE_BROWSER tag is set to YES then a list of source files will
690# be generated. Documented entities will be cross-referenced with these sources.
691# Note: To get rid of all source code in the generated output, make sure also
692# VERBATIM_HEADERS is set to NO.
693
694SOURCE_BROWSER = NO
695
696# Setting the INLINE_SOURCES tag to YES will include the body
697# of functions and classes directly in the documentation.
698
699INLINE_SOURCES = NO
700
701# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
702# doxygen to hide any special comment blocks from generated source code
703# fragments. Normal C and C++ comments will always remain visible.
704
705STRIP_CODE_COMMENTS = YES
706
707# If the REFERENCED_BY_RELATION tag is set to YES
708# then for each documented function all documented
709# functions referencing it will be listed.
710
711REFERENCED_BY_RELATION = NO
712
713# If the REFERENCES_RELATION tag is set to YES
714# then for each documented function all documented entities
715# called/used by that function will be listed.
716
717REFERENCES_RELATION = NO
718
719# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
720# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
721# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
722# link to the source code.
723# Otherwise they will link to the documentation.
724
725REFERENCES_LINK_SOURCE = YES
726
727# If the USE_HTAGS tag is set to YES then the references to source code
728# will point to the HTML generated by the htags(1) tool instead of doxygen
729# built-in source browser. The htags tool is part of GNU's global source
730# tagging system (see http://www.gnu.org/software/global/global.html). You
731# will need version 4.8.6 or higher.
732
733USE_HTAGS = NO
734
735# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
736# will generate a verbatim copy of the header file for each class for
737# which an include is specified. Set to NO to disable this.
738
739VERBATIM_HEADERS = YES
740
741#---------------------------------------------------------------------------
742# configuration options related to the alphabetical class index
743#---------------------------------------------------------------------------
744
745# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
746# of all compounds will be generated. Enable this if the project
747# contains a lot of classes, structs, unions or interfaces.
748
749ALPHABETICAL_INDEX = YES
750
751# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
752# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
753# in which this list will be split (can be a number in the range [1..20])
754
755COLS_IN_ALPHA_INDEX = 5
756
757# In case all classes in a project start with a common prefix, all
758# classes will be put under the same header in the alphabetical index.
759# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
760# should be ignored while generating the index headers.
761
762IGNORE_PREFIX =
763
764#---------------------------------------------------------------------------
765# configuration options related to the HTML output
766#---------------------------------------------------------------------------
767
768# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
769# generate HTML output.
770
771GENERATE_HTML = YES
772
773# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
774# If a relative path is entered the value of OUTPUT_DIRECTORY will be
775# put in front of it. If left blank `html' will be used as the default path.
776
777HTML_OUTPUT = html
778
779# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
780# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
781# doxygen will generate files with .html extension.
782
783HTML_FILE_EXTENSION = .html
784
785# The HTML_HEADER tag can be used to specify a personal HTML header for
786# each generated HTML page. If it is left blank doxygen will generate a
787# standard header.
788
789HTML_HEADER = @srcdir@/head.html
790
791# The HTML_FOOTER tag can be used to specify a personal HTML footer for
792# each generated HTML page. If it is left blank doxygen will generate a
793# standard footer.
794
795HTML_FOOTER = @srcdir@/foot.html
796
797# The HTML_STYLESHEET tag can be used to specify a user-defined cascading
798# style sheet that is used by each HTML page. It can be used to
799# fine-tune the look of the HTML output. If the tag is left blank doxygen
800# will generate a default style sheet. Note that doxygen will try to copy
801# the style sheet file to the HTML output directory, so don't put your own
802# stylesheet in the HTML output directory as well, or it will be erased!
803
804HTML_STYLESHEET = @srcdir@/e.css
805
806# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output.
807# Doxygen will adjust the colors in the stylesheet and background images
808# according to this color. Hue is specified as an angle on a colorwheel,
809# see http://en.wikipedia.org/wiki/Hue for more information.
810# For instance the value 0 represents red, 60 is yellow, 120 is green,
811# 180 is cyan, 240 is blue, 300 purple, and 360 is red again.
812# The allowed range is 0 to 359.
813
814HTML_COLORSTYLE_HUE = 220
815
816# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of
817# the colors in the HTML output. For a value of 0 the output will use
818# grayscales only. A value of 255 will produce the most vivid colors.
819
820HTML_COLORSTYLE_SAT = 100
821
822# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to
823# the luminance component of the colors in the HTML output. Values below
824# 100 gradually make the output lighter, whereas values above 100 make
825# the output darker. The value divided by 100 is the actual gamma applied,
826# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2,
827# and 100 does not change the gamma.
828
829HTML_COLORSTYLE_GAMMA = 80
830
831# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
832# page will contain the date and time when the page was generated. Setting
833# this to NO can help when comparing the output of multiple runs.
834
835HTML_TIMESTAMP = YES
836
837# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
838# documentation will contain sections that can be hidden and shown after the
839# page has loaded. For this to work a browser that supports
840# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox
841# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).
842
843HTML_DYNAMIC_SECTIONS = NO
844
845# If the GENERATE_DOCSET tag is set to YES, additional index files
846# will be generated that can be used as input for Apple's Xcode 3
847# integrated development environment, introduced with OSX 10.5 (Leopard).
848# To create a documentation set, doxygen will generate a Makefile in the
849# HTML output directory. Running make will produce the docset in that
850# directory and running "make install" will install the docset in
851# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
852# it at startup.
853# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
854# for more information.
855
856GENERATE_DOCSET = NO
857
858# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the
859# feed. A documentation feed provides an umbrella under which multiple
860# documentation sets from a single provider (such as a company or product suite)
861# can be grouped.
862
863DOCSET_FEEDNAME = "Doxygen generated docs"
864
865# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that
866# should uniquely identify the documentation set bundle. This should be a
867# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen
868# will append .docset to the name.
869
870DOCSET_BUNDLE_ID = org.doxygen.Project
871
872# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify
873# the documentation publisher. This should be a reverse domain-name style
874# string, e.g. com.mycompany.MyDocSet.documentation.
875
876DOCSET_PUBLISHER_ID = org.doxygen.Publisher
877
878# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.
879
880DOCSET_PUBLISHER_NAME = Publisher
881
882# If the GENERATE_HTMLHELP tag is set to YES, additional index files
883# will be generated that can be used as input for tools like the
884# Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
885# of the generated HTML documentation.
886
887GENERATE_HTMLHELP = NO
888
889# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
890# be used to specify the file name of the resulting .chm file. You
891# can add a path in front of the file if the result should not be
892# written to the html output directory.
893
894CHM_FILE =
895
896# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
897# be used to specify the location (absolute path including file name) of
898# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
899# the HTML help compiler on the generated index.hhp.
900
901HHC_LOCATION =
902
903# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
904# controls if a separate .chi index file is generated (YES) or that
905# it should be included in the master .chm file (NO).
906
907GENERATE_CHI = NO
908
909# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING
910# is used to encode HtmlHelp index (hhk), content (hhc) and project file
911# content.
912
913CHM_INDEX_ENCODING =
914
915# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
916# controls whether a binary table of contents is generated (YES) or a
917# normal table of contents (NO) in the .chm file.
918
919BINARY_TOC = NO
920
921# The TOC_EXPAND flag can be set to YES to add extra items for group members
922# to the contents of the HTML help documentation and to the tree view.
923
924TOC_EXPAND = NO
925
926# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
927# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated
928# that can be used as input for Qt's qhelpgenerator to generate a
929# Qt Compressed Help (.qch) of the generated HTML documentation.
930
931GENERATE_QHP = NO
932
933# If the QHG_LOCATION tag is specified, the QCH_FILE tag can
934# be used to specify the file name of the resulting .qch file.
935# The path specified is relative to the HTML output folder.
936
937QCH_FILE =
938
939# The QHP_NAMESPACE tag specifies the namespace to use when generating
940# Qt Help Project output. For more information please see
941# http://doc.trolltech.com/qthelpproject.html#namespace
942
943QHP_NAMESPACE = org.doxygen.Project
944
945# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating
946# Qt Help Project output. For more information please see
947# http://doc.trolltech.com/qthelpproject.html#virtual-folders
948
949QHP_VIRTUAL_FOLDER = doc
950
951# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to
952# add. For more information please see
953# http://doc.trolltech.com/qthelpproject.html#custom-filters
954
955QHP_CUST_FILTER_NAME =
956
957# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the
958# custom filter to add. For more information please see
959# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">
960# Qt Help Project / Custom Filters</a>.
961
962QHP_CUST_FILTER_ATTRS =
963
964# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
965# project's
966# filter section matches.
967# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">
968# Qt Help Project / Filter Attributes</a>.
969
970QHP_SECT_FILTER_ATTRS =
971
972# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can
973# be used to specify the location of Qt's qhelpgenerator.
974# If non-empty doxygen will try to run qhelpgenerator on the generated
975# .qhp file.
976
977QHG_LOCATION =
978
979# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files
980# will be generated, which together with the HTML files, form an Eclipse help
981# plugin. To install this plugin and make it available under the help contents
982# menu in Eclipse, the contents of the directory containing the HTML and XML
983# files needs to be copied into the plugins directory of eclipse. The name of
984# the directory within the plugins directory should be the same as
985# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before
986# the help appears.
987
988GENERATE_ECLIPSEHELP = NO
989
990# A unique identifier for the eclipse help plugin. When installing the plugin
991# the directory name containing the HTML and XML files should also have
992# this name.
993
994ECLIPSE_DOC_ID = org.doxygen.Project
995
996# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
997# top of each HTML page. The value NO (the default) enables the index and
998# the value YES disables it.
999
1000DISABLE_INDEX = YES
1001
1002# This tag can be used to set the number of enum values (range [1..20])
1003# that doxygen will group on one line in the generated HTML documentation.
1004
1005ENUM_VALUES_PER_LINE = 4
1006
1007# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1008# structure should be generated to display hierarchical information.
1009# If the tag value is set to YES, a side panel will be generated
1010# containing a tree-like index structure (just like the one that
1011# is generated for HTML Help). For this to work a browser that supports
1012# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).
1013# Windows users are probably better off using the HTML help feature.
1014
1015GENERATE_TREEVIEW = NO
1016
1017# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
1018# used to set the initial width (in pixels) of the frame in which the tree
1019# is shown.
1020
1021TREEVIEW_WIDTH = 250
1022
1023# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open
1024# links to external symbols imported via tag files in a separate window.
1025
1026EXT_LINKS_IN_WINDOW = NO
1027
1028# Use this tag to change the font size of Latex formulas included
1029# as images in the HTML documentation. The default is 10. Note that
1030# when you change the font size after a successful doxygen run you need
1031# to manually remove any form_*.png images from the HTML output directory
1032# to force them to be regenerated.
1033
1034FORMULA_FONTSIZE = 10
1035
1036# Use the FORMULA_TRANPARENT tag to determine whether or not the images
1037# generated for formulas are transparent PNGs. Transparent PNGs are
1038# not supported properly for IE 6.0, but are supported on all modern browsers.
1039# Note that when changing this option you need to delete any form_*.png files
1040# in the HTML output before the changes have effect.
1041
1042FORMULA_TRANSPARENT = YES
1043
1044# When the SEARCHENGINE tag is enabled doxygen will generate a search box
1045# for the HTML output. The underlying search engine uses javascript
1046# and DHTML and should work on any modern browser. Note that when using
1047# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets
1048# (GENERATE_DOCSET) there is already a search function so this one should
1049# typically be disabled. For large projects the javascript based search engine
1050# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.
1051
1052SEARCHENGINE = NO
1053
1054# When the SERVER_BASED_SEARCH tag is enabled the search engine will be
1055# implemented using a PHP enabled web server instead of at the web client
1056# using Javascript. Doxygen will generate the search PHP script and index
1057# file to put on the web server. The advantage of the server
1058# based approach is that it scales better to large projects and allows
1059# full text search. The disadvances is that it is more difficult to setup
1060# and does not have live searching capabilities.
1061
1062SERVER_BASED_SEARCH = NO
1063
1064#---------------------------------------------------------------------------
1065# configuration options related to the LaTeX output
1066#---------------------------------------------------------------------------
1067
1068# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
1069# generate Latex output.
1070
1071GENERATE_LATEX = YES
1072
1073# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
1074# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1075# put in front of it. If left blank `latex' will be used as the default path.
1076
1077LATEX_OUTPUT = latex
1078
1079# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
1080# invoked. If left blank `latex' will be used as the default command name.
1081# Note that when enabling USE_PDFLATEX this option is only used for
1082# generating bitmaps for formulas in the HTML output, but not in the
1083# Makefile that is written to the output directory.
1084
1085LATEX_CMD_NAME = latex
1086
1087# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
1088# generate index for LaTeX. If left blank `makeindex' will be used as the
1089# default command name.
1090
1091MAKEINDEX_CMD_NAME = makeindex
1092
1093# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
1094# LaTeX documents. This may be useful for small projects and may help to
1095# save some trees in general.
1096
1097COMPACT_LATEX = NO
1098
1099# The PAPER_TYPE tag can be used to set the paper type that is used
1100# by the printer. Possible values are: a4, a4wide, letter, legal and
1101# executive. If left blank a4wide will be used.
1102
1103PAPER_TYPE = a4wide
1104
1105# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
1106# packages that should be included in the LaTeX output.
1107
1108EXTRA_PACKAGES =
1109
1110# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
1111# the generated latex document. The header should contain everything until
1112# the first chapter. If it is left blank doxygen will generate a
1113# standard header. Notice: only use this tag if you know what you are doing!
1114
1115LATEX_HEADER =
1116
1117# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
1118# is prepared for conversion to pdf (using ps2pdf). The pdf file will
1119# contain links (just like the HTML output) instead of page references
1120# This makes the output suitable for online browsing using a pdf viewer.
1121
1122PDF_HYPERLINKS = YES
1123
1124# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
1125# plain latex in the generated Makefile. Set this option to YES to get a
1126# higher quality PDF documentation.
1127
1128USE_PDFLATEX = YES
1129
1130# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
1131# command to the generated LaTeX files. This will instruct LaTeX to keep
1132# running if errors occur, instead of asking the user for help.
1133# This option is also used when generating formulas in HTML.
1134
1135LATEX_BATCHMODE = NO
1136
1137# If LATEX_HIDE_INDICES is set to YES then doxygen will not
1138# include the index chapters (such as File Index, Compound Index, etc.)
1139# in the output.
1140
1141LATEX_HIDE_INDICES = NO
1142
1143# If LATEX_SOURCE_CODE is set to YES then doxygen will include
1144# source code with syntax highlighting in the LaTeX output.
1145# Note that which sources are shown also depends on other settings
1146# such as SOURCE_BROWSER.
1147
1148LATEX_SOURCE_CODE = NO
1149
1150#---------------------------------------------------------------------------
1151# configuration options related to the RTF output
1152#---------------------------------------------------------------------------
1153
1154# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
1155# The RTF output is optimized for Word 97 and may not look very pretty with
1156# other RTF readers or editors.
1157
1158GENERATE_RTF = NO
1159
1160# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
1161# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1162# put in front of it. If left blank `rtf' will be used as the default path.
1163
1164RTF_OUTPUT = rtf
1165
1166# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
1167# RTF documents. This may be useful for small projects and may help to
1168# save some trees in general.
1169
1170COMPACT_RTF = NO
1171
1172# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
1173# will contain hyperlink fields. The RTF file will
1174# contain links (just like the HTML output) instead of page references.
1175# This makes the output suitable for online browsing using WORD or other
1176# programs which support those fields.
1177# Note: wordpad (write) and others do not support links.
1178
1179RTF_HYPERLINKS = NO
1180
1181# Load stylesheet definitions from file. Syntax is similar to doxygen's
1182# config file, i.e. a series of assignments. You only have to provide
1183# replacements, missing definitions are set to their default value.
1184
1185RTF_STYLESHEET_FILE =
1186
1187# Set optional variables used in the generation of an rtf document.
1188# Syntax is similar to doxygen's config file.
1189
1190RTF_EXTENSIONS_FILE =
1191
1192#---------------------------------------------------------------------------
1193# configuration options related to the man page output
1194#---------------------------------------------------------------------------
1195
1196# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
1197# generate man pages
1198
1199GENERATE_MAN = YES
1200
1201# The MAN_OUTPUT tag is used to specify where the man pages will be put.
1202# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1203# put in front of it. If left blank `man' will be used as the default path.
1204
1205MAN_OUTPUT = man
1206
1207# The MAN_EXTENSION tag determines the extension that is added to
1208# the generated man pages (default is the subroutine's section .3)
1209
1210MAN_EXTENSION = .3
1211
1212# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
1213# then it will generate one additional man file for each entity
1214# documented in the real man page(s). These additional files
1215# only source the real man page, but without them the man command
1216# would be unable to find the correct page. The default is NO.
1217
1218MAN_LINKS = NO
1219
1220#---------------------------------------------------------------------------
1221# configuration options related to the XML output
1222#---------------------------------------------------------------------------
1223
1224# If the GENERATE_XML tag is set to YES Doxygen will
1225# generate an XML file that captures the structure of
1226# the code including all documentation.
1227
1228GENERATE_XML = NO
1229
1230# The XML_OUTPUT tag is used to specify where the XML pages will be put.
1231# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1232# put in front of it. If left blank `xml' will be used as the default path.
1233
1234XML_OUTPUT = xml
1235
1236# The XML_SCHEMA tag can be used to specify an XML schema,
1237# which can be used by a validating XML parser to check the
1238# syntax of the XML files.
1239
1240XML_SCHEMA =
1241
1242# The XML_DTD tag can be used to specify an XML DTD,
1243# which can be used by a validating XML parser to check the
1244# syntax of the XML files.
1245
1246XML_DTD =
1247
1248# If the XML_PROGRAMLISTING tag is set to YES Doxygen will
1249# dump the program listings (including syntax highlighting
1250# and cross-referencing information) to the XML output. Note that
1251# enabling this will significantly increase the size of the XML output.
1252
1253XML_PROGRAMLISTING = YES
1254
1255#---------------------------------------------------------------------------
1256# configuration options for the AutoGen Definitions output
1257#---------------------------------------------------------------------------
1258
1259# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
1260# generate an AutoGen Definitions (see autogen.sf.net) file
1261# that captures the structure of the code including all
1262# documentation. Note that this feature is still experimental
1263# and incomplete at the moment.
1264
1265GENERATE_AUTOGEN_DEF = NO
1266
1267#---------------------------------------------------------------------------
1268# configuration options related to the Perl module output
1269#---------------------------------------------------------------------------
1270
1271# If the GENERATE_PERLMOD tag is set to YES Doxygen will
1272# generate a Perl module file that captures the structure of
1273# the code including all documentation. Note that this
1274# feature is still experimental and incomplete at the
1275# moment.
1276
1277GENERATE_PERLMOD = NO
1278
1279# If the PERLMOD_LATEX tag is set to YES Doxygen will generate
1280# the necessary Makefile rules, Perl scripts and LaTeX code to be able
1281# to generate PDF and DVI output from the Perl module output.
1282
1283PERLMOD_LATEX = NO
1284
1285# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
1286# nicely formatted so it can be parsed by a human reader.
1287# This is useful
1288# if you want to understand what is going on.
1289# On the other hand, if this
1290# tag is set to NO the size of the Perl module output will be much smaller
1291# and Perl will parse it just the same.
1292
1293PERLMOD_PRETTY = YES
1294
1295# The names of the make variables in the generated doxyrules.make file
1296# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
1297# This is useful so different doxyrules.make files included by the same
1298# Makefile don't overwrite each other's variables.
1299
1300PERLMOD_MAKEVAR_PREFIX =
1301
1302#---------------------------------------------------------------------------
1303# Configuration options related to the preprocessor
1304#---------------------------------------------------------------------------
1305
1306# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
1307# evaluate all C-preprocessor directives found in the sources and include
1308# files.
1309
1310ENABLE_PREPROCESSING = YES
1311
1312# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
1313# names in the source code. If set to NO (the default) only conditional
1314# compilation will be performed. Macro expansion can be done in a controlled
1315# way by setting EXPAND_ONLY_PREDEF to YES.
1316
1317MACRO_EXPANSION = NO
1318
1319# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
1320# then the macro expansion is limited to the macros specified with the
1321# PREDEFINED and EXPAND_AS_DEFINED tags.
1322
1323EXPAND_ONLY_PREDEF = NO
1324
1325# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
1326# in the INCLUDE_PATH (see below) will be search if a #include is found.
1327
1328SEARCH_INCLUDES = YES
1329
1330# The INCLUDE_PATH tag can be used to specify one or more directories that
1331# contain include files that are not input files but should be processed by
1332# the preprocessor.
1333
1334INCLUDE_PATH =
1335
1336# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
1337# patterns (like *.h and *.hpp) to filter out the header-files in the
1338# directories. If left blank, the patterns specified with FILE_PATTERNS will
1339# be used.
1340
1341INCLUDE_FILE_PATTERNS =
1342
1343# The PREDEFINED tag can be used to specify one or more macro names that
1344# are defined before the preprocessor is started (similar to the -D option of
1345# gcc). The argument of the tag is a list of macros of the form: name
1346# or name=definition (no spaces). If the definition and the = are
1347# omitted =1 is assumed. To prevent a macro definition from being
1348# undefined via #undef or recursively expanded use the := operator
1349# instead of the = operator.
1350
1351PREDEFINED =
1352
1353# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
1354# this tag can be used to specify a list of macro names that should be expanded.
1355# The macro definition that is found in the sources will be used.
1356# Use the PREDEFINED tag if you want to use a different macro definition.
1357
1358EXPAND_AS_DEFINED =
1359
1360# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
1361# doxygen's preprocessor will remove all function-like macros that are alone
1362# on a line, have an all uppercase name, and do not end with a semicolon. Such
1363# function macros are typically used for boiler-plate code, and will confuse
1364# the parser if not removed.
1365
1366SKIP_FUNCTION_MACROS = YES
1367
1368#---------------------------------------------------------------------------
1369# Configuration::additions related to external references
1370#---------------------------------------------------------------------------
1371
1372# The TAGFILES option can be used to specify one or more tagfiles.
1373# Optionally an initial location of the external documentation
1374# can be added for each tagfile. The format of a tag file without
1375# this location is as follows:
1376#
1377# TAGFILES = file1 file2 ...
1378# Adding location for the tag files is done as follows:
1379#
1380# TAGFILES = file1=loc1 "file2 = loc2" ...
1381# where "loc1" and "loc2" can be relative or absolute paths or
1382# URLs. If a location is present for each tag, the installdox tool
1383# does not have to be run to correct the links.
1384# Note that each tag file must have a unique name
1385# (where the name does NOT include the path)
1386# If a tag file is not located in the directory in which doxygen
1387# is run, you must also specify the path to the tagfile here.
1388
1389TAGFILES =
1390
1391# When a file name is specified after GENERATE_TAGFILE, doxygen will create
1392# a tag file that is based on the input files it reads.
1393
1394GENERATE_TAGFILE =
1395
1396# If the ALLEXTERNALS tag is set to YES all external classes will be listed
1397# in the class index. If set to NO only the inherited external classes
1398# will be listed.
1399
1400ALLEXTERNALS = NO
1401
1402# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1403# in the modules index. If set to NO, only the current project's groups will
1404# be listed.
1405
1406EXTERNAL_GROUPS = YES
1407
1408# The PERL_PATH should be the absolute path and name of the perl script
1409# interpreter (i.e. the result of `which perl').
1410
1411PERL_PATH = /usr/bin/perl
1412
1413#---------------------------------------------------------------------------
1414# Configuration options related to the dot tool
1415#---------------------------------------------------------------------------
1416
1417# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1418# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
1419# or super classes. Setting the tag to NO turns the diagrams off. Note that
1420# this option is superseded by the HAVE_DOT option below. This is only a
1421# fallback. It is recommended to install and use dot, since it yields more
1422# powerful graphs.
1423
1424CLASS_DIAGRAMS = YES
1425
1426# You can define message sequence charts within doxygen comments using the \msc
1427# command. Doxygen will then run the mscgen tool (see
1428# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the
1429# documentation. The MSCGEN_PATH tag allows you to specify the directory where
1430# the mscgen tool resides. If left empty the tool is assumed to be found in the
1431# default search path.
1432
1433MSCGEN_PATH =
1434
1435# If set to YES, the inheritance and collaboration graphs will hide
1436# inheritance and usage relations if the target is undocumented
1437# or is not a class.
1438
1439HIDE_UNDOC_RELATIONS = YES
1440
1441# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1442# available from the path. This tool is part of Graphviz, a graph visualization
1443# toolkit from AT&T and Lucent Bell Labs. The other options in this section
1444# have no effect if this option is set to NO (the default)
1445
1446HAVE_DOT = NO
1447
1448# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is
1449# allowed to run in parallel. When set to 0 (the default) doxygen will
1450# base this on the number of processors available in the system. You can set it
1451# explicitly to a value larger than 0 to get control over the balance
1452# between CPU load and processing speed.
1453
1454DOT_NUM_THREADS = 0
1455
1456# By default doxygen will write a font called FreeSans.ttf to the output
1457# directory and reference it in all dot files that doxygen generates. This
1458# font does not include all possible unicode characters however, so when you need
1459# these (or just want a differently looking font) you can specify the font name
1460# using DOT_FONTNAME. You need need to make sure dot is able to find the font,
1461# which can be done by putting it in a standard location or by setting the
1462# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory
1463# containing the font.
1464
1465DOT_FONTNAME = FreeSans.ttf
1466
1467# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs.
1468# The default size is 10pt.
1469
1470DOT_FONTSIZE = 10
1471
1472# By default doxygen will tell dot to use the output directory to look for the
1473# FreeSans.ttf font (which doxygen will put there itself). If you specify a
1474# different font using DOT_FONTNAME you can set the path where dot
1475# can find it using this tag.
1476
1477DOT_FONTPATH =
1478
1479# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
1480# will generate a graph for each documented class showing the direct and
1481# indirect inheritance relations. Setting this tag to YES will force the
1482# the CLASS_DIAGRAMS tag to NO.
1483
1484CLASS_GRAPH = YES
1485
1486# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
1487# will generate a graph for each documented class showing the direct and
1488# indirect implementation dependencies (inheritance, containment, and
1489# class references variables) of the class with other documented classes.
1490
1491COLLABORATION_GRAPH = YES
1492
1493# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
1494# will generate a graph for groups, showing the direct groups dependencies
1495
1496GROUP_GRAPHS = YES
1497
1498# If the UML_LOOK tag is set to YES doxygen will generate inheritance and
1499# collaboration diagrams in a style similar to the OMG's Unified Modeling
1500# Language.
1501
1502UML_LOOK = NO
1503
1504# If set to YES, the inheritance and collaboration graphs will show the
1505# relations between templates and their instances.
1506
1507TEMPLATE_RELATIONS = NO
1508
1509# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
1510# tags are set to YES then doxygen will generate a graph for each documented
1511# file showing the direct and indirect include dependencies of the file with
1512# other documented files.
1513
1514INCLUDE_GRAPH = YES
1515
1516# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
1517# HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1518# documented header file showing the documented files that directly or
1519# indirectly include this file.
1520
1521INCLUDED_BY_GRAPH = YES
1522
1523# If the CALL_GRAPH and HAVE_DOT options are set to YES then
1524# doxygen will generate a call dependency graph for every global function
1525# or class method. Note that enabling this option will significantly increase
1526# the time of a run. So in most cases it will be better to enable call graphs
1527# for selected functions only using the \callgraph command.
1528
1529CALL_GRAPH = NO
1530
1531# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then
1532# doxygen will generate a caller dependency graph for every global function
1533# or class method. Note that enabling this option will significantly increase
1534# the time of a run. So in most cases it will be better to enable caller
1535# graphs for selected functions only using the \callergraph command.
1536
1537CALLER_GRAPH = NO
1538
1539# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
1540# will graphical hierarchy of all classes instead of a textual one.
1541
1542GRAPHICAL_HIERARCHY = YES
1543
1544# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
1545# then doxygen will show the dependencies a directory has on other directories
1546# in a graphical way. The dependency relations are determined by the #include
1547# relations between the files in the directories.
1548
1549DIRECTORY_GRAPH = YES
1550
1551# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1552# generated by dot. Possible values are png, jpg, or gif
1553# If left blank png will be used.
1554
1555DOT_IMAGE_FORMAT = png
1556
1557# The tag DOT_PATH can be used to specify the path where the dot tool can be
1558# found. If left blank, it is assumed the dot tool can be found in the path.
1559
1560DOT_PATH =
1561
1562# The DOTFILE_DIRS tag can be used to specify one or more directories that
1563# contain dot files that are included in the documentation (see the
1564# \dotfile command).
1565
1566DOTFILE_DIRS =
1567
1568# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of
1569# nodes that will be shown in the graph. If the number of nodes in a graph
1570# becomes larger than this value, doxygen will truncate the graph, which is
1571# visualized by representing a node as a red box. Note that doxygen if the
1572# number of direct children of the root node in a graph is already larger than
1573# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note
1574# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
1575
1576DOT_GRAPH_MAX_NODES = 50
1577
1578# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
1579# graphs generated by dot. A depth value of 3 means that only nodes reachable
1580# from the root by following a path via at most 3 edges will be shown. Nodes
1581# that lay further from the root node will be omitted. Note that setting this
1582# option to 1 or 2 may greatly reduce the computation time needed for large
1583# code bases. Also note that the size of a graph can be further restricted by
1584# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
1585
1586MAX_DOT_GRAPH_DEPTH = 0
1587
1588# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
1589# background. This is disabled by default, because dot on Windows does not
1590# seem to support this out of the box. Warning: Depending on the platform used,
1591# enabling this option may lead to badly anti-aliased labels on the edges of
1592# a graph (i.e. they become hard to read).
1593
1594DOT_TRANSPARENT = NO
1595
1596# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
1597# files in one run (i.e. multiple -o and -T options on the command line). This
1598# makes dot run faster, but since only newer versions of dot (>1.8.10)
1599# support this, this feature is disabled by default.
1600
1601DOT_MULTI_TARGETS = NO
1602
1603# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1604# generate a legend page explaining the meaning of the various boxes and
1605# arrows in the dot generated graphs.
1606
1607GENERATE_LEGEND = YES
1608
1609# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1610# remove the intermediate dot files that are used to generate
1611# the various graphs.
1612
1613DOT_CLEANUP = YES
diff --git a/legacy/eio/doc/Makefile.am b/legacy/eio/doc/Makefile.am
deleted file mode 100644
index fcf2a28b46..0000000000
--- a/legacy/eio/doc/Makefile.am
+++ /dev/null
@@ -1,32 +0,0 @@
1MAINTAINERCLEANFILES = Makefile.in
2
3.PHONY: doc
4
5PACKAGE_DOCNAME = $(PACKAGE_TARNAME)-$(PACKAGE_VERSION)-doc
6
7if EFL_BUILD_DOC
8
9doc-clean:
10 rm -rf html/ latex/ man/ xml/ $(PACKAGE_DOCNAME).tar*
11
12doc: all
13 $(efl_doxygen)
14 cp $(srcdir)/img/* html/
15 rm -rf $(PACKAGE_DOCNAME).tar*
16 mkdir -p $(PACKAGE_DOCNAME)/doc
17 cp -R html/ latex/ man/ $(PACKAGE_DOCNAME)/doc
18 tar cf $(PACKAGE_DOCNAME).tar $(PACKAGE_DOCNAME)/
19 bzip2 -9 $(PACKAGE_DOCNAME).tar
20 rm -rf $(PACKAGE_DOCNAME)/
21 mv $(PACKAGE_DOCNAME).tar.bz2 $(top_builddir)
22
23clean-local: doc-clean
24
25else
26
27doc:
28 @echo "Documentation not built. Run ./configure --help"
29
30endif
31
32EXTRA_DIST = $(builddir)/Doxyfile $(wildcard $(srcdir)/img/*.*) $(srcdir)/e.css $(srcdir)/head.html $(srcdir)/foot.html
diff --git a/legacy/eio/doc/e.css b/legacy/eio/doc/e.css
deleted file mode 100644
index 8697a3a0be..0000000000
--- a/legacy/eio/doc/e.css
+++ /dev/null
@@ -1,218 +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
diff --git a/legacy/eio/doc/eio.dox.in b/legacy/eio/doc/eio.dox.in
deleted file mode 100644
index 32a97b7300..0000000000
--- a/legacy/eio/doc/eio.dox.in
+++ /dev/null
@@ -1,456 +0,0 @@
1/* EIO - EFL data type library
2 * Copyright (C) 2010 Enlightenment Developers:
3 * Cedric Bail <cedric.bail@free.fr>
4 * Vincent "caro" Torri <vtorri at univ-evry dot fr>
5 * Stephen "okra" Houston <unixtitan@gmail.com>
6 * Gustavo Sverzut Barbieri <barbieri@gmail.com>
7 *
8 * This library is free software; you can redistribute it and/or
9 * modify it under the terms of the GNU Lesser General Public
10 * License as published by the Free Software Foundation; either
11 * version 2.1 of the License, or (at your option) any later version.
12 *
13 * This library is distributed in the hope that it will be useful,
14 * but WITHOUT ANY WARRANTY; without even the implied warranty of
15 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
16 * Lesser General Public License for more details.
17 *
18 * You should have received a copy of the GNU Lesser General Public
19 * License along with this library;
20 * if not, see <http://www.gnu.org/licenses/>.
21 */
22
23/**
24 * @mainpage Eio
25 * @author Cedric Bail <cedric.bail@@free.fr>
26 * @author Stephen "okra" Houston <unixtitan@@gmail.com>
27 * @author Gustavo Sverzut Barbieri <barbieri@@gmail.com>
28 * @author Vincent "caro" Torri <vtorri at univ-evry dot fr>
29 * @author Guillaume "kuri" Friloux <guillaume.friloux@@asp64.com>
30 * @date 2010-2012
31 *
32 * @section eio_intro_sec Introduction
33 * @version @PACKAGE_VERSION@
34 *
35 * The Eio library is a library that implements an API for asynchronous
36 * input/output operation. Most operation are done in a separated thread
37 * to prevent lock. See @ref Eio_Group. Some helper to work on data
38 * received in Eio callback are also provided see @ref Eio_Helper.
39 * It is also possible to work asynchronously on Eina_File with @ref Eio_Map
40 * or on Eet_File with @ref Eio_Eet. It come with way to manipulate
41 * eXtended attribute assynchronously with @ref Eio_Xattr.
42 *
43 * This library is cross-platform and can be compiled and used on
44 * Linux, BSD, Opensolaris and Windows (XP and CE).
45 */
46
47/**
48 * @page tutorial_dir_copy eio_dir_copy() tutorial
49 *
50 * To use eio_dir_copy(), you basically need the source and
51 * destination files (or directories), and set three callbacks:
52 *
53 * @li The notification callback, which allows you to know if a file or
54 * a directory is copied, and the progress of the copy.
55 * @li The end callback, which is called when the copy is finished.
56 * @li The error callback, which is called if an error occured. You
57 * can then retrieve the error type as an errno error.
58 *
59 * @warning It is the user's duty to provide the "right target". It
60 * means that copying to '.' will copy the content directly inside '.'
61 * and not in a subdirectory.
62 *
63 * Here is a simple example:
64 *
65 * @code
66 * #include <Ecore.h>
67 * #include <Eio.h>
68 *
69 * static void
70 * _test_notify_cb(void *data, Eio_File *handler, const Eio_Progress *info)
71 * {
72 * switch (info->op)
73 * {
74 * case EIO_FILE_COPY:
75 * printf("[%s] %f%%\n", info->dest, info->percent);
76 * break;
77 * case EIO_DIR_COPY:
78 * printf("global [%li/%li] %f%%\n", info->current, info->max, info->percent);
79 * break;
80 * }
81 * }
82 *
83 * static void
84 * _test_done_cb(void *data, Eio_File *handler)
85 * {
86 * printf("copy done\n");
87 * ecore_main_loop_quit();
88 * }
89 *
90 * static void
91 * _test_error_cb(int error, Eio_File *handler, void *data)
92 * {
93 * fprintf(stderr, "error: [%s]\n", strerror(error));
94 * ecore_main_loop_quit();
95 * }
96 *
97 * int
98 * main(int argc, char **argv)
99 * {
100 * Eio_File *cp;
101 *
102 * if (argc != 3)
103 * {
104 * fprintf(stderr, "eio_cp source_file destination_file\n");
105 * return -1;
106 * }
107 *
108 * ecore_init();
109 * eio_init();
110 *
111 * cp = eio_dir_copy(argv[1], argv[2],
112 * _test_notify_cb,
113 * _test_done_cb,
114 * _test_error_cb,
115 * NULL);
116 *
117 * ecore_main_loop_begin();
118 *
119 * eio_shutdown();
120 * ecore_shutdown();
121 *
122 * return 0;
123 * }
124 * @endcode
125 */
126
127/**
128 * @page tutorial_dir_stat_ls eio_dir_stat_ls() tutorial
129 *
130 * @li The filter callback, which allow or not a file to be seen
131 * by the main loop handler. This callback run in a separated thread.
132 * @li The main callback, which receive in the main loop all the file
133 * that are allowed by the filter. If you are updating a user interface
134 * it make sense to delay the insertion a little, so you get a chance
135 * to update the canvas for a bunch of file instead of one by one.
136 * @li The end callback, which is called in the main loop when the
137 * content of the directory has been correctly scanned and all the
138 * file notified to the main loop.
139 * @li The error callback, which is called if an error occured or
140 * if the listing was cancelled during it's run. You can then retrieve
141 * the error type as an errno error.
142 *
143 * Here is a simple example that implement a stupidly simple replacement for find:
144 *
145 * @code
146 * #include <Ecore.h>
147 * #include <Eio.h>
148 *
149 * static Eina_Bool
150 * _test_filter_cb(void *data, Eio_File *handler, const Eina_File_Direct_Info *info)
151 * {
152 * fprintf(stderr, "ACCEPTING: %s\n", info->path);
153 * return EINA_TRUE;
154 * }
155 *
156 * static void
157 * _test_main_cb(void *data, Eio_File *handler, const Eina_File_Direct_Info *info)
158 * {
159 * fprintf(stderr, "PROCESS: %s\n", info->path);
160 * }
161 *
162 * static void
163 * _test_done_cb(void *data, Eio_File *handler)
164 * {
165 * printf("ls done\n");
166 * ecore_main_loop_quit();
167 * }
168 *
169 * static void
170 * _test_error_cb(void *data, Eio_File *handler, int error)
171 * {
172 * fprintf(stderr, "error: [%s]\n", strerror(error));
173 * ecore_main_loop_quit();
174 * }
175 *
176 * int
177 * main(int argc, char **argv)
178 * {
179 * Eio_File *cp;
180 *
181 * if (argc != 2)
182 * {
183 * fprintf(stderr, "eio_ls directory\n");
184 * return -1;
185 * }
186 *
187 * ecore_init();
188 * eio_init();
189 *
190 * cp = eio_dir_stat_ls(argv[1],
191 * _test_filter_cb,
192 * _test_main_cb,
193 * _test_done_cb,
194 * _test_error_cb,
195 * NULL);
196 *
197 * ecore_main_loop_begin();
198 *
199 * eio_shutdown();
200 * ecore_shutdown();
201 *
202 * return 0;
203 * }
204 *
205 * @endcode
206 */
207
208/**
209 * @page tutorial_file_ls eio_file_ls() tutorial
210 *
211 * To use eio_file_ls(), you just need to define four callbacks:
212 *
213 * @li The filter callback, which allow or not a file to be seen
214 * by the main loop handler. This callback run in a separated thread.
215 * @li The main callback, which receive in the main loop all the file
216 * that are allowed by the filter. If you are updating a user interface
217 * it make sense to delay the insertion a little, so you get a chance
218 * to update the canvas for a bunch of file instead of one by one.
219 * @li The end callback, which is called in the main loop when the
220 * content of the directory has been correctly scanned and all the
221 * file notified to the main loop.
222 * @li The error callback, which is called if an error occured or
223 * if the listing was cancelled during it's run. You can then retrieve
224 * the error type as an errno error.
225 *
226 * Here is a simple example:
227 *
228 * @code
229 * #include <Ecore.h>
230 * #include <Eio.h>
231 *
232 * static Eina_Bool
233 * _test_filter_cb(void *data, Eio_File *handler, const char *file)
234 * {
235 * fprintf(stderr, "ACCEPTING: %s\n", file);
236 * return EINA_TRUE;
237 * }
238 *
239 * static void
240 * _test_main_cb(void *data, Eio_File *handler, const char *file)
241 * {
242 * fprintf(stderr, "PROCESS: %s\n", file);
243 * }
244 *
245 * static void
246 * _test_done_cb(void *data, Eio_File *handler)
247 * {
248 * printf("ls done\n");
249 * ecore_main_loop_quit();
250 * }
251 *
252 * static void
253 * _test_error_cb(void *data, Eio_File *handler, int error)
254 * {
255 * fprintf(stderr, "error: [%s]\n", strerror(error));
256 * ecore_main_loop_quit();
257 * }
258 *
259 * int
260 * main(int argc, char **argv)
261 * {
262 * Eio_File *cp;
263 *
264 * if (argc != 2)
265 * {
266 * fprintf(stderr, "eio_ls directory\n");
267 * return -1;
268 * }
269 *
270 * ecore_init();
271 * eio_init();
272 *
273 * cp = eio_file_ls(argv[1],
274 * _test_filter_cb,
275 * _test_main_cb,
276 * _test_done_cb,
277 * _test_error_cb,
278 * NULL);
279 *
280 * ecore_main_loop_begin();
281 *
282 * eio_shutdown();
283 * ecore_shutdown();
284 *
285 * return 0;
286 * }
287 *
288 * @endcode
289 */
290
291/**
292 * @page tutorial_monitor_add eio_monitor_add() tutorial
293 *
294 * To use eio_monitor_add(), you have to define callbacks
295 * for events declared by eio.
296 * Available events are :
297 * - EIO_MONITOR_FILE_CREATED
298 * - EIO_MONITOR_FILE_DELETED
299 * - EIO_MONITOR_FILE_MODIFIED
300 * - EIO_MONITOR_FILE_CLOSED
301 * - EIO_MONITOR_DIRECTORY_CREATED
302 * - EIO_MONITOR_DIRECTORY_DELETED
303 * - EIO_MONITOR_DIRECTORY_CLOSED
304 * - EIO_MONITOR_SELF_RENAME
305 * - EIO_MONITOR_SELF_DELETED
306 *
307 * As nothing is worth an example, here it is :
308 * @code
309 * #include <Eina.h>
310 * #include <Ecore.h>
311 * #include <Eio.h>
312 *
313 * void file_modified(void *data, int type, void *event)
314 * {
315 * const char *filename = (const char *)data;
316 * printf("file %s ", filename);
317 * if( type == EIO_MONITOR_FILE_MODIFIED )
318 * printf("is being modified");
319 * else if( type == EIO_MONITOR_FILE_CLOSED )
320 * printf("is not more being modified");
321 * else printf("got unexpected changes");
322 * printf("\n");
323 * }
324 *
325 * int main(int argc, char **argv) {
326 * Eio_Monitor *monitor = NULL,
327 * *monitor2 = NULL;
328 * eio_init();
329 * const char *filename = eina_stringshare_add("/tmp/eio_notify_testfile");
330 *
331 * monitor = eio_monitor_add(filename);
332 * ecore_event_handler_add(EIO_MONITOR_FILE_MODIFIED, (Ecore_Event_Handler_Cb)file_modified, filename);
333 * ecore_event_handler_add(EIO_MONITOR_FILE_CLOSED, (Ecore_Event_Handler_Cb)file_modified, filename);
334 *
335 * ecore_main_loop_begin();
336 * eio_shutdown();
337 * eina_stringshare_del(filename);
338 * }
339 * @endcode
340 * Build the example doing :
341 * @verbatim gcc -o tutorial_monitor_add tutorial_monitor_add.c `pkg-config --libs --cflags eio ecore ecore-file eina`
342 * then create the file /tmp/eio_notify_testfile :
343 * touch /tmp/eio_notify_testfile
344 * and launch tutorial_monitor_add, and in another terminal, write into /tmp/eio_notify_testfile, doing for example :
345 * echo "test" >> /tmp/eio_notify_testfile
346 * @endverbatim
347 */
348
349/**
350 * @page tutorial_dir_direct_ls eio_dir_direct_ls() tutorial
351 *
352 * @li The filter callback, which allow or not a file to be seen
353 * by the main loop handler. This callback run in a separated thread.
354 * It also take care of getting a stat buffer needed by the main callback
355 * to display the file size.
356 * @li The main callback, which receive in the main loop all the file
357 * that are allowed by the filter. If you are updating a user interface
358 * it make sense to delay the insertion a little, so you get a chance
359 * to update the canvas for a bunch of file instead of one by one.
360 * @li The end callback, which is called in the main loop when the
361 * content of the directory has been correctly scanned and all the
362 * file notified to the main loop.
363 * @li The error callback, which is called if an error occured or
364 * if the listing was cancelled during it's run. You can then retrieve
365 * the error type as an errno error.
366 *
367 * Here is a simple example that implement a stupidly simple recursive ls that display file size:
368 *
369 * @code
370 * #include <Eina.h>
371 * #include <Ecore.h>
372 * #include <Eio.h>
373 *
374 * static Eina_Bool
375 * _test_filter_cb(void *data, Eio_File *handler, Eina_File_Direct_Info *info)
376 * {
377 * Eina_Stat *buffer;
378 * Eina_Bool isdir;
379 *
380 * isdir = info->type == EINA_FILE_DIR;
381 *
382 * buffer = malloc(sizeof (Eina_Stat));
383 * if (eina_file_statat(eio_file_container_get(handler), info, buffer))
384 * {
385 * free(buffer);
386 * return EINA_FALSE;
387 * }
388 *
389 * if (!isdir && info->type == EINA_FILE_DIR)
390 * {
391 * struct stat st;
392 * if (lstat(info->path, &st) == 0)
393 * {
394 * if (S_ISLNK(st.st_mode))
395 * info->type = EINA_FILE_LNK;
396 * }
397 * }
398 *
399 * eio_file_associate_direct_add(handler, "stat", buffer, free);
400 * fprintf(stdout, "ACCEPTING: %s\n", info->path);
401 * return EINA_TRUE;
402 * }
403 *
404 * static void
405 * _test_main_cb(void *data, Eio_File *handler, const Eina_File_Direct_Info *info)
406 * {
407 * struct stat *buffer;
408 *
409 * buffer = eio_file_associate_find(handler, "stat");
410 * fprintf(stdout, "PROCESS: %s of size %li\n", info->path, buffer->st_size);
411 * }
412 *
413 * static void
414 * _test_done_cb(void *data, Eio_File *handler)
415 * {
416 * printf("ls done\n");
417 * ecore_main_loop_quit();
418 * }
419 *
420 * static void
421 * _test_error_cb(void *data, Eio_File *handler, int error)
422 * {
423 * fprintf(stdout, "error: [%s]\n", strerror(error));
424 * ecore_main_loop_quit();
425 * }
426 *
427 * int
428 * main(int argc, char **argv)
429 * {
430 * Eio_File *cp;
431 *
432 * if (argc != 2)
433 * {
434 * fprintf(stdout, "eio_ls directory\n");
435 * return -1;
436 * }
437 *
438 * ecore_init();
439 * eio_init();
440 *
441 * cp = eio_dir_direct_ls(argv[1],
442 * _test_filter_cb,
443 * _test_main_cb,
444 * _test_done_cb,
445 * _test_error_cb,
446 * NULL);
447 *
448 * ecore_main_loop_begin();
449 *
450 * eio_shutdown();
451 * ecore_shutdown();
452 *
453 * return 0;
454 * }
455 * @endcode
456 */
diff --git a/legacy/eio/doc/foot.html b/legacy/eio/doc/foot.html
deleted file mode 100644
index 78ef911c72..0000000000
--- a/legacy/eio/doc/foot.html
+++ /dev/null
@@ -1,19 +0,0 @@
1
2 <div id="push"></div>
3 </div> <!-- #content -->
4 </div> <!-- .layout -->
5
6 </div> <!-- #container -->
7
8
9 <div id="footer">
10 <table><tr>
11 <td class="poweredby"><img src="doxygen.png"></td>
12 <td class="copyright">Copyright &copy;$year Enlightenment</td>
13 <td class="generated">Docs generated $datetime</td>
14 </tr></table>
15 </div>
16
17
18</body>
19</html>
diff --git a/legacy/eio/doc/head.html b/legacy/eio/doc/head.html
deleted file mode 100644
index b0f0a2c286..0000000000
--- a/legacy/eio/doc/head.html
+++ /dev/null
@@ -1,67 +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="pages.html">Tutorials</a></li>
50 <li><a href="group__Eio__Helper.html">Helper API</a></li>
51 <li><a href="group__Eio__Monitor.html">monitoring API</a></li>
52 <li><a href="group__Eio__Xattr.html">eXtended attribute API</a></li>
53 <li><a href="group__Eio__Eet.html">EET API</a></li>
54 <li><a href="group__Eio__Map.html">reading file API</a></li>
55 <li><a href="group__Eio__Group.html">Reference API</a></li>
56 <li class="current"><a href="index.html">Main Page</a></li>
57 </ul>
58 </div>
59 </div>
60
61
62 <div class="clear"></div>
63</div>
64</div>
65
66<div id="content">
67<div class="layout">
diff --git a/legacy/eio/doc/img/e.png b/legacy/eio/doc/img/e.png
deleted file mode 100644
index b3884a5cbc..0000000000
--- a/legacy/eio/doc/img/e.png
+++ /dev/null
Binary files differ
diff --git a/legacy/eio/doc/img/edoxy.css b/legacy/eio/doc/img/edoxy.css
deleted file mode 100644
index 3caf7a9736..0000000000
--- a/legacy/eio/doc/img/edoxy.css
+++ /dev/null
@@ -1,483 +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;