On 2 August 2010 18:53, Hal V. Engel <hven...@gmail.com> wrote: > In fact I would like to migrate LProf to lcms2 for a number of reasons. > Currently LProf has an embedded modified version of lcms 1.17. This was > needed > to extend lcms to support the creation of VCGT tags since there was no way to > do this short of modifying the lcms code (lcms1 did not have plugins). With > lcms2 the is no need for a customized version as at most it will only need a > plugin to handle this functionality (I have not looked - does lcms2 have VCGT > support?).
Yes, we're using it already in GCM. :-) > By migrating to lcms2 (and creating a VCGT plugin if needed) it > would be possible to remove the embedded version of lcms and this would make > things easier to maintain. Great. > The calls to lcms in LProf are fairly isolated in specific parts of the code > (most - 98% - are in liblprof) and this should make migrating to lcms2 fairly > straight forward. But LProf does use some lcms calls that are not part of the > public interface of lcms (IE. internal calls) and this might cause some issues > for the migration. Patches are welcome. Also what part of liblprof are you > using (or planning to use)? I'm planning to convert an it8 file to an icc file for trivial on the fly calibration, so really quite a lot of liblprof... > Also currently liblprof is statically linked in the current LProf builds. > Should this be changed so that it is a shared library (easy to do)? I know > that the digikam project also uses some code from an earlier version of > liblprof and perhaps having this as a shared library would make things easier > for everyone. But at least some of the functionality that digikam is using is > now embedded in a Qt4 designer plugin that is no longer part of liblprof so > making liblprof shared may not help them. I think the best idea would be: 1. either merge lcmsprf back into lcms2 2. have lcmsprf as a seporate add-on library that compliments lcms2 Then it would be trivial to use lcmsprof as a shared library in lprof. Point 1 would require Marti to accept a huge patch to lcms2 (which he might not be able/want to do) and point 2 would require splitting out the library to somewhere like github where we can all contribute to a shared version. If we did option 1 or 2, I would very much like to help converting it to use lcms2. Comments welcome, Richard. ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _______________________________________________ Lcms-user mailing list Lcms-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lcms-user
