-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Guide to Install on Windows #644
Comments
May be nice to add to README |
"How to install on windows: Use linux" is not the solution you think it is. |
I said use WSL2, which is on Windows. And it's better than not being able to use it on windows at all. This way you can use WSL2 on windows and make it work (which is better than the typical response "we are not sure / we do not support windows"). |
WSL2 is a full fledged Linux VM, anything you run in it is not 'on windows', which just makes the title and explanation misleading or incorrect. It's a bandaid non-native solution that everyone already knows by default. "How to run nodejs on windows: Well first install virtualbox and download the linux binaries". No. Not the goal. People dropping by the repo looking to "run on windows" are looking for native dependency-less support for a litany of reasons, for which there are other issues actually describing real efforts at tackling the issue #12 (comment) |
You have to use WSL2!!
In WSL2:
First you have to make sure you install torch version that matches your nvcc version:
You can match the versions by installing an older version of torch which uses a different cuda version:
then clone causal conv 1d and pip install:
then clone mamba and pip install:
The text was updated successfully, but these errors were encountered: