-
Notifications
You must be signed in to change notification settings - Fork 10
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
Unable to build cpp functions on Windows #2
Comments
Hi! Thanks for trying the code. Seems to be a problem with windows and pytorch cpp extensions. Maybe this can help? https://discuss.pytorch.org/t/error-with-cpp-extentions/67559/4 Cheers, |
Thanks for the quick reply! Indeed, my Visual Studio installation was not equipped with command line tools. Now it does, but it yields the following error. It has something to do with the build.ninja files.
Any thoughts? Thanks again! Jeroen |
Hi Jeroen, Seems like the cudnn functions have other signatures on windows or the compiler is more strict. This is the key part of the error:
You can fix this error by changing I'm sorry, I never tested the code on windows! |
No worries at all, your help is really appreciated. To make it work, I had to replace all instances of So yes, it compiles correctly now and it succesfully ran a few epochs on some images. Curious to see what comes out when using the full data set. So thanks for your help! Cheers, |
Hi Jeroen, I'm closing this issue. I will add a link to this issue and #3 to the README for people with Windows. Thanks for your help! Hans |
Thanks for sharing this great repository. I'm interested to apply this approach to some of my own data, but I am struggling with the installation. When trying to train a model (
python streaming/train.py
) I get the following error:I then tried to instal Ninja with pip
pip install ninja
That worked, but yielded the following error, which is a bit beyond my knowledge.
Do you have any ideas what might be causing this? I am working on Windows 10, 64 bit, CUDA 10.1 and the nightly built torch and torchvision.
Thanks,
Jeroen
The text was updated successfully, but these errors were encountered: