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. --- old-configure | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'old-configure') diff --git a/old-configure b/old-configure index 3bf27780f1..6eed18bcc8 100755 --- a/old-configure +++ b/old-configure @@ -761,7 +761,7 @@ check_statement_libs "LADSPA plugin support" $_ladspa LADSPA ladspa.h 'LADSPA_De check_pkg_config "libbs2b audio filter support" $_libbs2b LIBBS2B 'libbs2b' -check_pkg_config "LCMS2 support" $_lcms2 LCMS2 'lcms2' +check_pkg_config "LCMS2 support" $_lcms2 LCMS2 'lcms2 >= 2.6' check_pkg_config "VapourSynth support" $_vapoursynth VAPOURSYNTH 'vapoursynth >= 23 vapoursynth-script >= 23' -- cgit v1.2.3