Skip to content
This repository was archived by the owner on Aug 23, 2021. It is now read-only.

Add AppVeyor build set-up for Windows#1

Merged
caspervdw merged 1 commit intopygeos:masterfrom
mwtoews:appveyor
Mar 9, 2020
Merged

Add AppVeyor build set-up for Windows#1
caspervdw merged 1 commit intopygeos:masterfrom
mwtoews:appveyor

Conversation

@mwtoews
Copy link
Copy Markdown
Contributor

@mwtoews mwtoews commented Mar 3, 2020

This is based on pygeos/pygeos#99

Currently draft, as the subrepo to pygeos needs to be updated with pygeos/pygeos#103

I can also add a version of get_appveyor_artifacts.py to scripts/, if you need to manually download a bunch of files from AppVeyor.

@caspervdw
Copy link
Copy Markdown
Member

Thanks @mwtoews. I merged the pygeos PR, so you can rebase the submodule on master

The script is probably not necessary (but thanks for pointing me at it, might come in useful). I want to make 'release' branch and let travis / appveyor automatically push to PyPI

@mwtoews mwtoews force-pushed the appveyor branch 5 times, most recently from 378bd37 to c8eabb3 Compare March 5, 2020 21:53
@mwtoews mwtoews marked this pull request as ready for review March 5, 2020 22:30
@mwtoews
Copy link
Copy Markdown
Contributor Author

mwtoews commented Mar 5, 2020

The build now creates 6 wheel artifacts. Each of these are successfully tested on the VM with "vanilla" Python too (installing via pip and running pytest). I've tested one of these wheels on my Windows desktop with the Visual Studio packed Python, and this also works. Hopefully the caching mechanism works, as this means the difference of 9 mins/build vs 40 seconds/build when GEOS is cached.

@caspervdw can take it from here, to get AppVeyor to deploy the artifacts to PyPI

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants