On Tue, Jul 10, 2012 at 12:29 PM, Carsten Haitzler <[email protected]> wrote: > On Tue, 10 Jul 2012 12:22:03 +0900 Cedric BAIL <[email protected]> said: >> On Tue, Jul 10, 2012 at 12:03 PM, Gustavo Sverzut Barbieri >> <[email protected]> wrote: >> > On Monday, July 9, 2012, Carsten Haitzler wrote: >> >> On Mon, 9 Jul 2012 11:24:03 +0100 Michael Blumenkrantz >> >> <[email protected] <javascript:;>> said: >> >> > I don't know, but the idea of having to go to >> >> > efl/src/lib/ecore/src/lib/ecore_con/file.c makes me not want a single >> >> tree >> >> > at all >> >> >> >> god no. it'd be >> >> >> >> efl/src/lib/ecore_con/file.c >> >> >> >> ecore would flatten out to its component ecore_*'s - other libs wouldn't >> >> need >> >> more than a single dir. >> >> >> >> >> > Seems good, but 'src' is useless. It would be nice to also keep a >> > consistency of plugins x modules. >> >> I disagree, we have data, docs, m4 and src at the first level. And I >> think they do split information nicely. I don't really care about >> going one more directory below, it will be filled with lib, bin, tests >> and examples (maybe benchmark ?). >> >> > Tom suggest GUI x core... I'd be against it, EFL is basically for GUI and >> > split the core of that is not of use. Maybe the lib, but please not the >> > packages. >> >> I am for. EFL is not only about GUI. You can write light server and >> service with them. People are advocating using Qt for that can of job. > > i dont think we should split the src tree into 2 efl builds (like we have 12 > or > so now) for non-gui vs gui. it should be a single src tree. if u dont want gui > stuff --disable it or use packaging to split the libs into 2 groups.
I agree with the one tree, just I think providing libefl-core.so and libefl-ui.so make sense and doesn't cost us anything to do. -- Cedric BAIL ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
