Use Qt Resources

The Qt Resource System lets you store files in your program's executable. In some ways, this feature resembles a dedicated file system, which we call resource file system. Usually, this file system contains QML code and other assets like images. If you use the QML compiler, the compiled code is always placed in the resource file system. There are a few application manager specific considerations, especially when your application needs to support both single-process and multi-process modes.

Compile Resources

You can add resources as external binary resources or as compiled-in resources; both are generated from a .qrc file. Typically, external binary resources are stored in a file with the .rcc extension, whereas compiled-in resources are stored in libraries in the Application Manager context.

It's important to understand that each process has its own resource file system. Consequently, to support multi-process mode, resources must be generated separately for the System UI and for each application. Conversely, in single-process mode there is only one resource file system and you must ensure that file paths don't clash. To prevent clashes, we recommend to prefix each application file path with the unique application ID.

Consider the following application file structure:

|---- app1
|     |---- main.qml
|     |---- app1.qrc
|     ...
|---- app2
|     |---- main.qml
|     |---- app2.qrc
|     ...

Without a prefix, in single-process mode, the main.qml files would clash. To avoid this, the .qrc file for app1 should read like this:

<!DOCTYPE RCC><RCC version="1.0">
<qresource prefix="app1">

For app2 the prefix should be "app2", respectively. Generally, all files contained in any .qrc file should be unique; this also includes files that the System UI uses.

Load Resources

In addition to the approaches described in The Qt Resource System, the Application Manager provides configuration options to load resources, both -- external binary resources and compiled-in resources in the form of a library.

Suppose you have a my.rcc binary file and a library file. These can be loaded into the System UI by adding the following lines to the am-config.yaml file:

  resources: [ "${CONFIG_PWD}/my.rcc",
               "${CONFIG_PWD}/" ]

You can also load these two files into an application by adding the following snippet to the info.yaml file:

  resources: [ "my.rcc",
               "" ]

The resources are loaded when the System UI starts, before the QML engine is instantiated. In multi-process mode the application resources are also loaded into the application process at startup. In single-process mode, resources are loaded when the application first starts and then reused on subsequent invocations; they are never unloaded.

Access Resources

The application manager allows for file access in the resource file system, either with the URL scheme (qrc) or the file name prefix (:). Both these options require an absolute file path in the resource file system, such as:

  • qrc:/app1/main.qml or qrc:///app1/main.qml
  • :/app1/main.qml

While the Qt Application Manager accepts this relaxed naming structure, the QML engine distinguishes between URLs and file names. For instance, an Image source property only accepts the qrc scheme.

If you want to specify a relative path, don't use the scheme or file path prefix.

If your files aren't found in the resource file system, you can list the contents of the entire resource file system with the following code snippet:

QDirIterator it(qSL(":"), QDirIterator::Subdirectories);
while (it.hasNext()) {
    const QString fn =;
    if (!fn.startsWith(qSL(":/")))  // exclude Qt internal files
        qDebug() << fn;

© 2019 Luxoft Sweden AB. Documentation contributions included herein are the copyrights of their respective owners. The documentation provided herein is licensed under the terms of the GNU Free Documentation License version 1.3 as published by the Free Software Foundation. Qt and respective logos are trademarks of The Qt Company Ltd. in Finland and/or other countries worldwide. All other trademarks are property of their respective owners.