Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FR] Add a version number #1004

Open
krzikalla opened this issue Jul 17, 2020 · 1 comment
Open

[FR] Add a version number #1004

krzikalla opened this issue Jul 17, 2020 · 1 comment

Comments

@krzikalla
Copy link

I tried to figure out the version of my installed google/benchmark. It is either 1.5.0 or 1.5.1, but I am unsure.
I'd like to have a version.h file or something similar, which gives me the version at a glance.

@google google deleted a comment from akagamy55 Feb 18, 2021
@google google deleted a comment from akagamy55 Feb 18, 2021
@dmah42
Copy link
Member

dmah42 commented Jan 17, 2022

it would be really nice if when you ran a benchmark binary the version of the library was part of the intro metadata.

dmah42 pushed a commit that referenced this issue Jun 20, 2022
* Add possibility to ask for libbenchmark version number (#1004)

Add a header which holds the current major, minor, and
patch number of the library. The header is auto generated
by CMake.

* Do not generate unused functions (#1004)

* Add support for version number in bazel (#1004)

* Fix clang format #1004

* Fix more clang format problems (#1004)

* Use git version feature of cmake to determine current lib version

* Rename version_config header to version

* Bake git version into bazel build

* Use same input config header as in cmake for version.h

* Adapt the releasing.md to include versioning in bazel
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants