Dmitriy Kubyshkin

App Version From Git in Qt/QML

While making an app it is really important to keep accurate track of the versions. Usually such a tracking is implemented via tags in version control system like git. It’s also a good idea to keep in mind semantic versioning when assigning version to your code.

But tagging your code with the right version number is only the first step. You also need to show version to the user and in some cases the system.

Getting Version to C++

The easiest way to get git to display most recent tag is to run:

git describe --always --tags

If you have a tag in your repository and it is on current commit then you will get it’s name, otherwise something like this will be returned:


First part is the most recent tag name (yourtag), then number of commits since that tag (6) and then g(which stands for git) followed but current commit’s hash.

One thing to note is that from this point onward I assume that tags used for commits conform to semantic versioning and look something like 2.5.3.

Now that we understand the structure it’s time to get cracking. Qt .pro files allow you to call command line scripts and save it’s contents using $$system() function. Here’s how we can use it to get git tag:

GIT_VERSION = $$system(git --git-dir $$PWD/.git --work-tree $$PWD describe --always --tags)

The only tricky thing here is that we have to specify path for our repository manually using PWD variable .

To use it in C++ we can add compile-time #DEFINE statement by adding following line:


Once that is done, GIT_VERSION becomes usable just like any macro inside your code:

QString version(GIT_VERSION);

Passing version to QML

The easiest way to use version you got from git in QML is to create a singleton. Basically you just define a function that will return a QJSValue you want and then you import a module in QML. Here’s how you main.c might look:

#include <QtQml>
#include "qtquick2controlsapplicationviewer.h"

static QJSValue appVersionSingletonProvider(QQmlEngine *engine, QJSEngine *scriptEngine)

    QJSValue appInfo = scriptEngine->newObject();
    appInfo.setProperty("version", GIT_VERSION);
    return appInfo;

int main(int argc, char *argv[])
    Application app(argc, argv);

    qmlRegisterSingletonType("Native", 1, 0, "AppInfo", appVersionSingletonProvider);

    QtQuick2ControlsApplicationViewer viewer;

    return app.exec();

Once that is done, you can use the value inside your QML like this:

import QtQuick 2.2
import Native 1.0

Text {
    text:  AppInfo.version

Adding Windows Executable Version

On Windows version of the executable file as well as some other meta information (like icon) is specified via special resource file. Qt generates this file for you and even fills in the version from VERSION variable in .pro file.

This sounds easy enough, unfortunately if you try to put something that is non-numeric inside, like a hash, the application won’t compile. Luckily there is support for regular expression inside qmake so we can clean it like this:

win32 {
    VERSION ~= s/-\d+-g[a-f0-9]{6,}//

That’s it, now you should be able to see correct version number when inspecting properties of your executable using Windows Explorer.

Adding Mac OS X App Version

If you used Mac OS X you might have noticed that application version is displayed in Finder Inspector, it’s also used when showcasing your app on Mac App Store. The value is taken from Info.plist that is included into the package of every application.

Qt generates one for you automatically same as with RC file on Windows and it will also automatically fill in version from VERSION variable that we populated above when dealing with Windows, but it will only use major and minor version numbers. This might be ok for some application, but if you want to use full version — it can be done too by overwriting it after the main build like this:

macx {
    INFO_PLIST_PATH = $$shell_quote($${OUT_PWD}/$${TARGET}.app/Contents/Info.plist)
    QMAKE_POST_LINK += /usr/libexec/PlistBuddy -c \"Set :CFBundleShortVersionString $${VERSION}\" $${INFO_PLIST_PATH}

Putting All Together

To be able to easily reuse this I’ve separated all the logic into a Qt project include file (.pri) and saved it as a gist. It also takes care of few more edge cases than discussed above. To use it simply save gist to the same folder as the main .pro file and include before the end like this:


Credits and Resources