It was seen at the time that Evas_Core was not supposed (only Evas Canvas) to be used by bindings and be an implementation detail only. I think this was true because elementary was to be seen as the high-level API. Since implementers will be using Evas directly, then this may need to change. Shouldn't Evas be Eolized then?

I already have this working at present in my citest branch; running make examples in the efl tree automatically updates the submodule and builds all the examples using the (provided) raw makefiles. The examples build is roughly 30x faster on my local machine now.

Note: src/bin/ethumb/* is just a example.