Adding travis and appveyor cotinuous integration tests #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an automated pull request that enables continuous integration testing for openFrameworks addons. 1
Before merging this PR you'll need to create an account on https://travis-ci.org and https://ci.appveyor.com using your github account and enable the tests for this repository there.
Once you have created an account at travis.org you can enable tests for this addon at https://travis-ci.org/jvcleave/ofxPQLabs
And for windows at https://ci.appveyor.com/projects/new
This PR includes test files for travis and appveyor ci services, once you merge it any new commit or PR to your repository will compile this addon for every supported platform against the latest openFrameworks.
This new files can be customized but we recommend to not touch them much except for commenting or uncommenting the different platfoms to test. That way we can ensure that the addon will work for any standard setup. The testing can be further customized (for example to install some dependencies in certain platforms by using some scripts in scripts/platforms there's more instructions on how to use them in the .travis.yml and appveyor.yml files in this PR.
Once your addon tests are working you can add a badge to your readme files so people using your addon can see the build status:
For travis you can just copy and paste the following markdown:
which will look like:
For appveyor you can find the badge code at https://ci.appveyor.com/project/jvcleave/ofxPQLabs/settings/badges
If you have any doubt you can ask directly in this PR or in the openFrameworks forum
[1] We believe this repository contains an openFrameworks addon because it's name starts with ofx, it has c, c++ or objc source in an src folder and any of the present c or c++ source files includes an openFrameworks header.
If this repository isn't really an openFrameworks addon, it is but it's not maintained anymore or you are simply not interested in testing it, we are really sorry for bothering you. You can just close or ignore this PR and no further communications will be sent to this repository.