From 973c1fa5701366eed3752666d6035454ae37712c Mon Sep 17 00:00:00 2001 From: wm4 Date: Mon, 16 Jun 2014 16:57:19 +0200 Subject: gl_lcms: use thread-safe lcms API, require lcms2 2.6 The error log callback was not thread-safe and not library-safe. And apparently there were some other details that made it not library-safe, such as a global lcms plugin registry. Switch the the thread-safe API provided by lcms2 starting with 2.6. Remove our approximate thread-safety hacks. Note that lcms basically provides 2 APIs now, the old functions, and the thread-safe alternatives whose names end with THR. Some functions don't change, because they already have a context of some sort. Care must be taken not to accidentally use old APIs. --- wscript | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'wscript') diff --git a/wscript b/wscript index 0b4e196823..075e1cf20c 100644 --- a/wscript +++ b/wscript @@ -319,7 +319,7 @@ If you really mean to compile without libass support use --disable-libass." }, { 'name': '--lcms2', 'desc': 'LCMS2 support', - 'func': check_pkg_config('lcms2'), + 'func': check_pkg_config('lcms2', '>= 2.6'), }, { 'name': '--vapoursynth', 'desc': 'VapourSynth filter bridge', -- cgit v1.2.3