-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI builds #27
Comments
I don't think it's needed, if we switch back to the normal build system. It was topsy turby for a bit when cmake was attempted, but overall it's been kinda reliable. |
I'm sorry, I just kinda impulsively posted this after it didn't compile for On Mon, Jan 5, 2015 at 12:18 AM, Charles [email protected] wrote:
|
haha, that seems a bit aggressive for a project so small. Though there are multiple versions of TCC out there each incompatible with the next... any idea what is causing the issue now? |
I think that I got TCC from a fork of 0.9.25 on github, and ended up installing it on a system where I previously had a different libTCC version installed. I'll try getting the very latest version from Bellard's site and building it. Perhaps that will work :) |
The other reason to use CI is so that it can build against a standard environment. |
I don't actually know anything about how that works. How would we decide what the golden environment is? How would we target other platforms, i.e. OSX? |
I just added a .travis.yml file doing a simple build, but @cnlohr will still have to login at http://travis-ci.org to enable it. And maybe add a webhook |
If you have experience with this sort of thing I'd rather you take the lead on it? |
Oh! It's apparently part of github. Interesting. Regardless, if you're willing to accept the responsibility, I'd rather that. Already the codebase has departed a good ways from what I am the definitive expert of. |
Only used it once (and with java), so not really. The current config also only compiles which is not all that helpful. |
@cnlohr:
This game seems to vary a lot in buildability between commits-
Is it possible to use Travis or Drone.io to do continuous integration?
The only reason I suggest Drone is that it lets you retrieve build artifacts from a successful build.
The text was updated successfully, but these errors were encountered: