GammaRay consists of two parts, the client and the probe. The client is the graphical user interface you are going to interact with. The probe interacts very closely with the Qt application it analyzes, using a number of internal APIs of Qt. This makes it necessary that the probe is built for exactly your Qt.

All of the following affect the compatibility of the GammaRay probe with the target application:

  • Qt version
  • Qt configuration
  • system architecture (most prominently 32bit vs 64bit)
  • compiler vendor (particularly on Windows)
  • compiler settings (particularly debug or release mode, on Windows)

This tight coupling to Qt makes it unfortunately somewhat difficult to provide pre-compiled binaries for the GammaRay probe in all cases, the following instructions therefore also cover how to build GammaRay from source code, should no pre-built probe be available for your configuration.

Local Development

Pre-built packages

Pre-built GammaRay packages are available for the following systems:

  • Qt Automotive Suite contains everything needed as part of the standard SDK already.
  • For some Linux distributions KDAB provides packages via the Open Build Service here.

Build recipes

Build recipes for the following source-based software distribution systems are available:

Building manually

You can obtain the source code of GammaRay on Github. To build it you need the following requirements:

  • Qt 4.8 or 5.2 or newer
  • CMake 2.8.12 or newer
  • a C++11 compatible compiler

GammaRay is build using the normal CMake build process, you can find more information in the Install.txt file in the GammaRay source tree.

Embedded Targets

The Qt Automotive Suite contains pre-built GammaRay probes are included in the device images.

For the following source-based embedded Linux distributions, there are example build recipes included below. Note that these likely need to be adjusted for your specific setup.

  • Yocto
  • Buildroot

In all other cases, including non-Linux target systems, refer to the cross-compilation instructions below.



SUMMARY = "GammaRay Qt introspection probe"

LIC_FILES_CHKSUM = "file://LICENSE.GPL.txt;md5=2abfe5daa817fd4346b6d55293941415"

inherit cmake_qt5

SRC_URI = "git://;branch=master"

SRCREV = "1728dff87163c370fa6903a6d739d1a132b4c62f"
PV = "2.7.0+git${SRCPV}"

DEPENDS = "qtdeclarative"

S = "${WORKDIR}/git"


FILES_${PN}-dev += " \
    /usr/lib/cmake/* \
    /usr/mkspecs/modules/* \
FILES_${PN}-dbg += " \
    /usr/lib/.debug/* \
    /usr/lib/gammaray/*/*/.debug \
    /usr/lib/gammaray/*/*/styles/.debug \

The lines you probably want to adjust are:

  • SRCREV: to use newer versions
  • DEPENDS: to select the Qt modules you are using, in order to enable all relevant GammaRay features



        bool "gammaray"
        depends on BR2_PACKAGE_QT5
        GammaRay Qt introspection probe.


GAMMARAY_VERSION = 1728dff87163c370fa6903a6d739d1a132b4c62f


$(eval $(cmake-package))

The lines you probably want to adjust are:

  • GAMMARAY_VERSION: to use newer versions
  • GAMMARAY_DEPENDENCIES: to select the Qt modules you are using, in order to enable all relevant GammaRay features

Manual cross-compilation

GammaRay can be cross-compiled using the normal cross-compilation mechanism of CMake, ie. passing CMake a toolchain file. The GammaRay source code contains a number of example toolchain files for Linux (RPI, iMX6), QNX (6.5, 6.6) and Android you can use or adjust.

The toolchain file is passed to CMake using the -DCMAKE_TOOLCHAIN_FILE command line option. Note that this only works on the very first CMake run, CMake doesn't like changing the toolchain file on an existing build directory. In that case, make sure to wipe the entire build directory first (just deleting CMakeCache.txt is not enough!).

Additionally you might need to pass one or more -DCMAKE_PREFIX_PATH=... command line options to point CMake to the location your sysroot has Qt (or any other dependency) installed in, just as during desktop builds.

A default build of GammaRay includes both the client and the probe, for cross-compiling you normally only want the probe, which can be achieved by setting the CMake option GAMMARAY_BUILD_UI to off.

Here's an example CMake invocation for building for RaspberryPI:

export SYSROOT=/where/your/rpi/sysroot/is/located
export PATH=<toolchain>:$PATH

cd <builddir>

© 2016-2017 Klarälvdalens Datakonsult AB (KDAB). Documentation contributions included herein are the copyrights of their respective owners.
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.