Ops! I guess it was a problem when we split ecore_evas into modules, these events should be, indeed, defined in libecore_evas.so, not in the module.
I can't commit a fix right now, could someone move the EAPI declaration and ecore_event_new() attribution to ecore_evas.c? On Fri, Jan 3, 2014 at 9:52 AM, Albin Tonnerre <[email protected]> wrote: > Hi, > > I noticed something strange while working on the Debian packaging for > EFL 1.8: the two symbols mentionned in the title are no longer present > in libecore-evas.so but are apparently part of the API: they're > exported in Ecore_Evas.h > > Those two variables seem to have been moved to a module by commit > 85f8163c3ee5b5d776d94c70ff9fbc667a615b2a , but as far a I can tell > moving the actual symbols in an Ecore_Evas module effectively breaks > the ABI: any library or application that used this variable will fail > to load because the symbols can't be resolved. Similarly, it's not > possible to use them in an application since the symbol can't be > resolved at link time. > > Does anyone know what to make of this? > > Thanks, > -- > Albin -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -------------------------------------- MSN: [email protected] Skype: gsbarbieri Mobile: +55 (19) 9225-2202 ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
