Add Travis CI configuration

[jgoldfar]

Possible partial solution to #6 and #7? I can push an update to the branch to give the correct link for your CI if you'd like to turn CI for the repo on

[vikrambombhi]

The built game can be saved as a CircleCI artifact. Do you know if it is possible to make the artifact public? Another option would be to use a service like transfer.sh but this would be a temporary solution because the download link is only live for 14 days. A simple hack could be to just trigger the build every 14 days.

[jgoldfar]

I've only tinkered with CircleCI a couple of times (and I have no idea how "standard" Linux packaging should be done, unless creating a tarball suffices,) but one can easily push a build artifact to Github as a release (for tagged versions)

[jgoldfar]

This is now also working on OSX, so issues like #9 can hopefully be fixed in a reproducible way

[vikrambombhi]

not sure if pushing as a GitHub release is super simple. Can you try getting it to work and report back?

[jgoldfar]

Seems to work fine (see https://github.com/jgoldfar/MarbleMarcher/releases) though some of the settings will have to be tweaked for it to release from this repo, and from the master branch, etc.

[HackerPoet]

I'm not familiar with Travis CI, but I like the idea that it can cross compile for the other platforms. It would be great to add Mac and Linux versions to the itch.io page. I noticed that the tarballs seem to also include source for the dependencies, is that really necessary?

[jgoldfar]

I'd had a commit changing the packaging to only include usr/lib/ that got lost. I find debugging Travis more frustrating than it probably should be... Anyways, that is fixed now, and I added instructions to the README to work around any missing dependencies if using a tarball.

[HackerPoet]

Thanks, merging.

[HackerPoet]

How do I get it to rebuild after pushing?

[jgoldfar]

There should be a UI option on Travis to restart a given job, and I believe the release provider is set to overwrite any previous releases. Are you having trouble getting it to push back to this repository’s releases? It will need a new API key AFAIK