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
As described in anaconda-issues #6431, the placement of cudatoolkit libraries in DLLs on Windows keeps other packages from being able to use these libraries without hardcoding their paths. The current convention seems to place VC++ DLLs in Library\bin. It seems like it would make more sense to place the DLLs there and then create hardlinks in any other locations which are required for numba compatibility. See PR #7 for possible solution.
The text was updated successfully, but these errors were encountered:
mike-wendt
pushed a commit
to mike-wendt/conda-recipe-cudatoolkit
that referenced
this issue
Jun 8, 2020
As described in anaconda-issues #6431, the placement of cudatoolkit libraries in DLLs on Windows keeps other packages from being able to use these libraries without hardcoding their paths. The current convention seems to place VC++ DLLs in Library\bin. It seems like it would make more sense to place the DLLs there and then create hardlinks in any other locations which are required for numba compatibility. See PR #7 for possible solution.
The text was updated successfully, but these errors were encountered: