From f99739772b854d86ba01fb2b63268c08c9081e0f Mon Sep 17 00:00:00 2001 From: King_DuckZ Date: Thu, 23 Jul 2015 23:28:19 +0200 Subject: [PATCH] Fix travis.yml --- .travis.yml | 2 +- README.md | 3 +++ 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/.travis.yml b/.travis.yml index 89fe7d0..8dd4019 100644 --- a/.travis.yml +++ b/.travis.yml @@ -1,5 +1,5 @@ language: cpp compiler: gcc script: - - cmake -DCMAKE_BUILD_TYPE=Debug ../test && make + - cmake -DCMAKE_BUILD_TYPE=Debug test/ && make - ./unit/unit --gtest_filter='*.*' diff --git a/README.md b/README.md index fd571f3..8c397ab 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,7 @@ # Vector Wrapper # +## Build status ## +![Image Build status](https://travis-ci.org/KingDuckZ/vectorwrapper.svg?branch=master) + ## Motivation ## We all need vectors in our code, and there are quite a few implementations out there. They all do their job, and in terms of interface they are pretty similar to each other, but not *exactly* the same thing. While this is not an issue in its own, it can become a problem when your code depends on external libraries that will provide their own vector implementation. So you might have your own implementation, MyVector, and the library will give you Ogre::Vector3, which is what you must use when you invoke Ogre's functions. If you also depend on openCV you will have yet another vector around. Microsoft Kinect SDK also imposes you its own, barebone vector implementation.