-
-
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
Windows support #1
Comments
Here's the set of steps I used to build - it should basically just work with python 3.5
For python 2.7, a couple extra steps so that MSVC 2015 is used.
(stolen from https://github.com/pybind/pbtest) |
If c++11 is necessary, the best way is to add
To meta.yaml. this does exactly what you posted, but is tied into conda-build. You should also then pin the appropriate msvc runtime as a run requirement:
Finally, be very careful with this. You are mixing msvc runtimes, and this can lead to subtle bugs and out right crashes. Unfortunately, there's not really a good way to have both c++11 and python 2.7. There is some work towards making it easier to have a complete python 2.7 ecosystem with a newer compiler, but that's not really ready for conda forge yet. |
Created PR #2 which is running builds on the current master branch of the Git repo including on Windows. |
Summary from the PR. Current master branch builds and imports on Windows using Visual Studio 2015 but not with previous versions of Visual Studio. |
With wesm/feather#146, we should be able to create Windows builds. It might be nice to verify the builds before making a PyPI release
The text was updated successfully, but these errors were encountered: