Add GitHub workflow for wheel and sdist building and upload #23
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on discussion in #22
This is a basically an almost straight copy/paste from vispy's github workflow which we've only used once or twice. I decided to use vispy's workflow instead of some of my other projects that have fancier workflows because vispy is closer to datoviz's build process with freetype and other stuff. We'll see how this goes.
There are a lot of steps I see in the install from source documentation and I'm not sure how many of them transfer to this 1:1. Also, this has the "cibuildwheel" tool to create all the wheels which means some of the build commands have to go into environment variables. It might be easier to put these into scripts (ex.
<repos root>/ci/
). I'm going to focus on linux first and see if we can get that working.This won't show up in datoviz's Actions until merged so if you want to see the current status you can go here: https://github.com/djhoese/datoviz/actions