You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've installed this SDK on a Windows 11 x64 machine- well, actually, I'm not that good with CMake and stuff, but these two commands were executed successfully:
I have to assume a lot of things, because you're omitting some info on how you consume the result of the build.
The --target install will install the SDK to some place, I believe by default under Program Files so you were likely also prompted for admin priviliges.
Because you didn't specify a build type, CMake by default builds Debug, so you have a Debug builds of everything. (Which may be what you want, initially while developing it's surely the more useful build type, before wanting to benchmark or release when Release build type will be needed.)
We recently merged the ability to install Debug and Release builds on top of each other, allowing ton consume both build types on Windows from a single install location.
When using the SDK, you have to specify where you installed the SDK. This is typically done using CMAKE_PREFIX_PATH by specifying -D CMAKE_PREFIX_PATH=<root_of_SDK_install> while configuring your project using the SDK.
I've installed this SDK on a Windows 11 x64 machine- well, actually, I'm not that good with CMake and stuff, but these two commands were executed successfully:
However, I'm still getting the
cannot open source file "CL/cl.h"
error in Visual Studio Community 2022 forI appreciate any help with my issue, and thank you in advance.
The text was updated successfully, but these errors were encountered: