OpenCL deprecation in MacOS 10.14

Richard L. Hamilton rlhamil at
Sun Sep 1 11:35:50 UTC 2019

On my 10.14.6 2017 MacBook Pro, output of "locate -i opencl.h" includes




(the first two because I have Xcode and command line compiler tools installed)

OTOH, that system was upgraded from prior OS releases.  Another (2018 Mac Mini) that I think started out on 10.14.x (x < 6, but it's on 10.14.6 now)  does not have the file in /System/Library/Frameworks, although the rest of /System/Library/Frameworks/OpenCL.framework is there. Both have Xcode 10.3 (10G8).

On either system, I can compile the demo in <> with Xcode, so it is finding a usable version of opencl.h somewhere. On either, it gets a bunch of deprecation warnings for functions with names beginning with "cl", not surprising.  The program runs on either, apparently successfully.

Of course, since matters may further deteriorate on Catalina (I don't know, not having signed up for the beta for it as yet), even if OpenCL is still usable and buildable (under the right conditions) on 10.14, you might want to pull the plug on support for it now, unless the performance advantage it offers is truly massive.

> On Sep 1, 2019, at 06:15, Vincent Habchi <vince at> wrote:
> Folks,
> I’m currently upgrading the GDAL port to 3.0.1 and… the OpenCL code doesn’t work anymore. No way I can find the file OpenCL.h anywhere in the system. I suppose this is part of Apple policy of deprecating OpenCL, so that no one can build new software based on it. 
> Could you confirm that OpenCL.h has also disappeared from the /System/Library/Framework on your machines (as of 10.14.6)? In which case, I’m going to pull out the +opencl variant from the new Portfile.
> Thanks a bunch,
> Vincent

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the macports-users mailing list