On 25/01/15 02:16, Carsten Haitzler (The Rasterman) wrote:
> On Sat, 24 Jan 2015 18:53:15 + Tom Hacohen said:
>
>> Ask raster?
> yeah. only the author can do this. eo stuff changed around after i wrote this
> post - so yes - it has details that are off (but general gist is correct)
> someone
On Sat, 24 Jan 2015 18:53:15 + Tom Hacohen said:
> Ask raster?
yeah. only the author can do this. eo stuff changed around after i wrote this
post - so yes - it has details that are off (but general gist is correct)
someone summarize what they want me to change so i dont have to spend the tim
Ask raster?
On 23/01/15 19:48, Andrew Williams wrote:
> Hi Tom,
>
> Thanks very much, it was indeed EFL_EO_API_SUPPORT.
> THe page I used this time was
> https://phab.enlightenment.org/phame/live/1//post/yet_another_c_object_model_but_better/
> Do you know if I can edit this post to update it for
Hi Tom,
Thanks very much, it was indeed EFL_EO_API_SUPPORT.
THe page I used this time was
https://phab.enlightenment.org/phame/live/1//post/yet_another_c_object_model_but_better/
Do you know if I can edit this post to update it for the current state
of things?
Many thanks for your help.
Andrew
Really hard to see among all the warnings. :(
I'm not sure what you've done, but you need EFL_BETA_API_SUPPORT (which
you have) and EFL_EO_API_SUPPORT both defined before the inclusion of
the other headers.
As for the exact specifics of how to use .eo.c and .eo.h see one of the
numerous exampl
Hi,
Sorry to bug folk on what's probably simple but I can't figure what's up
with my attempt to port elm_code to an elm_object through eo.
I've got a pretty skeleton file (as you can see from the warnings) but
can anyone figure what I might be missing? The build setup should have
al dependenci
