On 26 July 2013 18:48, Robin Watts wrote:
> The cmsContext was introduced a while ago as a way to give *some* thread
> safety to lcms. It is by no means a perfect system (as having 2 separate
> apps calling into the same lcms library will conflict over their global
> settings (*)), but it does sol
Robin Watts wrote:
> * LCMS still uses static globals to hold things like the alloc function
> pointers, the alarm values, the currently registered plugins etc. I have
> spent some time over the past week or so updating my own local copy of
> LCMS so that these are held in a 'globals' struct and ad
On 26/07/2013 18:12, Richard Hughes wrote:
> 2. There's no void *user_data to cmsSetLogErrorHandler
The cmsContext is passed to every call to cmsSignalError (well, almost
every - There are a couple of calls where 0 is passed as the context).
> 2 is a lot harder and a lot
> more important. If you
