On Mon, 21 Feb 2011 10:42:21 +0100 michael bouchaud <michael.bouch...@gmail.com> said:
now i see your detection stuff... we have some problems. 1. libraw-list as shipped is a c++ lib - not c. your detection code assumes a c library withs symbols that don't exist int he c++ lib (no c interface so the loader would have to become the c interface to libraw-lite) 2. there is a disagreement on header location/naming between your code and libraw-lite (0.7.2 i tried). also see #1 above - 0.7.2 disagrees with your detection and api usage. 3. this means whatever you are using is a patched libraw-lite or some specific version with a c interface as opposed to c++ (and maybe a .so not just a .a as libraw-lite 0.7.2 ships). so all in all this isnt a really fully working patch and loader. which brings me to part of the core issue here with libraw, libraw-lite etc. (gpl vs lgpl)... we need a solution for "gpl or other unfriendly licensed decoder libraries". i have an idea - a plan. and that involves a generic "load by running external process, if found in $PATH and then letting that process decode the image and write the result to a shared memory segment exposed to the loader binary". this would allow the creation of small binary utilities that handle this system that evas can execute to load things. as the data structures shared are non-complex (simple array of pixels values plus width/height/depth etc. values) this means gpl isn't an issue. i think at this stage it is better to do raw loading this way - then you can actually use full libraw too and just make a loader executable. but... need to create this generic "exec" loader first. > Sure it was here :D. And I'll be happy if this go in ! > > 2011/2/19 Carsten Haitzler <ras...@rasterman.com> > > > On Fri, 11 Feb 2011 15:21:42 +0100 (CET) Vincent Torri < > > vto...@univ-evry.fr> > > said: > > > > fyi = i'm waiting on an updated patch - if you can provide one that > > actually > > detects libraw-lite as suggested below... i'd be happy to put it in. > > > > > On Fri, 11 Feb 2011, michael bouchaud wrote: > > > > > > > 2011/2/11 Vincent Torri <vto...@univ-evry.fr> > > > > > > > > > > > >> > > > >> On Fri, 11 Feb 2011, michael bouchaud wrote: > > > >> > > > >> On Thu, 10 Feb 2011, michael bouchaud wrote: > > > >>>>> > > > >>>>> Hi, everybody I have wrote an evas_image loader for raw image > > type. I > > > >>>>> use > > > >>>>> > > > >>>>>> libraw-lite to do this jobs, who is licensed under lgpl > > > >>>>>> This is not perfect, so please review this code. Any comments are > > > >>>>>> welcome > > > >>>>>> ! > > > >>>>>> > > > >>>>>> > > > >>>>> some things: > > > >>>>> > > > >>>>> 1) ChangeLog > > > >>>>> 2) remove all the Evil stuff, I'll test it later on Windows > > > >>>>> 3) the check in EVAS_CHECK_LOADER_DEP_RAW is wrong, use pkg-config > > (see > > > >>>>> EVAS_CHECK_LOADER_DEP_EET for example) > > > >>>>> > > > >>>> > > > >>>> This is a new version of this patch. I don't change the m4 macro > > because > > > >>> libraw_lite aren't correctly packaged for now. So pkg-config can't > > detect > > > >>> them. I added an entry in changelog and change the double loop. I > > have > > > >>> also > > > >>> changed the header loading code. > > > >>> Any comments still are welcome ! > > > >>> > > > >> > > > >> he problem is that if someone installs libraw in another dir than > > /usr, the > > > >> detection will fail. > > > >> > > > >> There is a .pc file that is provided with libraw (actually, there are > > 2 > > > >> .pc, one for thread safe libn another for non thread safe lib). You > > should > > > >> (must) use one of them > > > >> > > > >> Vincent > > > >> > > > > > > > > yeah 2 pc files are given with libraw (under gpl) but not with > > libraw-lite > > > > (under lgpl). Sure the test of this macro is definitely bad. But I > > don't > > > > know how to detect this without pc files. go here > > > > http://www.libraw.org/libraw-lite to download libraw-lite not libraw > > > > > > haaa, i certainly downloaded libraw. Ok, then look at the tiff m4 macro > > > (note that it has 3 AC_CHECK_LIB because the name of the lib is not > > always > > > the same and because it can have some dependencies. You should just use > > > one AC_CHECK_LIB > > > > > > Vincent > > > > > > > > ------------------------------------------------------------------------------ > > > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > > > Pinpoint memory and threading errors before they happen. > > > Find and fix more than 250 security defects in the development cycle. > > > Locate bottlenecks in serial and parallel code that limit performance. > > > http://p.sf.net/sfu/intel-dev2devfeb > > > _______________________________________________ > > > enlightenment-devel mailing list > > > enlightenment-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > > > > > > -- > > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > > The Rasterman (Carsten Haitzler) ras...@rasterman.com > > > > > > > -- > Michaël Bouchaud -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
