maybe you can add configure output too at the end of configure.ac Vincent
On Wed, 16 Sep 2009, Enlightenment SVN wrote: > Log: > enable "make doc", improve doxygen support for client library. > > Some methods are missing and the in-process thumbnail needs to be > done, the documentation is almost the same as the client, so I really > appreciate someone else do it :-) > > > Author: barbieri > Date: 2009-09-16 23:08:10 -0700 (Wed, 16 Sep 2009) > New Revision: 42541 > > Added: > trunk/ethumb/doc/ trunk/ethumb/doc/Doxyfile trunk/ethumb/doc/Makefile.am > trunk/ethumb/doc/e.css trunk/ethumb/doc/foot.html trunk/ethumb/doc/head.html > trunk/ethumb/doc/img/ trunk/ethumb/doc/img/e.png > trunk/ethumb/doc/img/edoxy.css trunk/ethumb/doc/img/foot_bg.png > trunk/ethumb/doc/img/head_bg.png trunk/ethumb/doc/img/menu_bg.png > trunk/ethumb/doc/img/menu_bg_current.png > trunk/ethumb/doc/img/menu_bg_hover.png trunk/ethumb/doc/img/menu_bg_last.png > trunk/ethumb/doc/img/menu_bg_unsel.png trunk/ethumb/m4/efl_doxygen.m4 > Modified: > trunk/ethumb/INSTALL trunk/ethumb/Makefile.am trunk/ethumb/autogen.sh > trunk/ethumb/configure.ac trunk/ethumb/m4/Makefile.am > trunk/ethumb/src/lib/client/Ethumb_Client.c > trunk/ethumb/src/lib/client/Ethumb_Client.h trunk/ethumb/src/tests/ > > Modified: trunk/ethumb/INSTALL > =================================================================== > --- trunk/ethumb/INSTALL 2009-09-17 05:41:23 UTC (rev 42540) > +++ trunk/ethumb/INSTALL 2009-09-17 06:08:10 UTC (rev 42541) > @@ -1,16 +1,19 @@ > Installation Instructions > ************************* > > -Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free > -Software Foundation, Inc. > +Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005, > +2006, 2007, 2008 Free Software Foundation, Inc. > > -This file is free documentation; the Free Software Foundation gives > + This file is free documentation; the Free Software Foundation gives > unlimited permission to copy, distribute and modify it. > > Basic Installation > ================== > > -These are generic installation instructions. > + Briefly, the shell commands `./configure; make; make install' should > +configure, build, and install this package. The following > +more-detailed instructions are generic; see the `README' file for > +instructions specific to this package. > > The `configure' shell script attempts to guess correct values for > various system-dependent variables used during compilation. It uses > @@ -23,9 +26,9 @@ > > It can also use an optional file (typically called `config.cache' > and enabled with `--cache-file=config.cache' or simply `-C') that saves > -the results of its tests to speed up reconfiguring. (Caching is > +the results of its tests to speed up reconfiguring. Caching is > disabled by default to prevent problems with accidental use of stale > -cache files.) > +cache files. > > If you need to do unusual things to compile the package, please try > to figure out how `configure' could check whether to do them, and mail > @@ -35,20 +38,17 @@ > may remove or edit it. > > The file `configure.ac' (or `configure.in') is used to create > -`configure' by a program called `autoconf'. You only need > -`configure.ac' if you want to change it or regenerate `configure' using > -a newer version of `autoconf'. > +`configure' by a program called `autoconf'. You need `configure.ac' if > +you want to change it or regenerate `configure' using a newer version > +of `autoconf'. > > The simplest way to compile this package is: > > 1. `cd' to the directory containing the package's source code and type > - `./configure' to configure the package for your system. If you're > - using `csh' on an old version of System V, you might need to type > - `sh ./configure' instead to prevent `csh' from trying to execute > - `configure' itself. > + `./configure' to configure the package for your system. > > - Running `configure' takes awhile. While running, it prints some > - messages telling which features it is checking for. > + Running `configure' might take a while. While running, it prints > + some messages telling which features it is checking for. > > 2. Type `make' to compile the package. > > @@ -67,42 +67,57 @@ > all sorts of other programs in order to regenerate files that came > with the distribution. > > + 6. Often, you can also type `make uninstall' to remove the installed > + files again. > + > Compilers and Options > ===================== > > -Some systems require unusual options for compilation or linking that the > -`configure' script does not know about. Run `./configure --help' for > -details on some of the pertinent environment variables. > + Some systems require unusual options for compilation or linking that > +the `configure' script does not know about. Run `./configure --help' > +for details on some of the pertinent environment variables. > > You can give `configure' initial values for configuration parameters > by setting variables in the command line or in the environment. Here > is an example: > > - ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix > + ./configure CC=c99 CFLAGS=-g LIBS=-lposix > > *Note Defining Variables::, for more details. > > Compiling For Multiple Architectures > ==================================== > > -You can compile the package for more than one kind of computer at the > + You can compile the package for more than one kind of computer at the > same time, by placing the object files for each architecture in their > -own directory. To do this, you must use a version of `make' that > -supports the `VPATH' variable, such as GNU `make'. `cd' to the > +own directory. To do this, you can use GNU `make'. `cd' to the > directory where you want the object files and executables to go and run > the `configure' script. `configure' automatically checks for the > source code in the directory that `configure' is in and in `..'. > > - If you have to use a `make' that does not support the `VPATH' > -variable, you have to compile the package for one architecture at a > -time in the source code directory. After you have installed the > -package for one architecture, use `make distclean' before reconfiguring > -for another architecture. > + With a non-GNU `make', it is safer to compile the package for one > +architecture at a time in the source code directory. After you have > +installed the package for one architecture, use `make distclean' before > +reconfiguring for another architecture. > > + On MacOS X 10.5 and later systems, you can create libraries and > +executables that work on multiple system types--known as "fat" or > +"universal" binaries--by specifying multiple `-arch' options to the > +compiler but only a single `-arch' option to the preprocessor. Like > +this: > + > + ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ > + CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ > + CPP="gcc -E" CXXCPP="g++ -E" > + > + This is not guaranteed to produce working output in all cases, you > +may have to build one architecture at a time and combine the results > +using the `lipo' tool if you have problems. > + > Installation Names > ================== > > -By default, `make install' installs the package's commands under > + By default, `make install' installs the package's commands under > `/usr/local/bin', include files under `/usr/local/include', etc. You > can specify an installation prefix other than `/usr/local' by giving > `configure' the option `--prefix=PREFIX'. > @@ -125,7 +140,7 @@ > Optional Features > ================= > > -Some packages pay attention to `--enable-FEATURE' options to > + Some packages pay attention to `--enable-FEATURE' options to > `configure', where FEATURE indicates an optional part of the package. > They may also pay attention to `--with-PACKAGE' options, where PACKAGE > is something like `gnu-as' or `x' (for the X Window System). The > @@ -137,14 +152,36 @@ > you can use the `configure' options `--x-includes=DIR' and > `--x-libraries=DIR' to specify their locations. > > +Particular systems > +================== > + > + On HP-UX, the default C compiler is not ANSI C compatible. If GNU > +CC is not installed, it is recommended to use the following options in > +order to use an ANSI C compiler: > + > + ./configure CC="cc -Ae" > + > +and if that doesn't work, install pre-built binaries of GCC for HP-UX. > + > + On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot > +parse its `<wchar.h>' header file. The option `-nodtk' can be used as > +a workaround. If GNU CC is not installed, it is therefore recommended > +to try > + > + ./configure CC="cc" > + > +and if that doesn't work, try > + > + ./configure CC="cc -nodtk" > + > Specifying the System Type > ========================== > > -There may be some features `configure' cannot figure out automatically, > -but needs to determine by the type of machine the package will run on. > -Usually, assuming the package is built to be run on the _same_ > -architectures, `configure' can figure that out, but if it prints a > -message saying it cannot guess the machine type, give it the > + There may be some features `configure' cannot figure out > +automatically, but needs to determine by the type of machine the package > +will run on. Usually, assuming the package is built to be run on the > +_same_ architectures, `configure' can figure that out, but if it prints > +a message saying it cannot guess the machine type, give it the > `--build=TYPE' option. TYPE can either be a short name for the system > type, such as `sun4', or a canonical name which has the form: > > @@ -170,9 +207,9 @@ > Sharing Defaults > ================ > > -If you want to set default values for `configure' scripts to share, you > -can create a site shell script called `config.site' that gives default > -values for variables like `CC', `cache_file', and `prefix'. > + If you want to set default values for `configure' scripts to share, > +you can create a site shell script called `config.site' that gives > +default values for variables like `CC', `cache_file', and `prefix'. > `configure' looks for `PREFIX/share/config.site' if it exists, then > `PREFIX/etc/config.site' if it exists. Or, you can set the > `CONFIG_SITE' environment variable to the location of the site script. > @@ -181,7 +218,7 @@ > Defining Variables > ================== > > -Variables not defined in a site shell script can be set in the > + Variables not defined in a site shell script can be set in the > environment passed to `configure'. However, some packages may run > configure again during the build, and the customized values of these > variables may be lost. In order to avoid this problem, you should set > @@ -190,22 +227,30 @@ > ./configure CC=/usr/local2/bin/gcc > > causes the specified `gcc' to be used as the C compiler (unless it is > -overridden in the site shell script). Here is a another example: > +overridden in the site shell script). > > - /bin/bash ./configure CONFIG_SHELL=/bin/bash > +Unfortunately, this technique does not work for `CONFIG_SHELL' due to > +an Autoconf bug. Until the bug is fixed you can use this workaround: > > -Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent > -configuration-related scripts to be executed by `/bin/bash'. > + CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash > > `configure' Invocation > ====================== > > -`configure' recognizes the following options to control how it operates. > + `configure' recognizes the following options to control how it > +operates. > > `--help' > `-h' > - Print a summary of the options to `configure', and exit. > + Print a summary of all of the options to `configure', and exit. > > +`--help=short' > +`--help=recursive' > + Print a summary of the options unique to this package's > + `configure', and exit. The `short' variant lists options used > + only in the top level, while the `recursive' variant lists options > + also present in any nested packages. > + > `--version' > `-V' > Print the version of Autoconf used to generate the `configure' > @@ -231,6 +276,16 @@ > Look for the package's source code in directory DIR. Usually > `configure' can determine that directory automatically. > > +`--prefix=DIR' > + Use DIR as the installation prefix. *Note Installation Names:: > + for more details, including other options available for fine-tuning > + the installation locations. > + > +`--no-create' > +`-n' > + Run the configure checks, but stop before creating any output > + files. > + > `configure' also accepts some other, not widely useful, options. Run > `configure --help' for more details. > > > Modified: trunk/ethumb/Makefile.am > =================================================================== > --- trunk/ethumb/Makefile.am 2009-09-17 05:41:23 UTC (rev 42540) > +++ trunk/ethumb/Makefile.am 2009-09-17 06:08:10 UTC (rev 42541) > @@ -29,6 +29,12 @@ > > endif > > -SUBDIRS = m4 src data > +SUBDIRS = m4 src data doc > > ACLOCAL_AMFLAGS = -I m4 > + > +.PHONY: doc > + > +doc: > + @echo "entering doc/" > + $(MAKE) -C doc doc > > Modified: trunk/ethumb/autogen.sh > =================================================================== > --- trunk/ethumb/autogen.sh 2009-09-17 05:41:23 UTC (rev 42540) > +++ trunk/ethumb/autogen.sh 2009-09-17 06:08:10 UTC (rev 42541) > @@ -1,14 +1,7 @@ > #!/bin/sh > > -rm -rf autom4te.cache > -rm -f aclocal.m4 ltmain.sh > +autoreconf -f -i > > -echo "Running aclocal..." ; aclocal $ACLOCAL_FLAGS -I m4 || exit 1 > -echo "Running autoheader..." ; autoheader || exit 1 > -echo "Running autoconf..." ; autoconf || exit 1 > -echo "Running libtoolize..." ; (libtoolize --copy --automake || glibtoolize > --automake) || exit 1 > -echo "Running automake..." ; automake --add-missing --copy --gnu || exit 1 > - > if [ -z "$NOCONFIGURE" ]; then > ./configure "$@" > fi > > Modified: trunk/ethumb/configure.ac > =================================================================== > --- trunk/ethumb/configure.ac 2009-09-17 05:41:23 UTC (rev 42540) > +++ trunk/ethumb/configure.ac 2009-09-17 06:08:10 UTC (rev 42541) > @@ -40,6 +40,8 @@ > AS_AC_EXPAND(PLUGINSDIR, $pluginsdir) > AC_DEFINE_UNQUOTED(PLUGINSDIR, ["$PLUGINSDIR"], [Where plugins are > installed.]) > > +EFL_CHECK_DOXYGEN([build_doc="yes"], [build_doc="no"]) > + > PKG_CHECK_MODULES(EINA, [eina-0]) > PKG_CHECK_MODULES(EVAS, [evas]) > PKG_CHECK_MODULES(ECORE, [ecore]) > @@ -110,4 +112,5 @@ > data/Makefile > data/frames/Makefile > m4/Makefile > +doc/Makefile > ]) > > > Property changes on: trunk/ethumb/doc > ___________________________________________________________________ > Name: svn:ignore > + Makefile > Makefile.in > html > man > latex > *~ > > > Added: trunk/ethumb/doc/Doxyfile > > Added: trunk/ethumb/doc/Makefile.am > > Added: trunk/ethumb/doc/e.css > > Added: trunk/ethumb/doc/foot.html > > Added: trunk/ethumb/doc/head.html > > Added: trunk/ethumb/doc/img/e.png > > > Property changes on: trunk/ethumb/doc/img/e.png > ___________________________________________________________________ > Name: svn:mime-type > + image/png > > Added: trunk/ethumb/doc/img/edoxy.css > > Added: trunk/ethumb/doc/img/foot_bg.png > > > Property changes on: trunk/ethumb/doc/img/foot_bg.png > ___________________________________________________________________ > Name: svn:mime-type > + image/png > > Added: trunk/ethumb/doc/img/head_bg.png > > > Property changes on: trunk/ethumb/doc/img/head_bg.png > ___________________________________________________________________ > Name: svn:mime-type > + image/png > > Added: trunk/ethumb/doc/img/menu_bg.png > > > Property changes on: trunk/ethumb/doc/img/menu_bg.png > ___________________________________________________________________ > Name: svn:mime-type > + image/png > > Added: trunk/ethumb/doc/img/menu_bg_current.png > > > Property changes on: trunk/ethumb/doc/img/menu_bg_current.png > ___________________________________________________________________ > Name: svn:mime-type > + image/png > > Added: trunk/ethumb/doc/img/menu_bg_hover.png > > > Property changes on: trunk/ethumb/doc/img/menu_bg_hover.png > ___________________________________________________________________ > Name: svn:mime-type > + image/png > > Added: trunk/ethumb/doc/img/menu_bg_last.png > > > Property changes on: trunk/ethumb/doc/img/menu_bg_last.png > ___________________________________________________________________ > Name: svn:mime-type > + image/png > > Added: trunk/ethumb/doc/img/menu_bg_unsel.png > > > Property changes on: trunk/ethumb/doc/img/menu_bg_unsel.png > ___________________________________________________________________ > Name: svn:mime-type > + image/png > > Modified: trunk/ethumb/m4/Makefile.am > =================================================================== > --- trunk/ethumb/m4/Makefile.am 2009-09-17 05:41:23 UTC (rev 42540) > +++ trunk/ethumb/m4/Makefile.am 2009-09-17 06:08:10 UTC (rev 42541) > @@ -5,4 +5,5 @@ > lib-prefix.m4 \ > progtest.m4 \ > as-expand.m4 \ > - ac-modules.m4 > + ac-modules.m4 \ > + efl_doxygen.m4 > > Added: trunk/ethumb/m4/efl_doxygen.m4 > > Modified: trunk/ethumb/src/lib/client/Ethumb_Client.c > =================================================================== > --- trunk/ethumb/src/lib/client/Ethumb_Client.c 2009-09-17 05:41:23 UTC > (rev 42540) > +++ trunk/ethumb/src/lib/client/Ethumb_Client.c 2009-09-17 06:08:10 UTC > (rev 42541) > @@ -1,6 +1,9 @@ > /** > * @file > * > + * This is the client-server thumbnail library, see @ref > + * tutorial_ethumb_client. > + * > * Copyright (C) 2009 by ProFUSION embedded systems > * > * This program is free software; you can redistribute it and/or modify it > @@ -19,7 +22,46 @@ > * USA. > * > * @author Rafael Antognolli <[email protected]> > + * @author Gustavo Sverzut Barbieri <[email protected]> > */ > + > +/** > + * @page tutorial_ethumb_client Client-Server Thumbnailing Tutorial > + * > + * @section tutorial_ethumb_client_intro Introduction > + * > + * Ethumb provides both in process and client-server generation > + * methods. The advantage of the client-server method is that current > + * process will not do the heavy operations that may block, stopping > + * animations and other user interactions. Instead the client library > + * will configure a local #Ethumb instance and mirrors/controls a > + * remote process using DBus. The simple operations like most setters > + * and getters as well as checking for thumbnail existence > + * (ethumb_client_thumb_exists()) is done locally, while expensive > + * (ethumb_client_generate()) are done on server and then reported > + * back to application when it is finished (both success or failure). > + * > + * @section tutorial_ethumb_client_connect Connecting to Server > + * > + * TODO > + * > + * @section tutorial_ethumb_client_generate Requesting Thumbnail Generation > + * > + * TODO > + * > + * @section tutorial_ethumb_client_setup Setup Extra Thumbnail Parameters > + * > + * TODO > + * > + * @section tutorial_ethumb_client_server_died Handle Server Disconnection > + * > + * TODO > + */ > + > +/** > + * @cond LOCAL > + */ > + > #ifdef HAVE_CONFIG_H > #include "config.h" > #endif > @@ -417,6 +459,10 @@ > _ethumb_client_report_connect(client, 0); > } > > +/** > + * @endcond > + */ > + > EAPI int > ethumb_client_init(void) > { > @@ -676,6 +722,10 @@ > client->die.free_data = free_data; > } > > +/** > + * @cond LOCAL > + */ > + > static void > _ethumb_client_ethumb_setup_cb(void *data, DBusMessage *msg, DBusError *error) > { > @@ -735,6 +785,10 @@ > } > > /** > + * @endcond > + */ > + > +/** > * Send setup to server. > * > * This method is called automatically by ethumb_client_generate() if > @@ -769,6 +823,9 @@ > dbus_message_iter_init_append(msg, &iter); > dbus_message_iter_open_container(&iter, DBUS_TYPE_ARRAY, "{sv}", &aiter); > > +/** > + * @cond LOCAL > + */ > #define _open_variant_iter(str_entry, str_type, end_iter) \ > entry = str_entry; \ > dbus_message_iter_open_container(&aiter, DBUS_TYPE_DICT_ENTRY, NULL, > &diter); \ > @@ -779,6 +836,9 @@ > #define _close_variant_iter(end_iter) \ > dbus_message_iter_close_container(&diter, &end_iter); \ > dbus_message_iter_close_container(&aiter, &diter); > +/** > + * @endcond > + */ > > /* starting array elements */ > > @@ -880,6 +940,10 @@ > dbus_message_unref(msg); > } > > +/** > + * @cond LOCAL > + */ > + > static void > _ethumb_client_generated_cb(void *data, DBusMessage *msg) > { > @@ -1057,6 +1121,9 @@ > pending->free_data(pending->data); > free(pending); > } > +/** > + * @endcond > + */ > > /** > * Ask server to cancel generation of thumbnail. > @@ -1154,6 +1221,9 @@ > dbus_message_unref(msg); > } > > +/** > + * @cond LOCAL > + */ > static void > _ethumb_client_queue_clear_cb(void *data, DBusMessage *msg __UNUSED__, > DBusError *error __UNUSED__) > { > @@ -1161,6 +1231,9 @@ > > client->pending_clear = NULL; > } > +/** > + * @endcond > + */ > > /** > * Ask server to cancel generation of all thumbnails. > > Modified: trunk/ethumb/src/lib/client/Ethumb_Client.h > =================================================================== > --- trunk/ethumb/src/lib/client/Ethumb_Client.h 2009-09-17 05:41:23 UTC > (rev 42540) > +++ trunk/ethumb/src/lib/client/Ethumb_Client.h 2009-09-17 06:08:10 UTC > (rev 42541) > @@ -37,10 +37,64 @@ > extern "C" { > #endif > > +/** > + * @defgroup Ethumb_Client Client > + * > + * @{ > + */ > + > +/** > + * @brief client handle. > + * > + * The client handle is created by ethumb_client_connect() and > + * destroyed by ethumb_client_disconnect(). The connection and > + * requests are asynchronous and callbacks should be used to report > + * both success and failure of calls. > + */ > typedef struct _Ethumb_Client Ethumb_Client; > + > +/** > + * @brief reports results of ethumb_client_connect() > + * > + * @param data extra context given to ethumb_client_connect(). > + * @param client handle of the current connection to server. > + * @param success #EINA_TRUE if connected or #EINA_FALSE if it was not > possible. > + */ > typedef void (*Ethumb_Client_Connect_Cb)(void *data, Ethumb_Client *client, > Eina_Bool success); > + > +/** > + * @brief reports server connection ended. > + * > + * Functions of this type may be called if they are set with > + * ethumb_client_on_server_die_callback_set(). > + * > + * @param data extra context given to > ethumb_client_on_server_die_callback_set(). > + * @param client handle of the current connection to server. > + */ > typedef void (*Ethumb_Client_Die_Cb)(void *data, Ethumb_Client *client); > + > +/** > + * @brief reports results of ethumb_client_generate(). > + * > + * @param data extra context given to ethumb_client_generate(). > + * @param client handle of the current connection to server. > + * @param id identifier returned by ethumb_client_generate(). > + * @param file path set with ethumb_client_file_set(). > + * @param key value set with ethumb_client_file_set() or #NULL. > + * @param thumb_path where thumbnail was stored, either set with > + * ethumb_client_thumb_path_set() or automatically calculated > + * using parameters. > + * @param thumb_key key inside thumb_path where thumbnail was stored or > #NULL. > + * @param success #EINA_TRUE if generated or #EINA_FALSE on errors. > + */ > typedef void (*Ethumb_Client_Generate_Cb)(void *data, Ethumb_Client *client, > int id, const char *file, const char *key, const char *thumb_path, const char > *thumb_key, Eina_Bool success); > + > +/** > + * @brief reports results of ethumb_client_generate_cancel() > + * > + * @param data extra context given to ethumb_client_generate_cancel() > + * @param client handle of the current connection to server. > + */ > typedef void (*Ethumb_Client_Generate_Cancel_Cb)(void *data, Eina_Bool > success); > > EAPI int ethumb_client_init(void); > @@ -88,6 +142,11 @@ > EAPI void ethumb_client_generate_cancel(Ethumb_Client *client, int id, > Ethumb_Client_Generate_Cancel_Cb cancel_cb, const void *data, Eina_Free_Cb > free_data); > EAPI void ethumb_client_generate_cancel_all(Ethumb_Client *client); > > +/** > + * @} > + */ > + > + > #ifdef __cplusplus > } > #endif > > > Property changes on: trunk/ethumb/src/tests > ___________________________________________________________________ > Name: svn:ignore > - Makefile > Makefile.in > *~ > *.o > *.a > *.so > *.la > .libs > .deps > > + Makefile > Makefile.in > *~ > *.o > *.a > *.so > *.la > .libs > .deps > ethumb_dbus > > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > enlightenment-svn mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-svn > > ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
