Skip to content
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 Build/CI #1278

Merged
merged 92 commits into from
Jun 18, 2015
Merged

Windows Build/CI #1278

merged 92 commits into from
Jun 18, 2015

Conversation

wiredfool
Copy link
Member

This PR adds an initial cut of Windows build and CI integration with Appveyor.com. (See #553 for background) The test suite passes with one exception: Image.grab errors out on the CI system. This has been tested on a local win7 pro x64 machine with the similar results as the appveyor CI runs, except that Image.grab works.

It is currently incomplete, in that only a subset of the dependencies are correctly built and recognized.

Working:

  • zlib
  • libjpeg
  • freetype
  • libtiff

Not Working:

  • Tk (not recognized)
  • webp (not recognized)
  • lcms (not built)
  • openjpeg (not built)

Appveyor's build matrix is configured with python 2.7 and 3.4, in 32 and 64 bit versions. Python 3.3 is available, but not enabled at this point. The current matrix covers all compiler versions, if not all pythons that we ship for.

Future Work:

  • Fix remaining dependencies
  • Cache dependency builds (potentially activate py33 at this point)
  • Deploy generated packages to a nightly archive

<installation>` should be sufficient

This page will describe a build setup to build Pillow against the
supported python versions in 32 and 64 bit modes, using freely
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Python", "64-bit modes"

@hugovk
Copy link
Member

hugovk commented Jun 16, 2015

Once all merged, here's how to enable a CI run for PRs: http://help.appveyor.com/discussions/questions/203-auto-run-tests-on-pull-requests#comment_33212404

@wiredfool
Copy link
Member Author

.obsolete was bits that were in progress. I guess they can just be dropped.

It's already ticked to trigger on PRs, so not sure why it's not doing it, unless you ticked that after I made the PR.

@hugovk
Copy link
Member

hugovk commented Jun 17, 2015

(Nope, not ticked by me, I don't have access to any of those settings. I guess they put it there during auth.)

@wiredfool
Copy link
Member Author

Huh. I'm confused then. It appears to be trying to merge other PRs but not this one. Hopefully it will get better when we merge this one.

@wiredfool
Copy link
Member Author

I'm going to merge this now, if we have trouble we can back it out later.

wiredfool added a commit that referenced this pull request Jun 18, 2015
@wiredfool wiredfool merged commit a92d737 into python-pillow:master Jun 18, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants