7 Commity (dc587099a2e26ef6ce238ef709f508a91175a45d)

Autor	SHA1	Wiadomość	Data
Lex Neva	633ec88186	windows build (#79) ... Ink/stitch now supports windows!	2018-02-19 21:43:39 -05:00
Lex Neva	fe4a0ff1b8	one more fix	2018-02-04 23:10:18 -05:00
Lex Neva	977d3b0d7e	fix make locales	2018-02-04 23:03:41 -05:00
Lex Neva	72d52dc317	framework for translations (#55) ... sets up all the plumbing to send strings to CrowdIn for translation and incorporate the results	2018-02-04 22:38:24 -05:00
Lex Neva	0086607a94	stop adding build.tar.gz to the release	2018-01-23 22:39:53 -05:00
Lex Neva	a57ac2a902	use TRAVIS_BRANCH (which is the tag for tag builds)	2018-01-23 22:04:19 -05:00
Lex Neva	8bab858be6	pyinstaller release method (#16) ... pyinstaller packages up all of a python script's dependencies and builds them into standalone executables. It can either do a directory (containing a single executable and a bunch of shared libraries) or a self-contained executable that effectively just contains a compressed version of the directory. The problem is, if you have several scripts like we do, you get several large directories or standalone binaries, and there's a ton of duplication between them. Fortunately it looks like using the directory method and just combining the directories works fine (for this project). This PR runs the above build on any tagged commit and publishes a release in github containing the pyinstall-ified tarball. If the tag is named like "v1.2.3" _and_ the tag is on the master branch, then the github release will be marked as "production". Otherwise, it will be marked as a "pre-release". This means that we can build testable tarballs of the extension in a pull request by tagging a commit.	2018-01-13 20:18:50 -05:00