On Thu, 27 Sep 2012 13:57:48 +1000 David Seikel <[email protected]> said:
> On Wed, 26 Sep 2012 17:00:21 -0300 Gustavo Sverzut Barbieri > <[email protected]> wrote: > > > #2 - every dependency is mandatory: no more optional libjpeg, > > fontconfig and so on. No more "automagic" detection that silently > > causes problems for 99% of users (why can't I see text in e17? why > > can't I view png?) > > > > This removes lots of complexities from both configure.ac and helps > > packagers (see my complaints about packaging EFL on a live system, > > which Gentoo users suffer). This also helps people to have the same > > set of features everywhere, avoiding bugs like "I can't load font > > because I had fontconfig package, but no fontconfig-dev". > > > > In future we may review some of the mandatory libraries. Things > > like glib, gnutls/openssl will likely become optional in near future. > > This is a case for embedded folks doing custom slim systems. > > I will push strongly for optional dependencies, and the ability to only > compile those bits of EFL that I need. Some of my embedded work is in > controversial areas that governments usually heavily legislate. In at > least two countries (including the one I'm working in) there's a strict > legal requirement to keep things down to the bare minimum, leave out > things that are not actually part of the devices main function. This is > not just a slap on the wrist, this is "your device is illegal, you can't > use it in this country". Which will mean a wasted development effort, > the company closes down, and I'm out of a job. you can compile everything and just KEEP the libs/binaries etc. u need. example: compile all the way up to elementary and ONLY ship/package eina, eet, evas. (the libs and data files and modules for these). here's the catch. we need to optimize the build tree for the 99% of ppl not the 1%. for the 1% u can do the above - build more than u have to and strip out what u don't want shipped. you can also patch your tree so u are never screwed because its open source. it just adds more work onto your plate and takes it off upstream's plate. and now if you go and complain about how your builds are so slow because you build mode than you need, i'll pre-empt that with a "that's your fault.". you do not need to compile ON a slow device. me efl builds for everything INCLUDING e17 is down to 5mins with the split tree and re-running configures all the time. it'll be down to half this with the new tree. and thats a full re-compile and re-configure. if u are just doing updates u dont need to do this. you can either cross-compile if its a different architecture (eg arm target), OR.. you can use a chroot - the SAME chroot filled with what u already use on your device builds and build on a much beefier box. > So yeah, making custom slim embedded systems is kinda important to > me. :-P > > -- > A big old stinking pile of genius that no one wants > coz there are too many silver coated monkeys in the world. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
