geany/geany-plugins — pull request #172 by b4n (2014-10-21 00:38:19+00:00)
Title: Enable Travis CI

***This has to be discussed a little before merging***

Here it is a bit more complex than [on Geany](/geany/geany/pull/360), but it's also probably more important. Same concern applies than on Geany, so I won't repeat myself here and concentrate on technical questions.

1. We need a recent Geany (we can't simply install the Ubuntu 12.04 package). Here I made the setup rules build it from latest Git, but it might not be so great:
1. Any build issue in Geany git will break GP.
2. It means we rebuild from source each time. Maybe a better solution would be to [install](http://docs.travis-ci.com/user/installing-dependencies/#Installing-Packages-from-a-custom-APT-repository) from the [nightly builds .deb](http://nightly.geany.org/debian/)s but unfortunately the [Wheezy ones aren't compatible with Ubuntu 12.04](https://travis-ci.org/b4n/geany-plugins/jobs/38556973#L43).
2. As you can see with the additional commit, I couldn't build GeanyPy because [Ubuntu 12.04 don't seem to have libpython-dev](http://packages.ubuntu.com/search?keywords=libpython-dev&searchon=names&suite=precise§ion=all), which is quite weird.
3. As you can also see, I had [a fairly weird](https://travis-ci.org/b4n/geany-plugins/jobs/38544571#L2945) problem with cppcheck that I can't reproduce on my machine (which has cppcheck 1.66). If anyone can tell me what's going on here, please go ahead (especially as other cppcheck calls worked fine, see above in the log).

Finally, you might see that the [GTK2 build currently fails](https://travis-ci.org/b4n/geany-plugins/builds/38554414), but that's legitimate, see #171 (so that's a good point for Travis CI as I found the error when setting it up :).