-
Notifications
You must be signed in to change notification settings - Fork 64
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
Errors when building #18
Comments
Solved this by copy folder to
|
I'll look into this. This is on |
Yes! |
I returned to testing the package. I can not yet overcome the above compilation problem. |
Did you try with the latest? There has been some updated by @abeltensor |
Thanks! I updated
Thanks! |
I think that if we use this approach, it will be very convenient. |
Oh that's... surprising. What would the solution be then? Making sure everyone set their environment variable is a lot less intuitive, no? |
By default, this environment variables is set up by the CUDA toolkit installer itself. |
is it always the same? If a user decides to install CUDA elsewhere? If it's always the same we can hardcode it right? |
btw, feel free to send a PR to show me what you mean |
Thanks! Yes, the installer itself writes the selected path for installation. The default value is |
Sorry to interrupt the conversation here. But when I initially submitted my Pull request and added the other versions of Cuda I did actually try to set the environment flag ( Ill try it really quick now if you want and see if that will work. As @kolkov mentioned above, the cuda installer automatically sets up a CUDA_PATH variable on the system so it might be a better solution. |
After a quick try, I was unable to make it work. The problem it seems has to do with the difference between bash path variables and windows path variables. Cgo uses the gcc compiler which means it needs to use a bash style syntax to find the variable which would be I tried putting both |
Maybe this will help? |
Its not about the spaces so much as its about the windows variable format vs the bash variable format. |
As an alternative, we can use: |
I highly suggest putting in a PR. I'll mark it as hacktoberfest :) |
The text was updated successfully, but these errors were encountered: