-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Windows Support? #1437
Comments
Yes it is. |
@mdouze, oooooh that's interesting re: conda-forge/faiss-split-feedstock#2. Is this something that applies to 1.6.3 already, or only to HEAD? |
We support conda packages for the pytorch channel. The conda-forge channel's packages do not work on windows yet AFAIK |
@mdouze |
@mdouze I find there has not been a precompiled package on conda-forge for windows. Is there a guide for how to compile the source code for win? |
@hcji There are pre-compiled nightly packages available on the pytorch channel ( |
@beauby Thank you. But the GPU version is not ready? |
Restarted the conda-forge effort for windows under conda-forge/faiss-split-feedstock#17. With the build system changes from 1.6.3->1.6.4, it might still take a while, but should get there eventually. |
Windows is supported through anaconda now. closing. |
@beauby That is great! |
Starting from today, there are now windows packages in conda-forge. Cuda support for windows is hopefully not far away either: conda-forge/faiss-split-feedstock#19. Edit: this now needs conda-forge/faiss-split-feedstock#32 instead of conda-forge/faiss-split-feedstock#19 |
May I know the steps to install faiss-gpu using anaconda on windows? |
Faiss is not yet available with GPU on windows in conda-forge. It will be available once this PR is merged, but realistically, that will only happen when faiss itself officially supports it - there's ongoing work for this in #1610. Once that feedstock PR is merged, you will be able to do:
|
I see the number of PRs are merged to support Faiss on Windows
Is Faiss supported on Windows officially?
The text was updated successfully, but these errors were encountered: