\chapter{e3}

\section{Draft}

e3 will be dedicated to building, testing and generating docs from the
EFL source base.

e3 will do a nightly build of all EFL based library and application
considered stable or useful (this include from eina to e itself, plus
ethumb, emotion, elementary, entrance, python and javascript bindings,
editje, expedite, edje\_viewer, eyelight, eupnp, and also some module
from E-MODULES-EXTRA). The report will be available online for this
build and previous ones(indexed by the svn revision number). If the
build failed for any of this module a mail will be sent to the
build ML.

When the build is done, e3 will generate docs for all successful built
libraries and provide them (look at the current docs.enlightenment.org/auto
for an up-to-date list). Again, if the doc didn't generate for any of
this project, a mail will be sent to the build ML.

After that, if eina or eet change, e3 rebuilds them with --enable-tests
and --enable-coverage . Then run make coverage and expose the html
result. If the coverage is reduced compared to a previous built, or if the
coverage didn't run, a mail will be sent to the build ML.

If anything in eina or evas did change, e3 rebuilds them with all
optimisation turned on, and run expedite benchmark with software backend
and gl backend (I will provide a server with NVIDIA graphic card so we
can do real gl benchmark). The result should be stored somewhere for
each test (would be nice to have a beautiful graph, with score test and
svn revision). If expedite crashed or if the result were bad, then a
mail will be sent to the build ML. It would be cool, if multiple
profile for evas could be tested, with pipe renderer, with/without sse
or mmx backend and so on.

A complete build of the previous library and apps should be done with
LLVM static analyser ( http://local.profusion.mobi:8081/
~lfelipe/output-efl/ and http://clang-analyzer.llvm.org/ should provide
information on this build). A report should be put online. No need to
send a mail for this one if something goes wrong (It's still highly
experimental).

For all test results, a unique small bziped tarball will be put online
so people can work on fixing this nasty little error offline.

That's only for a linux build, but as we want to support more target, it
would be great if we could setup a cross compiler (just build) for
windows and perhaps macosX, and if we could build, thanks to a VM, on
OpenBSD and FreeBSD all the base libraries and run eina make check in this
VM. If someone donate a windows licence or a Mac OS X licence, we could
do the same. Of course, if something goes wrong, e3 sends a mail to
Vincent\^Wthe build ML :-)

I will ensure that e3 will have a 68GB SAS harddrive and 4GB of RAM, so
that we could build all the EFL with make -j :-)

Hardware temp will have to be monitored as we don't know how the
NVidia GT 8800 will do when expedite -e gl run. If things goes wrong, we
need to kill expedite.

