On Mon, Aug 30, 2010 at 5:28 PM, Eduardo Lima (Etrunko) <ebl...@gmail.com> wrote: > Hey there, > > I was following the advice that --enable-pthread only makes sense for > multicore systems and since I am building for embedded, I thought it > was a good idea to disable it. But I didn't know that asynchronous > render had something to do with threads, so I let it there. > > What happens is that if you configure Evas with --disable-pthreads and > --enable-async-render all you get is compile errors. I tried to > investigate the issue a bit further but I just got more confused in > the middle of all those #ifdefs. > > Questions: > 1) Does it make sense to build with --disable-pthread and > --enable-async-render at all?
>From a strict code point of view, it should work, but this doesn't make sense at all. pthread is used for decompressing image in the background, so usefull even when you don't have multicore CPU, when async-renderer is put the heavy rendering task in another thread. So you will receive a performance hit when you are running async renderer on single core CPU. If I may give you a recommendation, always turn pthread support on, and turn async and pipe rendering on, when you know it will be usefull for you. > 2) In anyways, don't you think build should work regardless of the > configure options? Or at least it should refuse to build with insane configuration flags :-) -- Cedric BAIL ------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
