Looking for a way to store versions in a binary compiled from git repo

I’m looking for some tips to implement binary --version that would provide good information about the version it was compiled from.

The project is using autotools build system, and is stored in a git repo that acts as a SVN frontend.

  • Bumping version numbers for new releases in associated files (documentation)
  • Which files generated by Autotools should I keep in version control repository?
  • Displaying from which git commit a binary was compiled
  • Compiling workflow with version control
  • Should Autotools output scripts and Makefiles be included in a repository?
  • Using git for distribution with autotools
  • What I would like to have inside the binary is:

    • compilation time
    • SVN commit that acts as base
    • last git commit ID and time
    • if possible the last commit that affects this specific binary

  • How to get the Git hash of the current working directory?
  • What is the right way to add .NET project with NuGet dependencies to a git repo?
  • Connect to git repo on Visual Studio Online
  • git push returns “fatal: protocol error: bad line length character”
  • How can Jenkins list merge request titles from Gitlab in build report
  • Difftool for binary files in git
  • 2 Solutions collect form web for “Looking for a way to store versions in a binary compiled from git repo”

    You’ll probably want to write your source code to use a #defined constant version string. You can then pass that in through your build with a -DMY_VERSION=... option. That’ll let you embed a default value in the code, too, wrapped in an #ifndef, just in case!

    #ifndef MY_VERSION
    #define MY_VERSION 0.0.1-alpha
    print_version() {
        printf("my product: %s\n", MY_VERSION);

    A nice way to handle this on the build process side to make an intermediate build product which is simply a makefile snippet like MY_VERSION = "...". This again adds redundancy by letting you distribute the project with the version file already created, so that the build doesn’t have to depend on the presence of the SCM.

    You can then create the version string however you like, for example:

    echo -n 'MY_VERSION = "' > VERSION_FILE
    git describe >> VERSION_FILE
    echo "Compiled on $(date)" >> VERSION_FILE
    echo '"' >> VERSION_FILE

    Then in your primary makefile, include that snippet, and add -DMY_VERSION='"$(MY_VERSION)"' to the build flags for the appropriate object.

    A slight variation: make your generated file purely the version string, then pull that value into the appropriate variable in the makefile.

    If you need help with specific git commands to get the desired output, feel free to comment. git describe is a great one, though, meant for exactly this kind of thing. The default output is the closest tag ancestor of the current commit, hyphen, number of commits since the tag, hyphen, and abbreviated commit hash.

    The VERSION_FILE (see other answer) needs to be marked as BUILT_SOURCES in Makefile.am too for it to be successfully used with myprog_SOURCES, in case you use automake.

    Git Baby is a git and github fan, let's start git clone.