This PR eliminates futhark code generation when the generated library is built, and also avoids ever trying to generate OpenCL bindings for MacOS. The latter is an annoyance, but I cannot get it to work.
These changes together allow me to generate and publish a usable OpenCL library which can be included in a containing project without breaking its build on any OS (although the result cannot actually be called on MacOS). For development purposes, when on MacOS, sequential C can be generated in a local package.
This is all suboptimal, but it allows me to at least develop with a reasonable workflow on a Mac and deploy to my real target (Linux). I'll keep trying to figure out how to make bindgen work with OpenCL + MacOS, but it's not a top priority now.
This PR eliminates futhark code generation when the generated library is built, and also avoids ever trying to generate OpenCL bindings for MacOS. The latter is an annoyance, but I cannot get it to work.
These changes together allow me to generate and publish a usable OpenCL library which can be included in a containing project without breaking its build on any OS (although the result cannot actually be called on MacOS). For development purposes, when on MacOS, sequential C can be generated in a local package.
This is all suboptimal, but it allows me to at least develop with a reasonable workflow on a Mac and deploy to my real target (Linux). I'll keep trying to figure out how to make bindgen work with OpenCL + MacOS, but it's not a top priority now.
UPDATE: Also added