-
Notifications
You must be signed in to change notification settings - Fork 582
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
Whether windwos is supported? #501
Comments
Hi, |
I see. |
We provide binaries for cuda 11.3 and 11.6 (but only for linux and specific versions of pytorch). If you build from source, we support any version of cuda >= 11.3 (and maybe even earlier versions of CUDA, but not tested). |
Windows is not really supported. And as Anaconda ignores the .condarc-File it generated itself, I also haven't found out a way to move it to another target folder. |
The "filename too long" is a limitation in Windows, that can be addressed. You can also download windows builds from there (have to be installed manually): https://github.com/facebookresearch/xformers/actions/runs/3616539007 |
In addition to Windows' limitation also git has to be configured to use long filenames by using Sadly none of this will help, as ninja doesn't appear to be working with long filenames either. I'm aware of no fix.
Uninstalling ninja (and making sure it really is) irritatingly makes no difference, giving the exact same error. Will try my luck with the windows builds you kindly mentioned. |
@BlankFX1 I think another user had luck by moving the build to a directory with a short name. I'm not sure how long your |
As mentioned above I tried moving that folder yesterday by telling Anaconda to use a very short path. Sadly Anaconda keeps ignoring the .condarc-File it generated itself and I'm not familiar enough with it to know how I can tell it else what folder to use. Working with the linked windows builds didn't work either as none of them appears to be compatible
|
Hi, Just run in an elevated powershell prompt (I'm not aware of any downside to enabling them, but there may be) New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" -Name "LongPathsEnabled" -Value 1 -PropertyType DWORD -Force reference: |
Hi guys, I ran the following:
Redacted logs are as follows:
From within that, I got:
I'm using elevated Windows PowerShell for VS 2022 with Microsoft Build Tools preinstalled. It seems something else is still enforcing 260 character filename length limit. Attached full log: ninja-windows-10-long-file-path.txt |
It seems it could be related to this ninja-build/ninja#1900 |
❓ Questions and Help
The text was updated successfully, but these errors were encountered: