1. 16 Oct, 2014 1 commit
  2. 22 Aug, 2014 5 commits
  3. 20 Aug, 2014 3 commits
  4. 15 Aug, 2014 3 commits
    • Check the number of benchmark tests ran · 11769369
      Matt Clarkson authored
      Previously the benchmark_test program executed the benchmark tests to make sure
      the API was working but was not checking the number of tests that were
      completed. If the regular expression matching breaks, zero tests could be ran.
      Similarly, if one of the APIs breaks and doesn't run the correct amount of tests
      then `make test` will catch this.
    • Ignore the result of make test · 92ddf09f
      Matt Clarkson authored
    • Do not use CMake CONCAT · 38c27c2c
      Matt Clarkson authored
      CONCAT was added quite late in the CMake release cycles so lets use `set()`
      instead which has been around _forever_...
  5. 08 Aug, 2014 2 commits
  6. 07 Aug, 2014 3 commits
  7. 06 Aug, 2014 1 commit
  8. 04 Aug, 2014 3 commits
  9. 02 Aug, 2014 1 commit
  10. 01 Aug, 2014 2 commits
    • get_git_version CMake function · c927845d
      Matt Clarkson authored
    • Implemented git versioning · d591edf5
      Matt Clarkson authored
      This patch automatically versions the shared libraries from any annotated `git`
      tags:
      
      ```
      git tag -a v1.0.0
      ```
      
      It expects semver version tags such as `v1.0.0`. It would be trivial to support
      `1.0.0` but looking around it seems that most C/C++ projects follow `vX.X.X`
      rather that `X.X.X` like a lot of `Node.js` stuff.
      
      This determines that the if the project has had a certain amount of commits
      since the last tag and also if the project is _dirty_ (has modified files), but
      does __nothing__ with that information. In the future a more robust release
      could be implemented in the script.
      
      This is pretty brittle and has little in the way of configuration. Ideally we
      should use `find_program` to work out where `git` is so that users can configure
      it. This implementation assumes that `git` will be available in `PATH`
      
      Outputs the following on the command line:
      
      ```
      -- git Version: v[MAJOR].[MINOR].[PATCH]-[COMMITS_SINCE_TAG]-[SHA1](-dirty)?
      -- Version: [MAJOR].[MINOR].[PATCH]
      ```
  11. 30 Jul, 2014 4 commits
  12. 27 Jul, 2014 3 commits
  13. 25 Jul, 2014 2 commits
  14. 24 Jul, 2014 2 commits
  15. 23 Jul, 2014 5 commits