-
-
Notifications
You must be signed in to change notification settings - Fork 2.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
Current Windows Build/Testing process #553
Comments
You can compile on Windows if you download the appropriate SDK: http://msdn.microsoft.com/en-us/dn369240.aspx And configure these settings:
|
The same compilers used to build the official CPython binaries, i.e. Visual Studio Pro 2008 for versions 2.6 to 3.2 and Visual Studio Pro 2010 for versions 3.3 and 3.4. The compilers are also part of the Microsoft Windows SDK for Windows 7 and .NET Framework 4 and 3.5 SP1. http://hg.python.org/cpython/file/95fff5a6a276/PCbuild/readme.txt
Build from source using the official source tar/zipballs and compiler settings compatible with the ones used by Python distutils (/MD, Release)
Don't know. |
I was somewhat worried that would be the compiler answer. @cgohlke, I assume that you've got a MSDN or academic license to VS? It appears that the VS Expresses can compile the 32 bit versions, but unfortunately, 2008 doesn't appear to be available anymore. |
I am almost certain that Pillow and all its C dependencies can be built with the free (and available) Windows SDKs. Visual Studio's IDE is not needed. |
That's a very helpful thread. When I first looked at the SDKs, it looked like they required VS, but now I see that they do include the compilers. I'll give that a shot. |
I've made some progress following these directions. So far, I've build for 2.7/x64, just to make sure that I'm getting the build process working end to end for one of the pillow iterations before I bury the poor machine for an hour. I'm running on Windows server 2012 x64, the base AMI on amazon EC2, with the 2 sdks installed. Also installed are emacs, setuptools, pip, virtualenv, 4 pythons so far and the github client. The plan is to be able to build/install/test in a virtualenv, or do a windows bdist if desired.
|
Hey guys, I am on Windows 8.1 Pro and I have severe difficulties getting it to work. So I downloaded the Windows SDK für Windows 8.1 and installed it with the following settings to I searched the folder and there is no |
The SDK you need depends on which python you're compiling with, not the OS you're running. Python 2.6, 2.7, and 3.2 require Win7 + .NET 3.5, 3.3 requires the Win7 + .NET 4. |
Looks like 3.4 takes the VC2010 SDK, which is Win7 + .NET 4: http://www.microsoft.com/en-us/download/details.aspx?id=8279 |
Status update, based on https://github.com/wiredfool/Pillow/tree/winbuild :
|
I've got the beginnings of a Windows CI at https://ci.appveyor.com/project/wiredfool/pillow/build/2.9.pre.18 . So far it's only one Python and not all the libraries but it is CI, on windows, and the tests are almost passing. This is based on my winbuild branch which is now merged up to current master. I think i'm going to clean up this first and then try to get all the other pythons and dependencies to build so that we can get at least basic windows CI going as soon as possible. |
Great news! |
@wiredfool Is it possible to move the main Pillow builds to a python-pillow account, rather than on your own account? The reason is free plans have only one concurrent job, which means there can be a bigger backlog for builds coming from both your repo and the main repo. Two accounts = two build queues. Here's how: |
I'll take a look at that. Another build queue would be good. |
Remind me why 3.3 isn't activated in AppVeyor? If it was initially disabled for speed, that would have made perfect sense at the time, but the builds are much faster now, consistently outperforming TravisCI. |
I guess we just wanted to get the main ones working and merged. AppVeyor accounts are free: how about just branching and giving it a shot? |
Probably speed, and I was working on maximal coverage with minimal implementations. Now that we're working, mostly, we should go towards more completeness. |
It passes - https://ci.appveyor.com/project/radarhere/pillow/build/3.0.pre.173 - and so I've created a PR. |
At the end of an AppVeyor build, it outputs
Is the only thing stopping us from using these as our Windows releases the fact that we are missing some dependencies? |
I think so, as long as we’re covering all the windows python versions. At the time this was done, we were covering a much smaller part of the matrix. |
@nulano given that #4495 has significantly improved compiling Pillow on Windows, do you think there's anything left to do here? |
What is the current best practices for building and testing Pillow on Windows?
@cgohlke?
The text was updated successfully, but these errors were encountered: