On 10/10/12 10:37, Stefan Schmidt wrote: > Magic checks, debug and log level left out here as they seem to be > handled by profiles. Should valgrind support also be handled with this? >
I guess. > Unit tests, coverage and benchmark will be enabled for all libs at once > I suppose. > Unit tests and benchmarks should only build when you issue "make check/benchmark". Coverage is a bit more problematic because it requires you to recompile the sources. I'd love having a way to just make coverage and make it rebuild the sources that were built without coverage, but otherwise, we probably need an option. -- Tom. > Evas is a real beast when it comes to configure options. :) > > The first thing that jumps into my eye are the ARGB Conversion Options. > Having them all on by default would really be so much overhead? I mean > you don't use them it should be fine to just always build them. > > Image loaders are way more complicated sadly as we drag in dependencies > here. I would vote for making jpeg, png, gif, bmp, eet on by default. > > For the others we might need to see what libs distros ship in a default > installation so we can decide if we have a hard dep on these libs or not. > > That should clear things up a lot. (Yes, I left out engines here on > purpose. Don't wanted to fight over them :)) > I'd love to see fribidi and harfbuzz there by default, but tbh, I think some people would appreciate the speed improvements that come with ignoring the. -- Tom. ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
