aboutsummaryrefslogtreecommitdiff
path: root/.gitignore
diff options
context:
space:
mode:
authorMatt Clarkson <mattyclarkson@gmail.com>2014-07-30 20:12:04 +0100
committerMatt Clarkson <mattyclarkson@gmail.com>2014-08-01 09:20:28 +0100
commitd591edf5139e0b160bfedc88c1e1632d21fc9f28 (patch)
tree787d7dced031b5c02a686919a1b9b5ce24033a1a /.gitignore
parent890908c1976ec733125c28c70e1d1de5aa5a7447 (diff)
downloadgoogle-benchmark-d591edf5139e0b160bfedc88c1e1632d21fc9f28.tar.gz
Implemented git versioning
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] ```
Diffstat (limited to '.gitignore')
0 files changed, 0 insertions, 0 deletions