| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
This patch adds 'eolian_cxx' -- a C++ bindings generator --
to the EFL tree. Eolian Cxx uses Eolian API to read .eo files and generate
.eo.hh. It relies/depends on Eo Cxx and Eina Cxx (both non-generated
bindings).
src/bin/eolian_cxx: The eolian_cxx program.
src/lib/eolian_cxx: A header-only library that implements the C++ code
generation that binds the .eo classes.
=Examples=
src/examples/eolian_cxx/eolian_cxx_simple_01.cc: The simplest example,
it just uses some "dummy" generated C++ classes.
src/examples/eolian_cxx/eolian_cxx_inherit_01.cc: Illustrates how
pure C++ classes inherit from .eo generated classes.
src/examples/evas/evas_cxx_rectangle.cc: More realistic example using
the generated bindings Evas Cxx. Still a bit shallow because we don't
have full fledged .eo descriptions yet, but will be improved.
=Important=
The generated code is not supported and not a stable API/ABI. It is
here to gather people interest and get review before we set things in
stone for release 1.11.
@feature
Reviewers: cedric, smohanty, raster, stefan_schmidt
CC: felipealmeida, JackDanielZ, cedric, stefan
Differential Revision: https://phab.enlightenment.org/D805
Signed-off-by: Cedric Bail <cedric.bail@free.fr>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The first object that we generate with Eolian is Evas_Line, as it is a
simple one.
Two files are generated during build:
- the .eo.c contains the APIs definitions invoking Eo, the Eo functions
extracting the parameters and calling the hand written functions and
Eo structures to define the objects. These hand written functions are
located in e.g evas_object_line.c.
- the .eo.h contains the APIs and Eo prototyes.
We will continue with the other objects. If you note something wrong,
please update us asap:
daniel.zaoui@samsung.com
yossi.kantor@samsung.com
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
* efl.m4: add support for xterm-256color and fix display for the bsd echo. Fix autotools issue (present on Ubuntu also, but better handled).
* doc/Makefile.am: bsd echo may not handle -n option in sh
Reviewers: cedric
CC: cedric, seoz
Differential Revision: https://phab.enlightenment.org/D329
|
| |
|
|
|
|
|
|
| |
This is taken verbatim from the linux kernel .gitignore
Signed-off-by: Eduardo Lima (Etrunko) <eduardo.lima@intel.com>
|
|
|
|
| |
Signed-off-by: Eduardo Lima (Etrunko) <eduardo.lima@intel.com>
|
| |
|
|
|
|
| |
Signed-off-by: Eduardo Lima (Etrunko) <eduardo.lima@intel.com>
|
|
|
|
|
| |
* ned to replicate changes in other .pc.in files
* need to replicate changes in other E*.h installed header files
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
git grep -l edbus2 | while read f; do sed -i 's/edbus2/eldbus/g' "$f"; done
find . -name '*edbus2*' -exec rename edbus2 eldbus {} \;
git grep -l "EDBUS" | while read f; do sed -i 's/EDBUS/ELDBUS/g' "$f"; done
git grep -l "EDBus" | while read f; do sed -i 's/EDBus/Eldbus/g' "$f"; done
git grep -l "edbus (v2)" | while read f; do sed -i 's/edbus (v2)/eldbus/g' "$f"; done
git grep -l "Edbus" | while read f; do sed -i 's/Edbus/Eldbus/g' "$f"; done
git grep -l "edbus" | while read f; do sed -i 's/edbus/eldbus/g' "$f"; done
find . -name '*edbus*' -exec rename edbus eldbus {} \;
find . -name '*EDBus*' -exec rename EDBus Eldbus {} \;
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
We can do pretty graphs with jenkins about our unit tests. But we
need the check xml output for that. Enabling it in all suites.
|
| |
|
| |
|
|
|
|
| |
SVN revision: 83541
|
|
|
|
| |
SVN revision: 82904
|
|
|
|
|
|
|
|
|
| |
Right now this contains only 2 tests, for checking if
init/shutdown works correctly.
SVN revision: 82842
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of just making our own "check-local" and calling the binaries
ourselves, just append them into "TESTS" variable. Then they run after
all check_PROGRAMS are compiled.
The reasons for changing are:
1) If we change the test and call "make check" the test is not
compiled again -- and the only way to compile it is to "make clean".
2) There's no need to reinvent the wheel here.
With a recent version of Automake, the test output is redirected to log
files. This is good but unexpected for whom was used to the previous
way. So, be warned.
SVN revision: 82841
|
|
|
|
| |
SVN revision: 82840
|
|
|
|
| |
SVN revision: 82778
|
|
|
|
| |
SVN revision: 82575
|
|
|
|
| |
SVN revision: 82476
|
|
|
|
|
|
|
|
| |
Patch by: José Roberto de Souza <zehortigoza@profusion.mobi>
SVN revision: 82214
|
|
|
|
| |
SVN revision: 82151
|
|
|
|
|
|
| |
Signed-off-by: Mike McCormack <mikem@atratus.org>
SVN revision: 81892
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After agreement in the mail list, core developers agree to remove this
engine that was not being supported for a long time.
Given that most operations Evas uses are not accelerated in DirectFB,
or at least hardware that exclusively supports DirectFB, it's better
for those people to just use Evas/Ecore software (buffer) rendering
and expose DirectFB's framebuffer as destination surface.
SVN revision: 80232
|
|
|
|
| |
SVN revision: 80132
|
|
|
|
|
|
|
| |
Instead of listing every single .dirstamp path we could just use a wildcard.
Do the same for the .gcnocoverage files.
SVN revision: 79028
|
|
|
|
| |
SVN revision: 78962
|
|
|
|
| |
SVN revision: 78949
|
|
|
|
| |
SVN revision: 77801
|
|
Signed-off-by: Mike McCormack <mikem@atratus.org>
SVN revision: 77636
|