When building #clinfo, if the OS is detected #Darwin, the system #OpenCL library is linked. Building with an OS override (e.g.: make OS=Homebrew) avoids this, and allows clinfo to be linked against the “local” OpenCL library (the aforementioned ocl-icd, typically).

Now the question is: would it be possible to build an executable that somehow manages to handle _both_? This would allow clinfo to report both the “system” platform and the “local” platforms.

As #Apple's #OpenCL implementation got deprecated and —I'm told— started degenerating towards uselessness, more people have started installing alternative ones through #Homebrew —typically PortableCL #PoCL.
This in turn returns an OpenCL library that is a #ICD loader —so people also install ocl-icd (again from Homebrew).

This poses an interesting conundrum for me as the #clinfo maintainer.