On Mon, Nov 7, 2016 at 3:43 AM, Jean-Philippe André <[email protected]> wrote: > Hi, > > On 4 November 2016 at 20:56, Felipe Magno de Almeida < > [email protected]> wrote: > >> On Fri, Nov 4, 2016 at 9:49 AM, Vincent Torri <[email protected]> >> wrote: >> > On Fri, Nov 4, 2016 at 11:10 AM, Mykyta Biliavskyi >> > <[email protected]> wrote: >> >> Hello. >> >> >> >> I think that code, that uses pipe() should be moved to using >> >> ecore_pipe. >> > >> > no because evas does not depend on ecore >> > > Evas now does depend on ecore. > libevas links to libecore and we even call ecore_main_loop_get() from evas.
i've missed that commit in that case, yes ecore_pipe can be used indeed. But anyway, i still think that an eina_socket abstraction should be written Vincent PS : a git grep of ecore in src/lib evas shows src/lib/evas/common/evas_pipe.c: eina_thread_name_set(eina_thread_self(), "Eecore-pipe"); typo in the string, I think ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
