Ah yes, that is on, you can find all our build flags for the release builds in blender_release.cmake
also I’m just curious, so if you don’t want to answer or can’t say, that’s perfectly fine, but what product are you integrating cycles into? It’s always neat to see our stuff being used by other software.
I would tell you privately. We have competitors. Its a sold product. You can email me at my contact info. Or personal message
BTW I got 4.1 working. What I still don’t get right is the dll in our product. Its coming up smaller than the 4.1 blender version. Sadly we can’t use the blender version because we have custom shaders to support.
what dpcpp version are you on? (clang++ --version should show it)
using the one from the 4.1 code I downloaded. Your lib basically.
Yeahh but i’m asking for the output so i can double check that 
clang version 16.0.0
Target: x86_64-pc-windows-msvc
Thread model: posix
Yup that checks out, what ocloc version? (we don’t ship ocloc) and while i’m not sure about the exact version on the CI around the time of 4.1 i’m guessing 2024.1.0.142 was used.
I installed the toolset fairly recently, like 2 weeks ago. Is there a way to check version? I would imagine blender make would have blown up without it.
Pretty sure all will work, but newer versions have some things that dropped about 100MiB off our kernels, which would explain a significant size difference.
Beyond it being smaller, does it work?
No the sycl::platform::get_platforms in device_impl does not detect the card however this does work in Blender 4.1. I exactly duplicate the flags when building the cycles oneapi dll and lib.