-
-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
%CUDA_PATH%
activation on Windows
#232
Comments
It's worth noting there is also some discussion about updating or dropping the activation script ( #206 ), which might also affect how this is handled |
Let us move the discussion to #206, I think it's the same issue. |
See #206 (comment). |
Ok I read that as Linux whereas the issue here is Windows The On Windows, we have a more similar CTK structure between CUDA 11 / 12 |
To CuPy the same applies to Linux as well. All headers and shared libraries can be found in the targets directory, enough to ensure a fully functional CuPy runtime. |
Ok let's close then |
Currently on Windows we set
%CUDA_PATH%
to%CONDA_PREFIX%
cupy-feedstock/recipe/activate.bat
Line 10 in 11d783c
However it appears when users run with this this, they get
CUDA_PATH
detection warnings. Though they seem to be able to use CuPy without issuesSince the headers and includes from the CTK typically are installed to
%CONDA_PREFIX%\Library
, wonder if we should update this to point to that locationThough looking at this logic in CuPy, am not sure if we should point to
%CONDA_PREFIX%\Library\bin
insteadThoughts?
The text was updated successfully, but these errors were encountered: