Added cross-platform binary builds and Travis CI support #3
Conversation
…I tests. - Added initial .travis.yml for all three platforms - Applied a simple fix to ProperTree.command for pyinstaller failing to load/bundle all dependencies
|
Travis-CI.org is deprecated, use Travis-CI.com instead. |
Source? Couldn't find anything solid on Google, and last I checked travis-ci.com was for paid/commercial projects, while travis-ci.org was for free/public/OSS. I have hundreds of projects building there, and don't see any deprecation notices, nor have I received any such emails from them. |
|
https://blog.travis-ci.com/2018-05-02-open-source-projects-on-travis-ci-com-with-github-apps |
|
Please fix git conflicts. |
|
The bummer is that Travis CI now requires $ to run. Perhaps shift to GitHub Actions? |
|
No idea what just happened here. I was happily working on something unrelated in my own fork, merging upstream changes from this repo to my fork, when I noticed that this had suddenly been merged. Re Travis: GitHub Actions sounds good and perfectly feasible. EDIT: Hmm, I guess this PR was left open, but still no idea how it got merged when doing upstream sync in the fork itself. |
Uses
pyinstallerto build a single-file executable for Linux, macOS and Windows, thanks to Travis CI.To enable Travis, you just need to go here, login with your GitHub account, go to Settings, search for
ProperTreeand toggle the on/off switch next to it. After that, each commit should trigger a build.You can see a successful sample build output here: https://travis-ci.org/Dids/ProperTree/builds/529411076
Note that this doesn't have any tag/release logic yet, but I can work on that next if you're interested. :)
EDIT: Sorry, missed PR #2, although it has a bit of a different approach.