currently anari level has some virtual switching of anari api calls to whatever the device implements; then barney has the same kind of virtual switching inside barney as to which 'backends' are enabled in the build.
it would significantly clean up the build process if each barney-"based" device could only have a single backend, with each such device then having a clear and well defined name. Ie, we'd have one barney_optix device, one barney_cuda, one barney_embree, one barney_cuda_mpi, etc.
This change would both help clean up the current build scripts, while also making it more explicit which backend/device the user is actually using.
currently anari level has some virtual switching of anari api calls to whatever the device implements; then barney has the same kind of virtual switching inside barney as to which 'backends' are enabled in the build.
it would significantly clean up the build process if each barney-"based" device could only have a single backend, with each such device then having a clear and well defined name. Ie, we'd have one barney_optix device, one barney_cuda, one barney_embree, one barney_cuda_mpi, etc.
This change would both help clean up the current build scripts, while also making it more explicit which backend/device the user is actually using.