Closed sqs closed 10 years ago
I think the real value of this is the possibility of testing different builds for each supported GTK version (I only run the latest, 3.10, so I am not immediately aware if I break the build for another version). Do you know if this is possible?
I also see that you added a build tag for GTK 3.6, even though I never explicitly targeted that release. I assume this is just because I happened to never add bindings for any 3.8 functions that weren't already present in 3.6?
Unfortunately, and this answer both of your questions, Travis runs Ubuntu 12.04 LTS VMs and only has gtk 3.6. That's why I added the build tag. I tried to install a newer gtk but it got quite messy. In theory it is possible to do a matrix build with different lib versions, though.
Sent from my iPhone
On Oct 28, 2013, at 7:22, Josh Rickmar notifications@github.com wrote:
I think the real value of this is the possibility of testing different builds for each supported GTK version (I only run the latest, 3.10, so I am not immediately aware if I break the build for another version). Do you know if this is possible?
I also see that you added a build tag for GTK 3.6, even though I never explicitly targeted that release. I assume this is just because I happened to never add bindings for any 3.8 functions that weren't already present in 3.6?
— Reply to this email directly or view it on GitHub.
Hi, I cherrypicked your commit, updating the Go version from 1.2rc2 to 1.2. Since the gtk_3_6 build tag and other additions were already in place, only the .travis.yml file was added. Sorry for the late merge but better late than never I suppose.
Still would be nice if there were a way to test the other GTK versions.
Adds Travis-CI support. You can check the build status of my fork at https://travis-ci.org/sqs/gotk3 (look at the master branch).